Why is tk8.4 removal triggering autoremoval messages of not depending packages at this point in time (Was: staden is marked for autoremoval from testing)

[Andreas Tille]

Hi,

On Sat, Dec 31, 2016 at 04:40:32AM +, Debian testing autoremoval watch 
wrote:
> staden 2.0.0+b11-2 is marked for autoremoval from testing on 2017-01-29
> 
> It (build-)depends on packages with these RC bugs:
> 734837: tk8.4: Time to remove from testing

Staden Build-Depends: tk-dev (without any version) and the binary
package Depends: libtk8.6 (>= 8.6.0) so I do not understand this
autoremoval message in principle and I specifically wonder why this
happens at this point in time.

Staden is juat an example for a set of packages with the same problem.

Kind regards

Andreas.

-- 
http://fam-tille.de

Bug#844184: RFS: muse-el/3.20+dfsg-1 [ITA]

[Sean Whitton]

On Fri, Dec 30, 2016 at 04:59:11PM +, Sean Whitton wrote:
> Just to let you know, we've already missed the deadline to add elpa-muse
> to stretch (it was Christmas day, due to 10 day migrations).

Sorry, looks like we were both wrong -- the deadline for binNEW is
February 5th.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#849318: RFS: eoconv/1.5-1

[Sean Whitton]

Dear Andreas,

On Sun, Dec 25, 2016 at 02:42:42PM +0100, Andreas Henriksson wrote:
> This repository looks whack. How do you build it? You should really add
> a debian/README.source with the details if you intend to use this as the
> official packaging vcs (as listed by the Vcs-* fields).

You might want to look at the origtargz(1) tool from devscripts to
handle this sort of repository.  You can just do this to get something
buildable:

% origtargz -u

--
Sean Whitton


signature.asc
Description: PGP signature

Bug#847101: kimchi source updated

[Lucio Correia]

I've uploaded new source with latest upstream release (2.3.1):

dget -x 
https://mentors.debian.net/debian/pool/main/k/kimchi/kimchi_2.3.1-1.dsc


Regards,
--
Lucio Correia

Bug#842026: RFS: bundlewrap/2.9.1-1, ITP: 838029 -- Decentralized configuration management system with Python

[Sean Whitton]

control: tag -1 +moreinfo

Dear Jonathan,

On Tue, Oct 25, 2016 at 01:48:49PM +0200, Jonathan Carter (highvoltage) wrote:
> Package: sponsorship-requests
> Severity: wishlist
> 
> Dear mentors (cc debian-python),
> 
> I am looking for a sponsor for my package "bundlewrap":

I just took at look at your source package.  You are not using the
dh_python tool, which means that your package fails several points of
the Python applications packaging policy (in particular, the .py files
you install are not bytecompiled).

Further, you list each dependency manually, whereas with dh_python you
could just use the $(python:Depends) substvar.  Please check out
dh_python!

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#847108: ginger-base source updated

[Lucio Correia]

I've uploaded a new package with latest upstream version:

dget -x
https://mentors.debian.net/debian/pool/main/g/ginger-base/ginger-base_2.2.2-1.dsc

Regards,
--
Lucio Correia

Bug#848687: RFS: yasnippet-snippets_0~git20161123-1

[Sean Whitton]

Hello Alberto,

On Thu, Dec 29, 2016 at 05:01:29PM +0100, Alberto Luaces wrote:
> Sean Whitton writes:
> >
> > If not, you should merge the changelog entries for -1 and -2.  It's just
> > confusing to have changlog entries that never made it into the Debian
> > archive.
> >
> 
> Well, it seemed cleaner than modifying an already published history, but
> I understand no solution is immune to drawbacks.  I have now pushed the
> new, fixed branch.  Please note that you will have to re-synchronise, or
> clone the repository again from scratch.

Oh dear, that wasn't what I meant!  I was suggesting you just make a
commit merging the changelog entries together.  Anyway, it's done now.

I'd like to suggest some improvements to your changelog:

>   * Updated d/control according to d.e.a.p.t. guidelines.

Only an existing team member would know what d.e.a.p.t. is!  Perhaps add
the URI ?

You also rewrote d/rules, but this is not mentioned in the changelog.

>   * Update standards to 3.9.8.

Did you have to change anything in the packaging for this update?  If
not, it's conventional to write "(no changes required)".

>   * Disabled parents in clojure mode due to upgrading errors.

This is meaningless to someone not already familiar with yasnippet.  You
wrote a great patch header, so I would suggest just this changelog
entry:

* Add 0001-Avoid-.dpkg-new-upgrading-error.patch

Please accept my apologies for not raising these suggestions in a
previous e-mail, and thank you for your patience with this sponsorship
process -- I'm confident I'll be able to upload after your next update.

