Bug#872680: RFS: nautilus-hide/0.2.1-1 [ITA]

[Carlos Maddela]

Package: sponsorship-requests
Severity: normal

Dear mentors,

  I am looking for a sponsor for my package "nautilus-hide"

 * Package name: nautilus-hide
   Version : 0.2.1-1
   Upstream Author : Bruno Nova 
 * URL : https://github.com/brunonova/nautilus-hide
 * License : GPL-3+
   Section : gnome

  It builds this binary package:

nautilus-hide - Extension for Nautilus to hide files without renaming them

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

  https://mentors.debian.net/package/nautilus-hide


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

dget -x 
https://mentors.debian.net/debian/pool/main/n/nautilus-hide/nautilus-hide_0.2.1-1.dsc

  More information about my recent changes can be obtained from the
  debian branch of this repo: https://github.com/e7appew/nautilus-hide.git.

  Changes since the last upload:

  [ Bruno Nova ]
  * New upstream release [0.2.1].
  * debian/control:
- Added xdotool to Depends and Build-Depends.
  * debian/copyright:
- added license of po/de.po.
- updated copyright of extension/nautilus-hide.py.
  * debian/source/options: added po/de.po to extend-diff-ignore regex.
  * Remove debian/install, debian/nautilus-admin-restart, debian/postinst
