Bug#913363: RFS: desktopfolder/1.0.10-1 [ITP]

2018-12-07 Thread foss.freedom
Hi Herbert,

  many thanks for your advice.

I followed the instructions in uscan - imported the upstream
maintainers public key and then exported the minimal signing key.

I've rebuilt the package, confirmed that uscan downloads with the
minimal signing key and then built on buster.

Running linitian -i -I on the built changes file no longer reports the
wishlist public-upstream-key-not-minimal

David
On Fri, 7 Dec 2018 at 10:10, foss.freedom  wrote:
>
> It has been about a month since the initial package was uploaded to
> mentors.  Still hoping for some feedback please.
>
> Yesterday I've tweaked the package to remove an unnecessary
> build-dependency after discussing with upstream.
>
> I note one new "Information" lintian issue now occurs since the
> initial upload.  Probably due to a slight tweak to the current debian
> policy?
>
> public-upstream-key-not-minimal
> upstream/signing-key.asc has 1 extra signature(s) for keyid 92DED901DA15CC0D
>
> Is this something I can deal with (if so how?) - or should I ask
> upstream to create a signing-key.asc  for me using "gpg --armor
> --export --export-options export-minimal,export-clean keyid"
>
> thanks in advance
>
> David



Bug#913363: RFS: desktopfolder/1.0.10-1 [ITP]

2018-12-07 Thread Herbert Fortes

On 07/12/2018 08:10, foss.freedom wrote:

It has been about a month since the initial package was uploaded to
mentors.  Still hoping for some feedback please.

Yesterday I've tweaked the package to remove an unnecessary
build-dependency after discussing with upstream.

I note one new "Information" lintian issue now occurs since the
initial upload.  Probably due to a slight tweak to the current debian
policy?

public-upstream-key-not-minimal
upstream/signing-key.asc has 1 extra signature(s) for keyid 92DED901DA15CC0D

Is this something I can deal with (if so how?) - or should I ask
upstream to create a signing-key.asc  for me using "gpg --armor
--export --export-options export-minimal,export-clean keyid"



The lintian tag is severity wishlist. But it is
good to save space in the archive.

"The package contains a public upstream signing key..."

The uscan man page says:

[...]
The armored keyring file debian/upstream/signing-key.asc can
be created by using the gpg (or gpg2) command as follows.
[...]

Did up try to run the command and see if there is any problem?

These would be my steps.



Bug#913363: RFS: desktopfolder/1.0.10-1 [ITP]

2018-12-07 Thread foss.freedom
It has been about a month since the initial package was uploaded to
mentors.  Still hoping for some feedback please.

Yesterday I've tweaked the package to remove an unnecessary
build-dependency after discussing with upstream.

I note one new "Information" lintian issue now occurs since the
initial upload.  Probably due to a slight tweak to the current debian
policy?

public-upstream-key-not-minimal
upstream/signing-key.asc has 1 extra signature(s) for keyid 92DED901DA15CC0D

Is this something I can deal with (if so how?) - or should I ask
upstream to create a signing-key.asc  for me using "gpg --armor
--export --export-options export-minimal,export-clean keyid"

thanks in advance

David



Bug#913363: RFS: desktopfolder/1.0.10-1 [ITP]

2018-11-09 Thread foss.freedom
Package: sponsorship-requests
Severity: wishlist

  Dear mentors,

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

 * Package name: desktopfolder
   Version : 1.0.10-1
   Upstream Author : José Amuedo Salmerón joseamu...@gmail.com
 * URL : https://github.com/spheras/desktopfolder
 * License : GPL-3+
   Section : x11

  It builds those binary packages:

desktopfolder - Organize your desktop with panels, notes and photos

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

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


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

dget -x 
https://mentors.debian.net/debian/pool/main/d/desktopfolder/desktopfolder_1.0.10-1.dsc

  More information about desktopfolder can be obtained from
https://github.com/spheras/desktopfolder/blob/master/README.md

Notes:
I am the project lead of a Debian derivative called Ubuntu Budgie.  I
already maintain many Debian packages via my current Debian
Maintainers rights.

The reason for the request for this ITP is due to the current Nautilus
version in Debian.
We recognise that many budgie-desktop users expect a more traditional
desktop experience that includes the ability to place various files
and folders onto the desktop.  Budgie-Desktop had integrated with
Nautilus to provide that ability in the past.

But due to Nautilus 3.30 now in Buster, nautilus has removed the
desktop icons & folders support, Debian budgie users have had to use
strange workarounds such as running two File Managers - Nautilus and
Nemo where Nemo provides the desktop icons support.

This ITP provides an excellent alternative - a low memory usage
dedicated application that provides desktop icons & folders.

The application has been part of the ElementaryOS appcenter and
Elementary Pantheon.  I have been working with the maintainer to make
this application compatible with budgie-desktop.

As a project team Ubuntu Budgie have a direct interest in helping
support this application.  We now help the desktopfolder project to
provide translations for the project and we will be working with the
maintainer to provide additional capabilities in the future.

In terms of packaging I have worked with the maintainer to ensure
lintian issues such as code typos, mismatched copyright statements and
missing copyright statements on source files.  The maintainer has also
agreed to sign his tarballs which the package makes use of to provide
trust.

I have run check-all-the-things and helped resolve source matters in
consultation with the maintainer.

I have run lintian -i -I --pedantic on the built source.  One
Information lintian remains - missing autopkgtest.  I dont consider it
necessary for such a test to be defined.

I have built the debian/copyright via "cme update dpkg-copyright" and
manually checked that it has built the copyright file correctly.

The debian package contains one specific patch to revert two
ElementaryOS AppCenter specifics that doesn't make sense in the
context of Debian budgie-desktop.  This is explained in the dep3
header for the patch.  I have discussed this patch with the maintainer
and he is content with the approach.

If appropriate I would like to continue maintainership of this package
(assuming that it is acceptable to Debian) in a similar manner as my
current  packages (dak fossfree...@ubuntu.com)

  Changes since the last upload:

  * Initial Release (Closes: #913356)


  Regards,
   David Mohammed