(don't forget dch -r)

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#844184: RFS: muse-el/3.20+dfsg-1 [ITA]

[Sean Whitton]

Hello Nicholas,

Just to let you know, we've already missed the deadline to add elpa-muse
to stretch (it was Christmas day, due to 10 day migrations).

I'll respond properly later.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#847105: wok source updated

[Lucio Correia]

I've uploaded a new source package containing:

- Updated to latest upstream version (2.3.1)
- Fixes for Andreas' review comments, except separated packaging of 
javascripts, for which I'm working on.


Regards,

--
Lucio Correia

Bug#848416: RFS: pyvtk/0.5.18-1 [ITA]

[Pierre-Elliott Bécue]

Le mardi 27 décembre 2016 à 22:11:38+, Sean Whitton a écrit :
> Hello Pierre,
> 
> On Tue, Dec 27, 2016 at 06:04:58PM +0100, Pierre-Elliott Bécue wrote:
> > Le lundi 26 décembre 2016 à 20:38:42+, Sean Whitton a écrit :
> > > control: tag -1 +moreinfo
> > > 
> > > Dear Pierre,
> > > 
> > > Thank you for your interest in adopting this package.
> > > 
> > > Unfortunately, your work has not been properly integrated with what is
> > > already in Debian:
> > > 
> > > - you marked version 0.4.74-4 as released but it was never uploaded
> > 
> > True. Yet, it is in the team repo.
> 
> The changelog tracks the Debian archive.  You should merge the existing
> 0.4.74-4 changelog entry with your changes.

0.4.74-4 is not in the debian archive, only in the team repo. How should I
merge exactly?

> > 
> > Actually, it is included. The commit is just hidden in the history of the
> > team git repository for an unknown reason. See commit
> > 53434cf161a64ab9ac1578fec3613cce20ed451b and merge commit
> > 6fd4d560cf1f1f25a581a28a3c0a93ebd3159386. I added manually the changelog
> > that has been truncated in the merge.
> 
> Sorry, my fault, thanks for fixing up the changelog in your upload.

No worries, you're welcome. :)

> > > - your work is not pushed to the team git repository
> > 
> > I have no permission to push.
> 
> Have you asked to join the team?

I don't feel that I've done enough to get permissions, maybe my
interpretation is wrong.

-- 
PEB


signature.asc
Description: PGP signature

Bug#849754: RFS: guerillabackup/0.0.0-1

[halfdog]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: guerillabackup
  Version : 0.0.0-1
  Upstream Author : halfdog
* URL : https://github.com/halfdog/guerillabackup
* License : LGPL-3
Section   : misc

It builds those binary packages:

  guerillabackup - resilient, distributed backup and archiving solution

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

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


Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/g/guerillabackup/guerillabackup_0.0.0-1.dsc

More information about guerillabackup can be obtained from
https://github.com/halfdog/guerillabackup

Changes since the last upload:

  * Initial packaging of guerillabackup (Closes: #849714)


As also stated in comment to https://mentors.debian.net/package/guerillabackup
to avoid reviewers wasting time searching for dirty little package
secrets, here are some pointers to things, I had problems with,
when creating the package. Reviewers might disagree with my proposed
solution, any feedback is very welcome!

* Upstream Debian file templates: to support building of native
  packages using only the upstream source, Debian package files
  and build instructions are included already in upstream. To
  avoid duplication of them when not (yet) needed, they are copied
  within "rules" in target "override_dh_auto_configure"

* (Re)starting units on upgrade: As stated in documentation, two
  services can be used also from commandline (on demand) or as
  non-root user, depending on end user use cases. Thus it is intended,
  that the two systemd units are not enabled by default. Also
  a user may start them manually without enabling them. With upgrade
  following problem may arise: with standard debhelper means it
  was not possible to
  1) stop all running units and
  2) after update start only those, that were running beforehand.
  Solution:
  1) do not use debhelper for stopping/starting of units,
  2) find out in "prerm" which units are currently running, stop them and
  3) in "postinst" start only those, that were running in step 1)

* Use of .pyc files: As I do not fully understand the consequences
  of using .pyc files, especially in conditions where backup might
  be more important, e.g. when disks start already failing and
  py/pyc files might fall out of sync, I decided not to use them
  until I understand the possible risks. As codebase is very small
  and program is long-running, overhead from JIT-compiling should
  be not an issue.

Regards,
hd

Bug#845710: RFS: mongovi/1.0.0-1 [ITP]

[Sean Whitton]

Dear Tim,

On Thu, Dec 29, 2016 at 07:51:56PM +0100, Tim Kuijsten wrote:
> On Thu, Dec 29, 2016 at 06:46:58PM +, Sean Whitton wrote:
> > control: tag -1 +moreinfo
> > 
> > Dear Tim,
> > 
> > Is this package available in a git repository?
> > 
> > The Vcs-* headers point to a repo that does not contain a debian/
> > directory.  They should point to a repository containing the source
> > package.
> 
> Ah, I thought it was the general repository, not Debian specific :)
> Then I guess it's best to remove the VCS link, rigth?

I think it would be best to keep the packaging in a git repository and
point Vcs-* there, but if you prefer not to, it would be best to remove
those fields, yes.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#847102: RFS: ginger/2.3.0-1 - HTML5-based host management tool

[Lucio Correia]

Hi,

On Mon, 19 Dec 2016 08:06:40 +0100 Tobias Frost  wrote:

Control: block 775747 by -1