and debian/prerm, removing the notification to restart nautilus.

  [ Carlos Maddela ]
  * New maintainer (Closes: #862211).
  * Add debian/gbp.conf.
  * Update VCS details.
  * Bump Standards Version to 4.0.1 and compat level to 10.
  * debian/control:
- Perform wrap-and-sort.
- Reformat package's description.
  * Package NEWS file as upstream changelog.
  * Update debian/copyright.
  * Include German translations.


  Regards,
   Carlos Maddela

Bug#872676: RFS: nautilus-admin/0.2.5-1 [ITA]

[Carlos Maddela]

Package: sponsorship-requests
Severity: normal

Dear mentors,

  I am looking for a sponsor for my package "nautilus-admin"

 * Package name: nautilus-admin
   Version : 0.2.5-1
   Upstream Author : Bruno Nova 
 * URL : https://github.com/brunonova/nautilus-admin
 * License : GPL-3+
   Section : gnome

  It builds this binary package:

nautilus-admin - Extension for Nautilus to do administrative operations

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

  https://mentors.debian.net/package/nautilus-admin


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

dget -x 
https://mentors.debian.net/debian/pool/main/n/nautilus-admin/nautilus-admin_0.2.5-1.dsc

  More information about my recent changes can be obtained from the
  debian branch of this repo: https://github.com/e7appew/nautilus-admin.git.

  Changes since the last upload:

  [ Bruno Nova ]
  * Remove debian/install, debian/nautilus-admin-restart, debian/postinst
and debian/prerm, removing the notification to restart nautilus
(Closes: #853147).

  [ Carlos Maddela ]
  * New upstream release [0.2.5].
  * Add debian/gbp.conf.
  * New maintainer (Closes: #862210).
  * Update VCS details.
  * Bump Standards Version to 4.0.1 and compat level to 10.
  * Perform wrap-and-sort on debian/control.
  * Package NEWS file as upstream changelog.
  * Update debian/copyright.


  Regards,
   Carlos Maddela

Bug#866123: RFS: fbkeyboard/0.1-1 [ITP]

[Julian Winkler]

I just uploaded a new source package (0.1-2).
I did every thing you told me.
But I don't know what's the problem about ignoring CPPFLAGS,
because the source code is written in c not cpp.

Bug#872661: RFS: node-unicode-property-aliases-ecmascript/1.0.3-1 ITP

[Julien Puydt]

Package: sponsorship-requests
Severity: wishlist

  Dear mentors,

  I am looking for a sponsor for my package
"node-unicode-property-aliases-ecmascript"

 * Package name: node-unicode-property-aliases-ecmascript
   Version : 1.0.3-1
   Upstream Author : Mathias Bynens
 * URL :
https://github.com/mathiasbynens/unicode-property-aliases-ecmascript
 * License : Expat
   Section : web

  It builds those binary packages:

node-unicode-property-aliases-ecmascript - Unicode property aliases
mapping for property names in Node.js

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


https://mentors.debian.net/package/node-unicode-property-aliases-ecmascript


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

dget -x
https://mentors.debian.net/debian/pool/main/n/node-unicode-property-aliases-ecmascript/node-unicode-property-aliases-ecmascript_1.0.3-1.dsc

  It is packaged within the Debian Javascript Maintainers repositories:
Vcs-Git:
https://anonscm.debian.org/git/pkg-javascript/node-unicode-property-aliases-ecmascript.git
Vcs-Browser:
https://anonscm.debian.org/cgit/pkg-javascript/node-unicode-property-aliases-ecmascript.git

Thanks,

Snark on #debian-js

Bug#872657: RFS: node-unicode-canonical-property-names-ecmascript/1.0.2-1 ITP

[Julien Puydt]

Package: sponsorship-requests
Severity: wishlist

  Dear mentors,

  I am looking for a sponsor for my package
"node-unicode-canonical-property-names-ecmascript"

 * Package name: node-unicode-canonical-property-names-ecmascript
   Version : 1.0.2-1
   Upstream Author : Mathias Bynens
 * URL :
https://github.com/mathiasbynens/unicode-canonical-property-names-ecmascript
 * License : Expat
   Section : web

  It builds those binary packages:

node-unicode-canonical-property-names-ecmascript - Unicode property
names supported in ES RegExp in Node.js

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


https://mentors.debian.net/package/node-unicode-canonical-property-names-ecmascript


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

dget -x
https://mentors.debian.net/debian/pool/main/n/node-unicode-canonical-property-names-ecmascript/node-unicode-canonical-property-names-ecmascript_1.0.2-1.dsc


  It is packaged within the Debian Javascript Maintainers repositories:
Vcs-Git:
https://anonscm.debian.org/git/pkg-javascript/node-unicode-canonical-property-names-ecmascript.git
Vcs-Browser:
https://anonscm.debian.org/cgit/pkg-javascript/node-unicode-canonical-property-names-ecmascript.git

  Thanks,

Snark on #debian-js

Bug#872652: RFS: python-pymeasure/0.4.6-1

[Ghislain Vaillant]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for the following package:

* Package name: python-pymeasure
  Version : 0.4.6-1
  Upstream Author : PyMeasure Developers
* URL : https://github.com/ralph-group/pymeasure
* License : Expat
  Section : python

Please check out the package by visiting the following URL:


https://anonscm.debian.org/git/debian-science/packages/python-pymeasure.git

Changes since last upload:

  * New upstream version 0.4.6
  * Drop patch No-pytest-conftest.patch.
Reason: No longer required
  * Adapt the autopkgtests to the new upstream layout.
Reason: Upstream moved the test suite outside the Python package, 
so the

tests can no longer be launched with --pyargs. Instead, the test suite
is copied from the source tree to the test bed before running pytest.
  * Add pytest-runner to the build dependencies
  * Drop superfluous nocheck guard for pybuild
  * Add support for the nodoc build option
  * Bump standards version to 4.0.1, no changes required
  * Fixup the Vcs-Browser URI

Regards,
Ghis

Bug#872648: RFS: find-file-in-project/5.4.0-1 [ITP]

[Nicholas D Steeves]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "find-file-in-project".  It is a 
requirement for elpy, a Python IDE for emacs (Bug# 861174).

Package name: find-file-in-project
Version : 5.4.0-1
Upstream Author : Will Farrington, Doug Alcorn, et al.  Chen Bin is the
  current maintainer 
URL : https://github.com/technomancy/find-file-in-project
License : GPL3+
Section : Elisp

It builds this binary packages:

elpa-find-file-in-project - Quick access to project files in Emacs

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

https://mentors.debian.net/package/find-file-in-project


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

dget -x 
https://mentors.debian.net/debian/pool/main/f/find-file-in-project/find-file-in-project_5.4.0-1.dsc

The package is in the pkg-emacsen team repo and can also be download with:

git clone 
https://anonscm.debian.org/git/pkg-emacsen/pkg/find-file-in-project.gi

Changelog:

find-file-in-project (5.4.0-1) unstable; urgency=medium

  * Initial release. (Closes: #861242)

 -- Nicholas D Steeves   Sat, 19 Aug 2017 14:10:13 -0400

Regards,
Nicholas D Steeves

Bug#872645: Subject: RFS: diodon/1.6.0-1

[Oliver Sauder]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: diodon
   Version : 1.6.0-1
   Upstream Author : Oliver Sauder 
 * URL : https://launchpad.net/diodon/
 * License : GPLv2
   Section : utils

It builds those binary packages:

 diodon - GTK+ Clipboard manager
 diodon-dev - GTK+ Clipboard manager (development files)
 gir1.2-diodon-1.0 - GTK+ Clipboard manager (GObject introspection data)
 libdiodon0 - GTK+ Clipboard manager (main library)

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

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


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

  dget -x
https://mentors.debian.net/debian/pool/main/d/diodon/diodon_1.6.0-1.dsc

Changes since the last upload:

 * New upstream release 1.6.0 (Closes: #824965)
 * Remove usage of dbus-launch (Closes: #823055, #836087)
 * Remove dependency libunique3 (Closes: #827235)
 * Added DEB_BUILD_OPTIONS support
 * Fixed dep5-copyright-license-name-not-unique

Regards,
 Oliver Sauder




signature.asc
Description: OpenPGP digital signature

Bug#872629: RFS: dmalloc/5.5.2-9

[Carlos Maddela]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: dmalloc
   Version : 5.5.2-9
   Upstream Author : Gray Watson 
 * URL : http://dmalloc.com/
 * License : CC-BY-SA-3.0 or Dmalloc
   Section : devel

  It builds these binary packages:

libdmalloc-dev - debug memory allocation library (development files and doc)
libdmalloc5 - debug memory allocation library

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

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


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

dget -x 
https://mentors.debian.net/debian/pool/main/d/dmalloc/dmalloc_5.5.2-9.dsc

  More information about my recent changes can be obtained at 
https://github.com/e7appew/pkg-dmalloc.

  Changes since the last upload:

  * Avoid direct calls to dpkg-parsechangelog from debian/rules.
  * Regenerate patches with git version 2.14.1.
  * Update compliance to Standards Version 4.0.1.
+ Priority is now optional, since extra is deprecated.
+ Update configure.ac to work with autoreconf 2.69 since autoreconf
  is now automatically performed by debhelper by default.
  * Mark libdmalloc5 package as Multi-Arch: same.
  * Enable LFS support for 32-bit architectures.
  * Remove incorrect use of 'Origin: vendor' from DEP-3 patch headers.
  * Perform wrap-and-sort on all Debian control files.
  * Fix typos in documentation.
  * Package HTML and PDF docs built from texi source file, rather than
just packaging the ones built upstream.
  * Fix erroneous failure in dmalloc_t.c test when free(NULL) is called.
  * Fix typo in debian/libdmalloc-dev.doc-base.
  * Update debian/copyright.


  Regards,
   Carlos Maddela

Re: Package not migrating

[Ole Streicher]

Hi Nils,

Niels Thykier  writes:
> Ole Streicher:
>> Andrey Rahmatullin  writes:
>>> On Thu, Aug 17, 2017 at 08:42:37PM +0200, Ole Streicher wrote:
> The package is affected by the same issue that chocolate-doom was in the
> referenced bug (#824169).  The situation in summary:
>
>  * The source produces 1 or more binaries in "main" and 1 or more
>binaries in "contrib"
>
>  * During upload, dak can (mistakenly) end up putting the source in
>both main and contrib at the same time.  Technically, it ends up in
>different suites (unstable vs unstable-debug), but these suites have
>to agree.

Can't they be rmeoved manually here? Or with a dirty script as a workaround?

>  * Once britney requests dak to migrate the package to testing, dak
>will notice the issue and reject the import (resulting in a
>rollback of all changes to testing).
>
>  * The quickest way to untangle the situation is to block the affected
>package (i.e. ensure britney will not migrate it), so other packages
>can migrate to testing.  This is most likely why cpl is now blocked
>by a manual hint.

But this will prevent from fixing bugs of the package in testing, doing
transisions etc. Currently the new package fixes a bug on armhf, which
is not that important due to the limited user base, but for sure there
will come RC bugs, transitions in this package (which then will also
prevent the reverse dependencies to migrate), or even transitions in an
dependent package (and then the transition will be stuck on a
non-migratable package). The solution to block packages which are
perfectly fine seems to be a quick, but also a dirty solution.

Is there a reason why the bug severity is "important" and not "serious"?
A bug that is preventing other packages from reaching "testing" (and,
in a few years, "stable" aka then "buster") should be RC, shouldn't it?
(And, shouldn't the affected packages be tagged as "affects" in the bug?)

I am also wondering why this did not happen before? The cpl package
structure is unchanged since years, without any reported problems.

> With the situation clarified, here is how it can be fixed:
>
>  1a. Have dak patched so it does not do this again.  Depending on the
>  exact implementation, it may need to be combined with 2).  Once
>  that is resolved, it will also need 3)

Which is nothing where I could do much, due to my non-existing dak knowledge.

>  1b. Avoid having a source package that builds binaries in multiple
>  components.  Sadly, this often implies duplicating the majority
>  of the source package.  Combine with 2) + 3)

Sounds like much work to work around a bug somewhere else. Especially
when the bug is temporary; since then one would want to revert it after
fixing.

>  1c. *Maybe* the FTP masters can work around this (I don't remember)
>  on their side on a per package basis.  This will need to be
>  combined with 2) (although, the FTP masters will probably do it
>  as the same time as this item) + 3).

So, this seems to be the way to go, right? Shall I just open a bug for
ftp-masters asking for unblock? Or what should I do here?

Best regards

Ole

Bug#872530: marked as done (RFS: qevercloud/3.0.3+ds-3 [RC])

[Debian Bug Tracking System]

Your message dated Sat, 19 Aug 2017 15:35:46 +0800
with message-id <4851354.gGQvXmjrRB@hosiet-tp>
and subject line Closing bug #872530
has caused the Debian Bug report #872530,
regarding RFS: qevercloud/3.0.3+ds-3 [RC]
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.)


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

Dear mentors,

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

 * Package name: qevercloud
   Version : 3.0.3+ds-3
   Upstream Author : Dmitry Ivanov 
 * URL : https://github.com/d1vanov/QEverCloud
 * License : MIT
   Section : libs

  It builds those binary packages:

libqt5qevercloud3 - Unofficial Evernote Cloud API library for Qt5
 qevercloud-doc - QEverCloud library documentation
 qt5qevercloud-dev - Development files for libqt5qevercloud

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

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


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

dget -x https://mentors.debian.net/debian/pool/main/q/qevercloud/
qevercloud_3.0.3+ds-3.dsc

  Git packaging repo on Alioth:

https://anonscm.debian.org/git/collab-maint/qevercloud.git

This upload would drop Qt4 packages (to cooperate with Qt4's removal) and fix 
the RC bug #871202.

 Changes since the last upload:

 qevercloud (3.0.3+ds-3) unstable; urgency=medium
 .
   * d/patches: refresh patch 0003 to fix FTBFS with gcc-7.
 (Closes: #871202)
   * d/control: bump Standards-Version to 4.0.1 (no changes needed)
   * d/control: remove Qt4-related package for upcoming Qt4 removal.
   * d/rules: review and remove Qt4 related instructions.

Regards,
Boyuan Yang

signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Version: 3.0.3+ds-3

Trying to close the bug #872530 properly. Thanks Adam!

Thanks,
Boyuan Yang--- End Message ---

Re: Package not migrating

[Niels Thykier]

Ole Streicher:
> Andrey Rahmatullin  writes:
>> On Thu, Aug 17, 2017 at 08:42:37PM +0200, Ole Streicher wrote:
>>> * Not touching package due to block request by adsb (check
>>>   https://release.debian.org/testing/freeze_policy.html if update is
>>>   needed) 
>> https://release.debian.org/britney/hints/adsb:
>> # 20170720
>> # in both main and contrib, breaks britney / dak
>> # (#824169)
>> block cpl
> 
> And what should I do to get it migrated?
> 
> Best
> 
> Ole
> 

The package is affected by the same issue that chocolate-doom was in the
referenced bug (#824169).  The situation in summary:

 * The source produces 1 or more binaries in "main" and 1 or more
   binaries in "contrib"

 * During upload, dak can (mistakenly) end up putting the source in
   both main and contrib at the same time.  Technically, it ends up in
   different suites (unstable vs unstable-debug), but these suites have
   to agree.

 * Once britney requests dak to migrate the package to testing, dak
   will notice the issue and reject the import (resulting in a
   rollback of all changes to testing).

 * The quickest way to untangle the situation is to block the affected
   package (i.e. ensure britney will not migrate it), so other packages
   can migrate to testing.  This is most likely why cpl is now blocked
   by a manual hint.

With the situation clarified, here is how it can be fixed:

 1a. Have dak patched so it does not do this again.  Depending on the
 exact implementation, it may need to be combined with 2).  Once
 that is resolved, it will also need 3)

 1b. Avoid having a source package that builds binaries in multiple
 components.  Sadly, this often implies duplicating the majority
 of the source package.  Combine with 2) + 3)

 1c. *Maybe* the FTP masters can work around this (I don't remember)
 on their side on a per package basis.  This will need to be
 combined with 2) (although, the FTP masters will probably do it
 as the same time as this item) + 3).

 2. Have the FTP masters clean up the old version that is in multiple
components at the same time.

 3. Ask the release team to remove the block hint now that the situation
is fixed (and attempting to migrate cpl will no longer force a
rollback)

Hope that clarified the situation.

Thanks,
~Niels