Please retitle the "RFP" bug (#775747) to "ITP" and set yourself as
owner.

--
tobi


OK, trying to find out how to do that.

Regards,
--
Lucio Correia

Bug#848969: RFS: dvdisaster/0.79.5-1~exp1

[Tobias Frost]

On Tue, Dec 27, 2016 at 07:40:57AM +1100, Carlos Maddela wrote:
> 
> 
> On 27/12/16 07:19, Sean Whitton wrote:
> > control: tag -1 +moreinfo
> >
> > Dear Carlos,
> >
> > On Wed, Dec 21, 2016 at 10:25:28PM +1100, Carlos Maddela wrote:
> >>  * Package name: dvdisaster
> >>Version : 0.79.5-1~exp1
> > Is there some special reason for the '~exp1'?  You can just use -1 to
> > upload to experimental, and then -2 if you want to upload 0.79.5 to
> > unstable.
> >
> The only reason I've done that is because that was what I was told to do
> for the dmalloc package. I wasn't sure as I'm still relatively new to this.
>

The reason I suggested this for dmalloc was to do this as an volatile upload,
solely ose to check if it builds and then throw away that version: In the case
more uploads would have been required -- c++ symbol files are tricky -- I
wanted to avoid the need to bump the debian version too much without any real
change behind.

--
tobi



signature.asc
Description: PGP signature

Bug#844184: RFS: muse-el/3.20+dfsg-1 [ITA]

[Nicholas D Steeves]

Dear Sean,

I hope you're enjoying the holidays.  Mine have been busy, and I hope
this version of src:muse-el is of sufficient quality to be uploaded to
the archive, because the addition of the new package elpa-muse won't
be possible after Jan 5th.

On Sat, Dec 10, 2016 at 02:46:11PM -0700, Sean Whitton wrote:
> Dear Nicholas,
> 
> On Wed, Dec 07, 2016 at 09:16:28PM -0500, Nicholas D Steeves wrote:
> > Thank you once again for holding me to high standards and for taking
> > the time to point out what needs work!
> 
> And thank you for your patience with this review process.
> 
> I saw some more problems.  Some of these are quite elementary errors:
> 
> 1. You're still not closing the ITA properly.  You are missing a '#'
> character.
> 
> 2. There is a spurious '+' character in your rules file that is subtly
> breaking the build.
> 
> I notice that you have an application to be a DM.  These sorts of errors
> can cause broken uploads, and confusion among collaborators.  Please try
> to get into the habit of checking your commits very carefully,
> especially when they are intended for upload to Debian.

I'm collecting a list of mistakes I'm likely to make when I'm not 100%
focused on the work I'm doing; in the future, I plan to use it as a
personal checklist.  If any of these mistakes fall into the "useful
for other new packages" category, please let me know and I'll find a
wiki.d.org article to contribute to.  On the other hand, maybe they're
just dumb mistakes ;-)

> Okay, now the less elementary stuff:
> 
> 2. Upstream's README says that the license for contrib/*blosxom is
> different from the main project.  This should be reflected in
> d/copyright (though see below for other issues to resolve first).

Done/pending.

> 3. Point 15 from my previous e-mail not yet addressed:
> > Why does elpa-muse depend on emacs-goodies-el?  Maybe add a comment to
> > the control file.
> 
Ah, specifically with a comment in d/control vs d/changelog.  Fixed,
plus a mistake I missed; in d/changelog I had intended to compromise
with recommends vs requires, but failed to make the change to
d/control).

> 4. "- Change section to editors; Change priority to optional."
> 
> This should be two separate lines.

Notice of this kind of convention I'd like to see in a "New Packages
Guide" ;-)

> 5. Have you figured out that "binary package" stuff discussed in your
> previous e-mail by yourself, or is that something I can help you with?

Sorry, unfortunately I have not.  Yes, please help me with this and
feel free commit directly to pkg-emacsen.

> > I've contacted Michael Olson about the possibility of providing an
> > examples/mwolson tarball on his website, because as I see it the
> > external links are an integral part of the Muse-managed website
> > example.  Specifically, I believe the intent of the example is to
> > provide a copy of a website that is browsable online so that the user
> > can explore both the source layout of a Muse-managed project and
> > browse the result.  In the meantime, I've added an override; if that
> > override is unacceptable, please let me know.  If we can keep the
> > override, I'd be happy to notify users--with NEWS--of the potential
> > privacy breach.
> 
> Looks good to me -- thanks for figuring out the warnings.
> 
> It would be good to limit the override to that directory.  Lintian
> overrides support wildcards, so you should be able to do something like
> this (not tested):
> 
> elpa-muse binary: 
> privacy-breach-generic*/usr/share/doc/elpa-muse/examples/mwolson/*

Originally I tried (and failed) to limit the override, so fell back to
the sloppy glob approach.  For future reference to anyone reading this
thread, this is the syntax that worked for me:

elpa-muse binary: privacy-breach-generic 
usr/share/doc/elpa-muse/examples/mwolson/*

> > > 10. How are the *.py files meant to be used?  Are they supposed to
> > > be copied into a pyblosxom installation, or run directly from where
> > > they are installed?  If the latter, they should be bytecompiled and
> > > installed into /usr/share/elpa-muse/contrib.  If the former, they
> > > are fine as they are.
> > 
> > By reading the following from getstamps.py:
[...]
> > It would seem that these are intended to be used in the following
> > manner: user reads the headers of these contributed python programs,
> > then adapts them to his/her needs, then copies them to the blog
> > project dir (eg: ~/my_blog).  Previous versions of src:muse-el
> > installed these contributed programs to
> > /usr/share/doc/muse-el/contrib.
> 
> I would be inclined to put them in /usr/src/elpa-muse.  The propellor
> package puts a copy of its upstream source code in /usr/src/propellor.
> 
> The current location is fine if you prefer.  Thanks for the explanation.

You're welcome.  In this particular case, I prefer to be conservative
vs disruptive ;-)

> > > 11. I've now reviewed d/copyright.  Unfortunately, you can't claim
> > > that the debian/ directory is GPL-3+ without 

Bug#848416: RFS: pyvtk/0.5.18-1 [ITA]

[Sean Whitton]

Hello Pierre,

On Thu, Dec 29, 2016 at 09:20:02PM +0100, Pierre-Elliott Bécue wrote:
> Le mardi 27 décembre 2016 à 22:11:38+, Sean Whitton a écrit :
> > Hello Pierre,
> > 
> > On Tue, Dec 27, 2016 at 06:04:58PM +0100, Pierre-Elliott Bécue wrote:
> > > Le lundi 26 décembre 2016 à 20:38:42+, Sean Whitton a écrit :
> > > > control: tag -1 +moreinfo
> > > > 
> > > > Dear Pierre,
> > > > 
> > > > Thank you for your interest in adopting this package.
> > > > 
> > > > Unfortunately, your work has not been properly integrated with what is
> > > > already in Debian:
> > > > 
> > > > - you marked version 0.4.74-4 as released but it was never uploaded
> > > 
> > > True. Yet, it is in the team repo.
> > 
> > The changelog tracks the Debian archive.  You should merge the existing
> > 0.4.74-4 changelog entry with your changes.
> 
> 0.4.74-4 is not in the debian archive, only in the team repo. How should I
> merge exactly?

This is roughly what I have in mind:

pyvtk (0.5.18-1) unstable; urgency=low

  [ Jakub Wilk ]
  * Use canonical URIs for Vcs-* fields.
  * Remove obsolete Conflicts/Replaces with python2.3-pyvtk and
python2.4-pyvtk.

  [ Stefano Rivera ]
  * Convert inline patch to 3.0 (quilt) to ease git-dpm migration.

  [ Ondřej Nový ]
  * Fixed VCS URL (https)

  [ Pierre-Elliott Bécue ]
  * New maintainer (Closes: #795017).
  * New upstream release
  * Uses pybuild for building the package.
  * Cleaning debian/*

 -- Pierre-Elliott Bécue   Sat, 17 Dec 2016 00:24:15 +0200

> > > > - your work is not pushed to the team git repository
> > > 
> > > I have no permission to push.
> > 
> > Have you asked to join the team?
> 
> I don't feel that I've done enough to get permissions, maybe my
> interpretation is wrong.

I see what you mean, and every Debian team is different.

However, chances are they would prefer that you join the team and push
your git history there, as then other team members can more easily build
upon your work.

So please submit a request, explaining that you want to work on pyvtk.
If they say no, it's not a big deal!

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#849627: RFS: xtrkcad/1:4.2.4a-1 ITA

[Sean Whitton]

control: tag -1 +moreinfo

Hello Jörg,

On Thu, Dec 29, 2016 at 07:03:26PM +0100, Jörg Frings-Fürst wrote:
> first thanks for your first review.

No problem.

I've now taken a proper look at your copyright file.  Some problems:

- the "FreeBSD" license has a standard shortname: BSD-2-clause

- did you make up the 'mixed', 'BSD-Revised' and 'permissive' license
  shortnames?  I suspect there are standard names -- try
  http://codesearch.debian.net

- you can't claim 2017 copyright on debian/ since we will upload this
  before 2017 begins :)

- if you run `licensecheck --copyright -r .` you will find many files
  that are Copyright 2005 David Bullis.  Maybe you should add this to
  the "Files: *" stanza?

- Mikko Nissinen also holds copyright on app/i18n/stripmsg.c

- copyright years for getopt.*, uthash.h, gwin32.c, mswbitmap.c and
  others are wrong -- why did you add '-2015' when the file was not
  edited since the earlier year?

- copyright for app/tools/halibut/charset/macenc.c wrong

> > >   Changes since the last upload:
> > > 
> > >   * New Maintainer (Closes: #849139):
> > > - debian/control: Add myself as maintainer.
> > > - debian/copyright: Add myself to debian/*.
> > >   * New upstream release (Closes: #847843, #784423).
> > 
> > In #847843, Mike Gabriel suggests team maintenance of xtrkcad.  Have you
> > got in touch with him about maintaining xtrkcad together?  Is he aware
> > of your ITA?  #847843 is itself almost an ITA, and it was submitted only
> > very recently, so you should be sure that your upload doesn't treat on
> > Mike's toes.
> > 
> My mistake. I have only skimmed through the text. I have ask Mike per
> mail and add him as Uploader.

Great.  I suggest writing "(Closes: #847843)" next to the Uploader
change -- it is okay to 'close' a bug more than once in a single upload.

> >   * Remove debian/source/options.
> > 
> > Why?
> 
> To use the default compression. Comment is added.

Okay.

> >
> > >   * Remove debian/source.lintian-overrides.
> > >   * Change debian/compat to 10 (no changes required).
> > >   * debian/control:
> > > - Bump Standards-Version to 3.9.8 (no changes required).
> > > - Bump debhelper B-D minimum version to 10.
> > > - Add Vcs-* tags.
> > > - Change Priority from extra to optional.
> > 
> > Just a reminder that you will have to submit a bug against
> > ftp.debian.org to have this actually take effect (post-adoption).
> > 
> 
> Because of the Priority change?
> 
> The change was based on the comment at the old PTS[1].

Ah.  You could mention this in your changelog, so I wouldn't ask the
question :)  E.g.

- Change Priority from extra to optional.
  To match current ftp-master override file.

> > >   * debian/rules:
> > >    - Enable hardening.
> > >   * New debian/patches/0700-info_file.patch to add requested directory 
> > > entry
> > > and INFO-DIR-SECTION.
> > >   * Rewrite debian/watch to use the sf redirector.
> > > - Add files to exclude in debian/copyright.
> > >   * Rewrite debian/copyright.
> > 
> > Lintian tags you can easily fix:
> > 
> > I: xtrkcad source: vcs-field-uses-insecure-uri vcs-git 
> > git://anonscm.debian.org/collab-maint/xtrkcad.git
> 
> My option to not change git to https was to start a git-gui client
> directly. If you want I change it.

Are you saying that git-gui cannot use https URIs?

It's okay to keep git:// if it is more convenient for you.

> > I: xtrkcad: spelling-error-in-binary usr/bin/xtrkcad Minumum Minimum
> 
> I have add a new patch 0900-spelling-errors.patch to correct the
> spelling error.

Thanks, and great work forwarding the patch.

> > It looks like you used wrap-and-sort -- please add this to the
> > changelog, so a future contributor knows which options to use.  E.g.
> > 
> > * Run wrap-and-sort -abst

You haven't added this to the changelog yet...

> > 
> > You made changes to d/rules not documented in the changelog.
> 
> sry. Also I don't have a git commit message. I have add a comment about
>  this.

What do you mean about "git commit message"?

Changelog for d/rules LGTM.

>
>  
> > 
> > After making further changes, don't forget to re-run `dch -r`, and
> > please remove the moreinfo tag from this bug to put it back in my queue.
> > 
> done

Ditto for this second review.

We are almost ready to upload.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#849581: RFS: numpydoc/0.6.0+ds1-1

[Sean Whitton]

Hello Ghislain,

On Thu, Dec 29, 2016 at 03:35:23PM +, Ghislain Vaillant wrote:
> I pushed a refreshed tag pointing at the latest commit already:
> 
> https://anonscm.debian.org/cgit/python-modules/packages/numpydoc.git/tag/?h=debian/0.6.0%2bds1-1
> 
> Isn't that enough?

It's fine, it just might cause some confusion later on since there are
two tags in existence, with the same name but signed by different
people.

This was basically my fault for not telling dgit not to create the
second tag.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#846325: RFS: netperfmeter/1.6.1-1

[Tobias Frost]

ping?

Bug#849627: RFS: xtrkcad/1:4.2.4a-1 ITA

[Jörg Frings-Fürst]

tags 849627 - moreinfo
thanks

Hello Sean,


Am Donnerstag, den 29.12.2016, 22:16 + schrieb Sean Whitton:
> control: tag -1 +moreinfo
> 
> Hello Jörg,
> 
> On Thu, Dec 29, 2016 at 07:03:26PM +0100, Jörg Frings-Fürst wrote:
> > first thanks for your first review.
> 
> No problem.
> 
> I've now taken a proper look at your copyright file.  Some problems:
> 
> - the "FreeBSD" license has a standard shortname: BSD-2-clause
> 
changed

> - did you make up the 'mixed', 'BSD-Revised' and 'permissive' license
>   shortnames?  I suspect there are standard names -- try
>   http://codesearch.debian.net
> 
I have change 

 * BSD-Revised to BSD-1-Clause
 * mixed to BSD-like-with-advertising-clause

permissive I have found at[1], but also a lot of other license text
with the same name. So I ask debian-legal[2].


> - you can't claim 2017 copyright on debian/ since we will upload this
>   before 2017 begins :)
ok I have removed the 2017 :-)


> 
> - if you run `licensecheck --copyright -r .` you will find many files
>   that are Copyright 2005 David Bullis.  Maybe you should add this to
>   the "Files: *" stanza?
> 
> - Mikko Nissinen also holds copyright on app/i18n/stripmsg.c
> 
> - copyright years for getopt.*, uthash.h, gwin32.c, mswbitmap.c and
>   others are wrong -- why did you add '-2015' when the file was not
>   edited since the earlier year?
> 
I have used the file modification time. 


> - copyright for app/tools/halibut/charset/macenc.c wrong
> 

I have checked and changed: 

 * Add David Bullis to Files: * and remove the stanzas with only him as
   copyright holder.
 * Use only the year(s) written into the files.
 * Add missing stanzas.



> > > >   Changes since the last upload:
> > > > 
> > > >   * New Maintainer (Closes: #849139):
> > > > - debian/control: Add myself as maintainer.
> > > > - debian/copyright: Add myself to debian/*.
> > > >   * New upstream release (Closes: #847843, #784423).
> > > 
> > > In #847843, Mike Gabriel suggests team maintenance of xtrkcad.  Have you
> > > got in touch with him about maintaining xtrkcad together?  Is he aware
> > > of your ITA?  #847843 is itself almost an ITA, and it was submitted only
> > > very recently, so you should be sure that your upload doesn't treat on
> > > Mike's toes.
> > > 
> > 
> > My mistake. I have only skimmed through the text. I have ask Mike per
> > mail and add him as Uploader.
> 
> Great.  I suggest writing "(Closes: #847843)" next to the Uploader
> change -- it is okay to 'close' a bug more than once in a single upload.
> 
Ah. I don't know that I can multiple close a bug at one time. Added.


> > >   * Remove debian/source/options.
> > > 
> > > Why?
> > 
> > To use the default compression. Comment is added.
> 
> Okay.
> 
> > > 
> > > >   * Remove debian/source.lintian-overrides.
> > > >   * Change debian/compat to 10 (no changes required).
> > > >   * debian/control:
> > > > - Bump Standards-Version to 3.9.8 (no changes required).
> > > > - Bump debhelper B-D minimum version to 10.
> > > > - Add Vcs-* tags.
> > > > - Change Priority from extra to optional.
> > > 
> > > Just a reminder that you will have to submit a bug against
> > > ftp.debian.org to have this actually take effect (post-adoption).
> > > 
> > 
> > Because of the Priority change?
> > 
> > The change was based on the comment at the old PTS[1].
> 
> Ah.  You could mention this in your changelog, so I wouldn't ask the
> question :)  E.g.
> 
> - Change Priority from extra to optional.
>   To match current ftp-master override file.
> 
It is now:

Change Priority from extra to optional to match with current ftp-master 
override file.


> > > >   * debian/rules:
> > > >    - Enable hardening.
> > > >   * New debian/patches/0700-info_file.patch to add requested directory 
> > > > entry
> > > > and INFO-DIR-SECTION.
> > > >   * Rewrite debian/watch to use the sf redirector.
> > > > - Add files to exclude in debian/copyright.
> > > >   * Rewrite debian/copyright.
> > > 
> > > Lintian tags you can easily fix:
> > > 
> > > I: xtrkcad source: vcs-field-uses-insecure-uri vcs-git 
> > > git://anonscm.debian.org/collab-maint/xtrkcad.git
> > 
> > My option to not change git to https was to start a git-gui client
> > directly. If you want I change it.
> 
> Are you saying that git-gui cannot use https URIs?
> 
No. I mean that I want to click on a link the right program should
open. 

> It's okay to keep git:// if it is more convenient for you.
> 
> > > I: xtrkcad: spelling-error-in-binary usr/bin/xtrkcad Minumum Minimum
> > 
> > I have add a new patch 0900-spelling-errors.patch to correct the
> > spelling error.
> 
> Thanks, and great work forwarding the patch.
> 
Normally. Or?

> > > It looks like you used wrap-and-sort -- please add this to the
> > > changelog, so a future contributor knows which options to use.  E.g.
> > > 
> > > * Run wrap-and-sort -abst
> 
> You haven't added this to the changelog yet...

I don't use this tool..

> 

Bug#849387: marked as done (RFS: farmhash/0~20161014-g92e897b-1 [ITP])

[Debian Bug Tracking System]

Your message dated Fri, 30 Dec 2016 17:54:21 +0100
with message-id <20161230165421.fcdny7ij5tzyj...@angband.pl>
and subject line Re: Bug#849387: RFS: farmhash/0~20161014-g92e897b-1 [ITP]
has caused the Debian Bug report #849387,
regarding RFS: farmhash/0~20161014-g92e897b-1 [ITP]
to be marked as done.

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

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


-- 
849387: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849387
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist

Note,
* This is a Tensorflow dependency.
* DoM-amd64 build is passing.
  
http://debomatic-amd64.debian.net/distribution#experimental/farmhash/0~20161014-g92e897b-1/buildlog

Dear mentors,

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

 * Package name: farmhash
   Version : 0~20161014-g92e897b-1
   Upstream Author : Google Inc.
 * URL : https://github.com/google/farmhash
 * License : Expat
   Section : science

  It builds those binary packages:

libfarmhash-dev - FarmHash, a family of hash functions (development files, 
docs)
 libfarmhash0 - FarmHash, a family of hash functions (shared library)

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

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


  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/f/farmhash/farmhash_0~20161014-g92e897b-1.dsc


  Changes since the last upload:

farmhash (0~20161014-g92e897b-1) experimental; urgency=medium

  * Initial release. (Closes: #848883)
--- End Message ---
--- Begin Message ---
On Thu, Dec 29, 2016 at 11:41:55AM +, lumin wrote:
> On Tue, 2016-12-27 at 22:47 +0100, Adam Borowski wrote:
> > What I meant is that you install a lot of cruft that doesn't appear to be
> > user docs at all
> 
> I agree with that. I reverted the package split and moved those
> stuff (incl. test suite) into the example directory. So the doc
> directory is cleaner:
> 
>   $ ls /usr/share/doc/libfarmhash-dev/
>   changelog.Debian.gz  copyright  examples/  NEWS.gz  README.gz  
> Understanding_Hash_Functions.gz
> 
> There is no file seems like a library guide there, so maybe the user
> will go take a look at the header directly.

I'm not sure if it makes sense to ship those files as examples/ either --
they're pieces of the testsuite with little use as examples.

But then, meh.  I don't care that much.  It's an upload to experimental
anyway -- there'll be plenty of time to massage the package.

In NEW.


Meow!
-- 
Autotools hint: to do a zx-spectrum build on a pdp11 host, type:
  ./configure --host=zx-spectrum --build=pdp11--- End Message ---

Bug#847102: ginger source updated

[Lucio Correia]

I've uploaded a new source package with new upstream release (2.3.1):

dget -x 
https://mentors.debian.net/debian/pool/main/g/ginger/ginger_2.3.1-1.dsc


Regards,
--
Lucio Correia

Bug#849691: RFS: gnome-shell-extension-radio/1.4-1 [ITP] -- GNOME shell extension for listening to Internet radio streams

[leo]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "gnome-shell-extension-radio", 
(see ITP [1]) :


* Package name: gnome-shell-extension-radio
  Version : 1.4-1
  Upstream Author : hslbck 
* URL : 
https://github.com/hslbck/gnome-shell-extension-radio

* License : GPL-3+
  Section : gnome

It builds those binary packages:

  gnome-shell-extension-radio - GNOME shell extension for listening to 
Internet radio streams


The source package is available at [2].

Packaging is available at [3].

Everything is ready except a few contributors informations missing in 
`debian/copyright` but I hope it'll to be fixed soon, see [4].


This is my first Debian package, sorry if I'm doing something wrong...

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849522
[2] http://213.246.39.125/~leo/packaging/gnome-shell-extension-radio/
[3] 
https://gitlab.com/zapashcanon/gnome-shell-extension-radio-packaging/tree/master/debian

[4] https://github.com/hslbck/gnome-shell-extension-radio/issues/43

--

Cheers,

Léo Andrès

Bug#847603: RFS: mod_pagespeed/1.11.33.4 [ITP] -- Apache module for rewriting web pages to reduce latency and bandwidth

[Sean Whitton]

control: tag -1 +moreinfo

Dear Jeff,

On Fri, Dec 09, 2016 at 02:43:32PM -0500, Jeff Kaufman wrote:
> I am looking for a sponsor for my package "mod_pagespeed":

This looks cool.  Here are some initial comments:

- I'm not prepared to fully review a package that is not available in
  git.  We might need multiple rounds of review, and git-diff(1) is
  invaluable for that.  Please consider `gbp import-dsc` or `dgit
  import-dsc` (the former is more popular; I prefer the latter)

- Your Vcs-* headers point to the upstream repository, which does not
  contain a debian/ directory.  Vcs-* headers are meant to point at a
  packaging repository.  Do you have one available somewhere?

- You have a very long list of quilt patches.  Have you considered
  merging some of them?  For example, all the -native patches could be a
  single patch.  Quilt patches can be a pain to manage when there are
  new upstream releases.

- I note that you have '#ifdef USE_SYSTEM_FOO' but your patch just
  strips off the whole conditional.  Wouldn't it be easier to use those
  USE_SYSTEM_* flags, instead of patching?

- generate.sh runs a copy of gyp in the source tree.  But gyp is
  packaged for Debian.  Please add a build-dependency on the packaged
  gyp, and run that instead (you might need another patch...)

- The package doesn't build in a clean sid chroot.  Log attached.

-- 
Sean Whitton
sbuild (Debian sbuild) 0.72.0 (25 Oct 2016) on zephyr.silentflame.com

+==+
| modpagespeed 1.11.33.4-1 (i386)  Fri, 30 Dec 2016 07:41:56 + |
+==+

Package: modpagespeed
Version: 1.11.33.4-1
Source Version: 1.11.33.4-1
Distribution: unstable
Machine Architecture: i386
Host Architecture: i386
Build Architecture: i386

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/unstable-i386-sbuild-dcccd87b-c0a4-4d7a-9cae-4908ef6a595f'
 with '<>'

+--+
| Update chroot|
+--+

Hit:1 http://mirror.vorboss.net/debian unstable InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

+--+
| Fetch source files   |
+--+


Local sources
-

/home/swhitton/rfs/modpagespeed_1.11.33.4-1.dsc exists in /home/swhitton/rfs; 
copying to chroot
I: NOTICE: Log filtering will replace 
'build/modpagespeed-vvyuTA/modpagespeed-1.11.33.4' with '<>'
I: NOTICE: Log filtering will replace 'build/modpagespeed-vvyuTA' with 
'<>'

+--+
| Install build-essential  |
+--+


Setup apt archive
-

Merged Build-Depends: build-essential, fakeroot
Filtered Build-Depends: build-essential, fakeroot
dpkg-deb: building package 'sbuild-build-depends-core-dummy' in 
'/<>/resolver-d63B9K/apt_archive/sbuild-build-depends-core-dummy.deb'.
dpkg-scanpackages: warning: Packages in archive but missing from override file:
dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy
dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
Ign:1 copy:/<>/resolver-d63B9K/apt_archive ./ InRelease
Get:2 copy:/<>/resolver-d63B9K/apt_archive ./ Release [957 B]
Ign:3 copy:/<>/resolver-d63B9K/apt_archive ./ Release.gpg
Get:4 copy:/<>/resolver-d63B9K/apt_archive ./ Sources [349 B]
Get:5 copy:/<>/resolver-d63B9K/apt_archive ./ Packages [430 B]
Fetched 1736 B in 0s (0 B/s)
Reading package lists...
Reading package lists...

Install core build dependencies (apt-based resolver)


Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  sbuild-build-depends-core-dummy
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 786 B of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 copy:/<>/resolver-d63B9K/apt_archive ./ 
sbuild-build-depends-core-dummy 0.invalid.0 [786 B]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 786 B in 0s (0 B/s)
Selecting previously unselected package sbuild-build-depends-core-dummy.
(Reading database ... 11483 files and directories currently installed.)
Preparing to unpack 

Bug#849627: RFS: xtrkcad/1:4.2.4a-1 ITA

[Sean Whitton]

Hello again Jörg,

On Thu, Dec 29, 2016 at 10:16:13PM +, Sean Whitton wrote:
> We are almost ready to upload.

I found one more issue...

- /usr/share/xtrkcad/{logo.bmp, html, examples, demo} should be in 
/usr/share/doc/xtrkcad

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#849627: RFS: xtrkcad/1:4.2.4a-1 ITA

[Jörg Frings-Fürst]

tags 849627 - moreinfo
thanks

Hello Sean,

first thanks for your first review.

Am Donnerstag, den 29.12.2016, 12:13 + schrieb Sean Whitton:
> control: tag -1 +moreinfo
> 
> Dear Jörg,
> 
> On Thu, Dec 29, 2016 at 10:08:50AM +0100, Jörg Frings-Fürst wrote:
> >   I am looking for a sponsor for my package "xtrkcad"
> 
> I'd like to sponsor this.
> 
> I assume it's okay for me to work out of your collab-maint repo.

ok...

> 
> >   Changes since the last upload:
> > 
> >   * New Maintainer (Closes: #849139):
> > - debian/control: Add myself as maintainer.
> > - debian/copyright: Add myself to debian/*.
> >   * New upstream release (Closes: #847843, #784423).
> 
> In #847843, Mike Gabriel suggests team maintenance of xtrkcad.  Have you
> got in touch with him about maintaining xtrkcad together?  Is he aware
> of your ITA?  #847843 is itself almost an ITA, and it was submitted only
> very recently, so you should be sure that your upload doesn't treat on
> Mike's toes.
> 
My mistake. I have only skimmed through the text. I have ask Mike per
mail and add him as Uploader.

>   * Remove debian/source/options.
> 
> Why?

To use the default compression. Comment is added.

> 
> >   * Remove debian/source.lintian-overrides.
> >   * Change debian/compat to 10 (no changes required).
> >   * debian/control:
> > - Bump Standards-Version to 3.9.8 (no changes required).
> > - Bump debhelper B-D minimum version to 10.
> > - Add Vcs-* tags.
> > - Change Priority from extra to optional.
> 
> Just a reminder that you will have to submit a bug against
> ftp.debian.org to have this actually take effect (post-adoption).
> 

Because of the Priority change?

The change was based on the comment at the old PTS[1].


> >   * debian/rules:
> >    - Enable hardening.
> >   * New debian/patches/0700-info_file.patch to add requested directory entry
> > and INFO-DIR-SECTION.
> >   * Rewrite debian/watch to use the sf redirector.
> > - Add files to exclude in debian/copyright.
> >   * Rewrite debian/copyright.
> 
> Lintian tags you can easily fix:
> 
> I: xtrkcad source: vcs-field-uses-insecure-uri vcs-git 
> git://anonscm.debian.org/collab-maint/xtrkcad.git

My option to not change git to https was to start a git-gui client
directly. If you want I change it.

> I: xtrkcad: spelling-error-in-binary usr/bin/xtrkcad Minumum Minimum

I have add a new patch 0900-spelling-errors.patch to correct the
spelling error.
> 
> In the future, after the stretch freeze, consider a package split:
> 
> I: xtrkcad: arch-dep-package-has-big-usr-share 16352kB 92%
> 
> It looks like you used wrap-and-sort -- please add this to the
> changelog, so a future contributor knows which options to use.  E.g.
> 
> * Run wrap-and-sort -abst
> 
> You made changes to d/rules not documented in the changelog.

sry. Also I don't have a git commit message. I have add a comment about
 this.
 
> 
> After making further changes, don't forget to re-run `dch -r`, and
> please remove the moreinfo tag from this bug to put it back in my queue.
> 
done

Many thanks!

CU
Jörg

[1] https://packages.qa.debian.org/x/xtrkcad.html

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser

Threema: SYR8SJXB

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.


signature.asc
Description: This is a digitally signed message part

Bug#845710: RFS: mongovi/1.0.0-1 [ITP]

[Sean Whitton]

control: tag -1 +moreinfo

Dear Tim,

Is this package available in a git repository?

The Vcs-* headers point to a repo that does not contain a debian/
directory.  They should point to a repository containing the source
package.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Re: dput: Call for feedback: What should change? What should stay the same? (was: Trouble with debsign, dput)

[Gianfranco Costamagna]

Hello Ben,

>

>I recently donned the mantle of maintaining ‘dput’ and am carefully
>making improvements. I am conscious of the special need for backward
>compatibility so I am taking care to understand how the Debian developer
>community uses it today.


ok, I used dput I think version "0.9.6.4ubuntu3"

first issue: probably a package outdated on Debian derivatives is bad and makes
people switch to dput-ng
(at least this happened to me)

second issue:
this is a warning when uploading on DebOMatic:
(I don't see it with dput-ng)


This account is restricted by rssh.
Allowed commands: scp sftp 

If you believe this is in error, please contact your system administrator.

Warning: The execution of '/usr/bin/ssh' as
'ssh deboma...@debomatic-i386.debian.net chmod 0644 
/srv/debomatic-i386/telepathy-ring_2.1.0-2.dsc 
/srv/debomatic-i386/telepathy-ring_2.1.0-2.debian.tar.xz 
/srv/debomatic-i386/telepathy-ring_2.1.0-2_source.changes'
returned a nonzero exit code.
Error while fixing permissions.



third issue:
dput ppa:costamagnagianfranco/locutusofborg-ppa 
../telepathy-ring_2.1.0-2_source.changes

(upload performed)
"wrong! the package had target suite "unstable", dput-ng refuses to upload in a 
ppa if the target
suite is Debian like


fourth issue:
dcut seems to work differently
dcut ftp-master reschedule -d 15 -f 
virtualbox-guest-additions-iso_4.3.36-1+deb8u1_amd64.changes
D: dcut 0.2.1
D: trying to get maintainer email from environment
D: Uploader from env: Gianfranco Costamagna 
D: first argument "ftp-master" treated as host
D: loading dput
D: calling dput.read_configs
D: Parsing Configuration File /etc/dput.cf
D: Parsing Configuration File /home/locutus/.dput.cf
D: Successfully parsed command "reschedule -d 15 -f 
virtualbox-guest-additions-iso_4.3.36-1+deb8u1_amd64.changes"
D: calling debsign: ['debsign', '-mGianfranco Costamagna 
', 
'/tmp/dcut.TYTeK6/dcut.Gianfranco_Costamagna__locutusofborg_debian_org_.1483097699.28814.commands']
.commands file has invalid Commands line: reschedule -d 15 -f 
virtualbox-guest-additions-iso_4.3.36-1+deb8u1_amd64.changes
debsign: .commands file appears to be invalid. see:
ftp://ftp.upload.debian.org/pub/UploadQueue/README
for valid format
Error: debsign failed.


dcut ftp-master dm --uid "samuel...@gmail.com" --allow pixiewps
Error: Could not parse commands at "dm"

>So I'm now familiar enough, but still fresh enough, that feedback is
>particularly valuable.


I would like to have an updated package, compatible with dput-ng, that works in 
Ubuntu and Debian uploads.

and it is kept in sync :)

>I'd like to take the opportunity of this thread to ask:
>What does ‘dput’ do that you really think should not be changed?
>What does ‘dput’ do that you wish it would stop doing?


work in a -ng compatible way, or with some better documentation about 
reschedule/dm commands

>What do other tools do better than ‘dput’? Do you think that ‘dput’
>should change to do those things the same way?


other tools do better checks for sanity before uploading

>The same questions can be asked of the ‘dcut’ program from the same
>package.


and now with dput from unstable:
dput debomatic-amd64 ../telepathy-ring_2.1.0-2_source.changes 
Checking signature on .changes
gpgme: ../telepathy-ring_2.1.0-2_source.changes: error 55: Invalid value
(7, 55, u'Invalid value')


dput ppa:costamagnagianfranco/locutusofborg-ppa 
../telepathy-ring_2.1.0-2_source.changes 
No host ppa:costamagnagianfranco/locutusofborg-ppa found in config


and so on...

thanks for maintaining it!
(maybe I'm just doing it wrong, I had a bad experience dated some years ago, I 
switched to dput-ng, and now
everything works(TM) )


G.

Re: Build-Depends vs Depends

[Narcis Garcia]

Build-Depends should not make any effect during package installation
process, because it's a dependency only for package-building process.



__
I'm using this express-made address because personal addresses aren't
masked enough at lists.debian.org archives.
El 30/12/16 a les 05:31, Taylor Kline ha escrit:
> What is the difference? How are they treated differently during the
> apt installation process? Thanks :)
>