Bug#975390: RFS: dragonfly-reverb/3.2.1-1 [ITP] -- Reverb effect plugins (metapackage)

[Ross Gammon]

tag 975390 - moreinfo
thanks

Hi Dennis,

I will take another look over the weekend. Hopefully my gpg key issue is 
sorted out now.


I am on a different machine, so I can't check the exact lintian warning. 
I think it was the "manpage missing" warnings, which have changed name 
and lintian does the divert automatically. I run lintian as a pbuilder 
hook (with all the pedantic options etc.), so it would have been the 
latest lintian in sid at that time. No matter. It is something that can 
be sorted out at the next upload anyway (if required).


Cheers,

Ross

On 25.02.2021 23.57, Dennis Braun wrote:

Hi Ross,

thank you for the review! I think ive fixed everything. I also added 2 
patches to fix cross building and fix building without sse.


about 5., i dont know which new tag you mean. my build on sid didnt 
had a different tag.


and about 12., yeah all plugins should be installed.

Best,
Dennis

Bug#975390: Review of Dragonfly Reverb

[Ross Gammon]

tag 975390 + moreinfo
owner 975390 !
thanks

Hi Dennis,

I have done a review of Dragonfly Reverb and have the following comments:
1. d/changelog - As this is the initial release for Debian, the
changelog entry should just have the one entry closing the ITP bug.
2. d/rules - I don't think we need to export the path prefixes. The
standard build should do the right thing.
3. d/rules - I think we can drop the dh_autobuild overides. dh % should
do the right thing on its own.
4. d/dragonfly-reverb.lintian-overrides - In addition to the note about
the online manuals, I think it would be worth adding to the note in the
override that there are no command line options and the executables
always launch a gui.
5. d/dragonfly-reverb.lintian-overrides - While we are at it, the tag
name has changed for the lintian warning which we could fix.
6. d/control - I don't think mentioning how the gui is built with a
toolkit is useful for a user of the package. I would prefer that the
long description mentions the different types of reverb effects that are
included.
7. d/copyright - The main Files: * part should probably be licensed as
GPL-3+ (not GPL-3). At least this is the case for some files in common/*.
8. d/copyright - Mark Borgerding (kiss_fft) is not mentioned.
9. d/copyright - Attributions for David Robillard, Gabriel M.
Beddingfield, Lars Luthman, Leonard Ritter, Rui Nuno Capela, Stefano
D'Angelo, and Steve Harris for various files in dpf/distrho/src/lv2 seem
to be missing.
10. d/copyright - An attribution for Javier Serrano in
dpf/distrho/src/vestige is missing
11. d/copyright - An attribution for Richard W.E. Furse, Paul
Barton-Davis, Stefan Westerfeld in dpf/distrho/src/ladspa/ladspa.h is
missing.
12. d/copyright - I ran out of time to complete the review of
d/copyright. I recommend a thorough review before uploading. There are
so many bundled effects in the source package. Are they all installed?

-- 
Regards,

Ross Gammon
FBEE 0190 904F 1EA0 BA6A  300E 53FE 7BBD A689 10FC





signature.asc
Description: OpenPGP digital signature

Re: Sending gpg keys to keyserver

[Ross Gammon]

Hi All,

On 12/02/2021 20:08, Ross Gammon wrote:
> Thanks for the tips everyone - it wasn't the silver bullet I was after,
> but that has given me some clues to investigate.
> 

Just a quick update on this.

$ gpg --refresh-keys
This gave me an error saying that Tor was not running. Sorry - I did not
capture the exact output from the command.

I found that dirmngr.conf had a "use-tor" item. After commenting this
setting out and rebooting:

$ gpg --refresh-keys
gpg: refreshing  keys from hkps://hkps.pool.sks-keyservers.net
gpg: keyserver refresh failed: General error

This was a much shorter error message, not complaining about Tor. But
still not very helpful :-)

So I decided to try the original command as something had changed:
$ gpg -vvv --keyserver keyring.debian.org --send-key 'fingerprint'
gpg: using character set 'utf-8'
gpg: sending key  to hkps://keyring.debian.org

That seemed to work! Probably I should be using Tor for obvious reasons.
I will look into that another day.

-- 
Regards,

Ross Gammon
FBEE 0190 904F 1EA0 BA6A  300E 53FE 7BBD A689 10FC



signature.asc
Description: OpenPGP digital signature

Re: Sending gpg keys to keyserver

[Ross Gammon]

Thanks for the tips everyone - it wasn't the silver bullet I was after,
but that has given me some clues to investigate.

It turned out to be faster to fix my laptop and upload from there :-)
I will hopefully get some time to fully investigate what is wrong with
the desktop machine soon.

On 10/02/2021 01:30, Paul Wise wrote:
> On Tue, Feb 9, 2021 at 6:48 PM Ross Gammon wrote:
> 
>> I have an upload stuck in the upload queue due to an expired key, and I
>> would like upload my newly unexpired key to the Debian keyservers so
>> that it is eventually unblocked.
>>
>> But I get this error:
>> $ gpg -v --keyserver keyring.debian.org --send-key 'fingerprint'
>> gpg: sending key 0x to hkp://keyring.debian.org
>> gpg: keyserver send failed: Connection refused
>> gpg: keyserver send failed: Connection refused
> 
> That command works for me and looks like the correct one according to:
> 
> https://keyring.debian.org/
> 
>> 6. Today, realise the upload has silently failed due to expired key.
>> 7. Extend expiry date of keys forward two more years.
> 
> It is a good idea to set a calendar appointment or at/systemd-run job
> to give you a reminder before the date. I'm doing the expiry update 3
> months before my expiry.
> 
> https://riseup.net/en/security/message-security/openpgp/best-practices#set-a-calendar-event-to-remind-you-about-your-expiration-date
> 
>> Any ideas on what configuration I might need to update?
> 
> Maybe look at your firewalls, network or proxy setup, or use wireshark
> and tcptraceroute to see what is blocking the connection. Or try
> creating a temporary user on your machine, logging in as that,
> creating a new key with a test name/email and try sending that to the
> server, the result will give some more info on where the problem is.
> Also do that from another machine on the same network, or from a
> Debian Live system booted on your machine.
> 


-- 
Regards,

Ross Gammon
FBEE 0190 904F 1EA0 BA6A  300E 53FE 7BBD A689 10FC



signature.asc
Description: OpenPGP digital signature

Sending gpg keys to keyserver

[Ross Gammon]

Hi All,

After some frustrated internet searching the last few days I am bringing
my problem here hoping for help.

I have an upload stuck in the upload queue due to an expired key, and I
would like upload my newly unexpired key to the Debian keyservers so
that it is eventually unblocked.

But I get this error:
$ gpg -v --keyserver keyring.debian.org --send-key 'fingerprint'
gpg: sending key 0x to hkp://keyring.debian.org
gpg: keyserver send failed: Connection refused
gpg: keyserver send failed: Connection refused

So how did I get into this mess?

1. Many years ago followed the riseup.net guide to configure my keys.
2. Over two years ago set the expiry date of my signing/encryption key
forwad two years to about now.
3. Weeks ago, sponsored a package to NEW.
4. Package was rejected.
5. The other day, uploaded a fixed package for my sponsee.
6. Today, realise the upload has silently failed due to expired key.
7. Extend expiry date of keys forward two more years.
8. Issue above command, then spend hours of frustrated searching :-)

I should say that I am on an Ubuntu machine (my Debian laptop has other
issues that need fixing). Googling comes up with gpg changes with
v2.1(?), and dirmngr now being the default - not curl ($ gpg --help
gives > gpg (GnuPG) 2.2.19). Riseup.net has completely changed since I
last looked, and there does not seem to be any updated advice on the
Debian keysigning pages.

Any ideas on what configuration I might need to update?

-- 
Regards,

Ross Gammon
FBEE 0190 904F 1EA0 BA6A  300E 53FE 7BBD A689 10FC



signature.asc
Description: OpenPGP digital signature

Bug#975389: Review of dpf-plugins RFS

[Ross Gammon]

tag 975389 + moreinfo
owner 975389 !
thanks

Hi Dennis,

Thanks for packaging dpf-plugins for Debian. Here is a review:

Need fixing:
d/changelog:
1. This is the initial release in Debian, so the the changelog should be
empty except for the "Initial debian release (Closes: #953129)" entry.
The earlier packaging work for KXStudio & Ubuntu is at least credited in
d/copyright.

d/copyright:
2. The distrho/extra plugins seem to be using the ISC license (not
GPL2+), or at least that is the case for Thread.hpp.
3. dpf/distrho/extra/String.hpp has "Copyright (C) 2004-2008 René
Nyffenegger", and Rene is not listed at all in d/copyright.
4. I stopped checking the d/copyright file here. I recommend a thorough
check of d/copyright to ensure the package passes smoothly through the
ftp-master review.

Minor/optional stuff:
5. d/dpf-plugins-vst.lintian-overrides (and for the lv2, ladspa & dssi
packages):
"splitted" is not grammatically correct, and the lintian output should
not be overriden, but a patch sent upstream. "3 Band Equalizer, split
output version" would be better.
6. dpf-plugins-common emits a lintian warning about "no-manual-page" for
the binaries. I tried a couple of them and they seem to open gui's and
the normal -h & -v options do nothing. Maybe we could check the others
and override the warning?

Other comments:
7. I see version 1.4 is now available upstream. If you prefer, we could
update to a full release rather than the "1.3 plus git commit" we have
at the moment.

I would be happy to upload with at least the first four comments fixed!

Regards,

Ross
FBEE 0190 904F 1EA0 BA6A  300E 53FE 7BBD A689 10FC



signature.asc
Description: OpenPGP digital signature

Bug#979274: Sfizz Review

[Ross Gammon]

n-outside-usr-share-doc
usr/lib/vst3/sfizz.vst3/gpl-3.0.txt
I: sfizz: spelling-error-in-binary usr/bin/sfizz_jack helpfull helpful
P: sfizz source: co-maintained-package-with-no-vcs-fields
X: sfizz source: debian-watch-does-not-check-gpg-signature
P: sfizz: image-file-in-usr-lib
usr/lib/lv2/sfizz.lv2/Contents/Resources/background.png
P: sfizz: image-file-in-usr-lib
usr/lib/lv2/sfizz.lv2/Contents/Resources/backgro...@2x.png
P: sfizz: image-file-in-usr-lib
usr/lib/lv2/sfizz.lv2/Contents/Resources/icon_white.png
P: sfizz: image-file-in-usr-lib
usr/lib/lv2/sfizz.lv2/Contents/Resources/icon_wh...@2x.png
P: sfizz: image-file-in-usr-lib
usr/lib/lv2/sfizz.lv2/Contents/Resources/knob48.png
P: sfizz: image-file-in-usr-lib
usr/lib/lv2/sfizz.lv2/Contents/Resources/kno...@2x.png
P: sfizz: image-file-in-usr-lib
usr/lib/lv2/sfizz.lv2/Contents/Resources/logo.png
P: sfizz: image-file-in-usr-lib
usr/lib/lv2/sfizz.lv2/Contents/Resources/logo_text.png
P: sfizz: image-file-in-usr-lib
usr/lib/lv2/sfizz.lv2/Contents/Resources/logo_t...@2x.png
P: sfizz: image-file-in-usr-lib
usr/lib/lv2/sfizz.lv2/Contents/Resources/logo_text_white.png
P: sfizz: image-file-in-usr-lib
usr/lib/lv2/sfizz.lv2/Contents/Resources/logo_text_wh...@2x.png
P: sfizz: image-file-in-usr-lib
usr/lib/vst3/sfizz.vst3/Contents/Resources/background.png
P: sfizz: image-file-in-usr-lib
usr/lib/vst3/sfizz.vst3/Contents/Resources/backgro...@2x.png
P: sfizz: image-file-in-usr-lib
usr/lib/vst3/sfizz.vst3/Contents/Resources/icon_white.png
P: sfizz: image-file-in-usr-lib
usr/lib/vst3/sfizz.vst3/Contents/Resources/icon_wh...@2x.png
P: sfizz: image-file-in-usr-lib
usr/lib/vst3/sfizz.vst3/Contents/Resources/knob48.png
P: sfizz: image-file-in-usr-lib
usr/lib/vst3/sfizz.vst3/Contents/Resources/kno...@2x.png
P: sfizz: image-file-in-usr-lib
usr/lib/vst3/sfizz.vst3/Contents/Resources/logo.png
P: sfizz: image-file-in-usr-lib
usr/lib/vst3/sfizz.vst3/Contents/Resources/logo_text.png
P: sfizz: image-file-in-usr-lib
usr/lib/vst3/sfizz.vst3/Contents/Resources/logo_t...@2x.png
P: sfizz: image-file-in-usr-lib
usr/lib/vst3/sfizz.vst3/Contents/Resources/logo_text_white.png
P: sfizz: image-file-in-usr-lib
usr/lib/vst3/sfizz.vst3/Contents/Resources/logo_text_wh...@2x.png
P: sfizz source: package-does-not-install-examples
editor/external/vstgui4/vstgui/standalone/examples/
P: sfizz source: silent-on-rules-requiring-root
P: sfizz source: source-contains-autogenerated-visual-c++-file
vst/external/VST_SDK/VST3_SDK/public.sdk/source/vst/aaxwrapper/resource/aaxwrapper.rc
X: sfizz source: upstream-metadata-file-is-missing

Let us know on the list if you need any help to improve things.

-- 
Regards,

Ross Gammon
FBEE 0190 904F 1EA0 BA6A  300E 53FE 7BBD A689 10FC



signature.asc
Description: OpenPGP digital signature

Bug#976113: Closing Hydrogen RFS

[Ross Gammon]

Hi Nicholas,

On 07.01.2021 23.44, Nicholas D Steeves wrote:

Have you created the release tag on your local master branch, or shall
I, and would you like to push the tag when the package is accepted, or
would you like me to remember to do so?


I normally wait until it is accepted by the ftp-masters. Feel free to 
ping me on private mail.

Bug#976113: RFS Review for Hydrogen

[Ross Gammon]

Hi Sebastian,

On 07/01/2021 11:06, Sebastian Ramacher wrote:
> The *.desktop and appdata files belong to the package that provides the
> executable (except for some corner cases). In particular, having the
> appdata file in hydrogen-data instructs the consumers of those files to
> install hydrogen-data if somebody wants to install hydrogen. They are
> non-functional if installing hydrogen-data without also installing
> hydrogen. So please move them to hydrogen.

Good point - well made.

Don't worry Nicholas. I can take care of that to avoid another mentors
upload round trip.

-- 
Regards,

Ross Gammon
FBEE 0190 904F 1EA0 BA6A  300E 53FE 7BBD A689 10FC



signature.asc
Description: OpenPGP digital signature

Bug#976113: RFS Review for Hydrogen

[Ross Gammon]

Hi Nicholas,

On 06/01/2021 18:12, Nicholas D Steeves wrote:
> Hi Ross,
> 
> Sorry for the delay, so tired and busy here!
>

Me too!

> Ross Gammon  writes:
> 
>> Please note, I was not able to do a test installation to check hydrogen
>> is working. I hope you can confirm that.
>>
> 
> I can confirm it works for everything I use it for, but unfortunately I
> don't have any midi gear to test midi-related functionality.
> 
>> Blocking upload:
>> 1. The package fails to build twice in a row (I used the --twice option
>> in pdebuild). It appears some translation files are not being cleaned
>> after the first build.
>>
> 
> Thank you for spotting this.  I've activated a build hook to catch cases
> like this in the future.  Fixed, and fixed an assumption I had made
> about the translations.
> 
>> Minor things:
>> 1. We could enable Salsa CI by adding a debian/salsa-ci.yml file.
> 
> We could, but I don't think Hydrogen's test is significant enough to
> make it worthwhile to spin up an instance every time someone pushes to
> the repo (cost of resources, and cost of carbon footprint).

No problems. But you also get other tests like reproducibility and
piuparts tests for free, which you should otherwise do manually to avoid
issue with an upload. :-)

> 
>> 2. I think the copyright-hints & check files can be removed as they were
>> used by cdbs?
> 
> Done, queued for the source-only -2 upload
> 
>> 3. The github issues page could be added to the upstream metadata
>> file.
> 
> Is this user facing?  I have been specifically omitting this from my
> packages, because I worry that it will make it more convenient for the
> user to click and report upstream, despite "Don't file bugs upstream" 
> (https://www.debian.org/Bugs/Reporting).

Yes, there are a few public facing tools that use this information. And
I always think a report in the wrong place is better than no report :-)

> 
>> 4. I am not sure what is going on with the icon. There is a lot going on
>> in d/rules and also a patch. This is probably something that should be
>> sorted out upstream. As a minimum we should probably forward our patch
>> upstream or tag the patch as "Forwarded: not-needed" if it is not an
>> upstream issue. I note that in Ubuntu, they install an svg into the
>> pixmaps folder.
> 
> Yeah, it's confusing to me too, and yes, ought to be solved upstream.
> The png (erroneously named as a bmp) is used internally for something,
> and I'm not sure using the svg in that context would succeed, but it
> seems like it ought to be.  The SVGs we install are:
> 
> usr/share/hydrogen/data/img/gray/h2-icon.svg
> usr/share/hydrogen/data/img/gray/icon.svg
> usr/share/hydrogen/data/img/gray/warning.svg
> usr/share/icons/hicolor/scalable/apps/org.hydrogenmusic.Hydrogen.svg
> 
>> 5. Patch 2001 should probably be tagged as "Forwarded: not-needed" as it
>> seems Debian specific.
> 
> Done.  Queued for -2.
> 
>> 6. I see that even with all hardening options enabled in d/rules, we
>> still get the "hardening no fortify" lintian error. Are there some flags
>> not being passed to the build system?
> 
> Possibly.  I will investigate and plan to solve this for -2.
> 
>> 7. I see the large number of commits to add library packages and upload
>> pre-release versions has resulted in some churn in the changelog. I
>> think some entries can be removed now that we have agreed to upload a
>> simpler structure and because it is a proper release (e.g. disabling the
>> documentation)?
>>
> 
> I believe I cut the bin:lib-pkg ones, but I see I missed the docs ones.
> Fixed.
> 
>> Suggestions/Considerations:
>> 1. It is worth taking a look at the version of hydrogen uploaded in
>> Ubuntu by Erich Eickmeyer. By adding ladspa-sdk and libtar as build
>> dependencies (and a patch), it appears that the hydrogen builds with
>> extra options.
> 
> I considered enabling new features, but chose to change the package as
> little as possible, because we're so late in the bullseye cycle.  I'm of
> course open to enabling them if someone else will thoroughly test the
> features.
> 
>> Erich also switched the jack dependency to jack2.
> 
> When building with libjack-dev, debhelper should indirectly generate a
> dependency on libjack-jackd2-0 | libjack-0.125.  My rational for not
> switching is that I'm aware of users of older Firewire interfaces who
> prefer (or need) jack and not jack2.  I also asked #debian-multimedia
> for confirmation that sticking with jack was consistent with team policy
> and received a firm statement to not switch to bui

Bug#976113: RFS Review for Hydrogen

[Ross Gammon]

Hi Nicholas,

Good stuff. I think we are just about ready to upload. Here are the
comments from my review.

Please note, I was not able to do a test installation to check hydrogen
is working. I hope you can confirm that.

Blocking upload:
1. The package fails to build twice in a row (I used the --twice option
in pdebuild). It appears some translation files are not being cleaned
after the first build.

Minor things:
1. We could enable Salsa CI by adding a debian/salsa-ci.yml file.
2. I think the copyright-hints & check files can be removed as they were
used by cdbs?
3. The github issues page could be added to the upstream metadata file.
4. I am not sure what is going on with the icon. There is a lot going on
in d/rules and also a patch. This is probably something that should be
sorted out upstream. As a minimum we should probably forward our patch
upstream or tag the patch as "Forwarded: not-needed" if it is not an
upstream issue. I note that in Ubuntu, they install an svg into the
pixmaps folder.
5. Patch 2001 should probably be tagged as "Forwarded: not-needed" as it
seems Debian specific.
6. I see that even with all hardening options enabled in d/rules, we
still get the "hardening no fortify" lintian error. Are there some flags
not being passed to the build system?
7. I see the large number of commits to add library packages and upload
pre-release versions has resulted in some churn in the changelog. I
think some entries can be removed now that we have agreed to upload a
simpler structure and because it is a proper release (e.g. disabling the
documentation)?

Suggestions/Considerations:
1. It is worth taking a look at the version of hydrogen uploaded in
Ubuntu by Erich Eickmeyer. By adding ladspa-sdk and libtar as build
dependencies (and a patch), it appears that the hydrogen builds with
extra options. Erich also switched the jack dependency to jack2.
2. I see we have added a lintian override for the desktop and appdata
files not being in the same package as the executable. Is there a reason
for not just installing the desktop/appdata files with the executable
instead of in -data?

-- 
Regards,

Ross Gammon
FBEE 0190 904F 1EA0 BA6A  300E 53FE 7BBD A689 10FC



signature.asc
Description: OpenPGP digital signature

Bug#976113: Bug#954823: Sponsorship of hydrogen

[Ross Gammon]

Hi Nicholas,

Dropped one of the bugs from "To:" (leaving only the RFS copied in).

On 30/12/2020 00:55, Nicholas D Steeves wrote:
> Hi Ross,
>
> Ross Gammon  writes:
>
>> I have spent some time going through the commit messages. There has
>> been a lot of work done!
> Yes :-)  If I remember correctly, cdbs -> dh, and upstream churn between
> prereleases was the worst of it.
>
>
> Will do!  The WIP branch is called "rfs-976113-rebase" and I pushed it
> just now; it doesn't contain much yet.  I will update mentors as soon as
> we have an upload candidate (still too many outstanding big issues at
> this time).

>> I was wondering why the library packages suddenly appeared. I think if
>> it is possible, it is best to stick to the old packages. What
>> applications would want to use hydrogen as a library?
>>
> Hypothetical 3rd party plugins, I think?  Unfortunately even with
> -DWANT_SHARED=OFF we still end up with libhydrogen-core-1.0.1.a, which
> appears to have not been installed in the 0.9.7 series of Debian
> packages.  I can whitelist and ignore it, but for comparison to other
> distributions, OpenSUSE chose to ship the lib:
>
> https://software.opensuse.org/package/libhydrogen-core0 (for 0.9.7)
> https://software.opensuse.org/package/libhydrogen-core1 (for 1.0.1)
>
> Also, I'm also not sure if there is any practical benefit to
> hydrogen-dev (hypothetical plugin development), so I'm wondering if the
> headers should not be installed; they weren't installed in the last
> release (0.9.7-6).  Hydrogen-dev_1.0.1-1_all.deb is only 84KB, so could
> be merged into libhydrogen-core-1.0.1.  Sebastinas says the -dev package
> is arch-specific, and if that's the case it seems like merging the -dev
> package into bin:libhydrogen-core-1.0.1 would be reasonable.
>
> There is something to be said the principle of least surprise when
> moving between distributions, but I don't have a position on way or the
> other.
>
> At this time we can also reassess the hydrogen and hydrogen-data split.
> If I was packaging Hydrogen from scratch I'm not sure that I would split
> them...
>
> Finally, if we maintain the split, what is your position on .desktop and
> appdata files?  Should they go in bin:hydrogen-data, or in bin:hydrogen?

OK - I think we are a bit too close to the next Debian release to be
making things complicated. Maintaining a library complicates upgrades to
new versions if transitions are required, and can be problematic if the
the ABI is not stable. I don't know how stable the hydrogen library is.
Why don't we just stick to how it was structured before it was removed?
That way users of Hydrogen in making music (like me) can just use the
application like they used to.

We have to go through the NEW queue to get hydrogen into the next
release, so making the ftp-master review as simple as possible (with a
rock solid copyright file) is the least risky approach.

I think the main reason for splitting stuff out into a *-data package is
to split the architecture dependent files from the architecture
independent files. When looking at the contents of the old hydrogen
package, you could question some of the decisions between the -data and
-doc packages.

Maybe after the release we can think about helping developers of
potential plugins, and moving files around between packages? That is
unless the previous structural decisions contributed to any bugs!

We can always backport new versions for users of Debian stable after the
release if there is a demand.



>
> I've reopened this list of bugs.
>
>> Let me know when the new version is available on mentors.
>>
> Will do!  I'd just want to take care of the major design decisions
> first.
>
> Cheers,
> Nicholas

Cheers,

Ross




signature.asc
Description: OpenPGP digital signature

Bug#976113: Bug#954823: Sponsorship of hydrogen

[Ross Gammon]

Hi Nicholas,

I have spent some time going through the commit messages. There has been
a lot of work done!

On 29/12/2020 17:29, Nicholas D Steeves wrote:
> Hi Ross!
>
> Ross Gammon  writes:
>
>> owner 954823 rossgam...@debian.org
>> thanks
>>
>> Hi Nicholas,
>>
>> I am happy to take a look at hydrogen, and sponsor it. I have some spare
>> time over the next few days.
>>
> Thank you, I really appreciate this! :-D  Here are some notes and
> questions:
>
> Will you be sponsoring from git or mentors?  How would you like me to
> work during the WIP cycles of the review?  The git history will look a
> bit silly and confusing with too many "refinalise for release to
> unstable" commits ;-)

I can do either. But I think in this case, I would prefer to work from
mentors (mainly because I have problems with my gbp setup on this
computer). But please also keep the git repository in sync (even if it
is on a different branch that we can merge later).

Actually, I would like to compliment you on your commit messages. It was
pleasing to see a verbose reason for the change, instead of some short
cryptic message that just generates more questions.

I think it is best to keep a record of the review in the RFS bug. So I
have cc'd the RFS bug (sorry - I did not spot it when I started), and we
can continue the discussion there.

>
> On #debian-multimedia, Sebastinas did a preliminary review, and two big
> issues were:
>
> 1. override_dh_auto_build had a typo! "override_override_dh_auto_build"
>*   I've fixed this locally
> 2. I was missing an override_dh_auto_configure to make use of
>$DEB_CMAKE_EXTRA_FLAGS
>* I believe that is why the extra lib and dev packages became
>  necessary.  Now that I know what was causing the problem I can
>  restore something closer to the old packaging.
>* Changing this in the future will require another trip through NEW,
>  so what do you think the correct split of the package is?

I was wondering why the library packages suddenly appeared. I think if
it is possible, it is best to stick to the old packages. What
applications would want to use hydrogen as a library?


> 3. override_dh_auto_clean failed to run "dh_auto_clean".  Oops :-/

This might explain why I found that the package failed to build twice in
a row for me.


> I've already make local fixes for these and other issues, but will delay
> pushing until I receive your preference regarding the shared lib and dev
> packages.  I'm of course open to fixing other issues and removing
> anything you consider vestigial to the old cdbs packaging (I chose the
> more labour-intensive approach rather than clean packaging)!
>
>> Have you reopened any bugs that were closed when the package was removed?
>> https://www.debian.org/doc/manuals/developers-reference/pkgs.html#reintroducing-packages
>>
> I have not yet reopened any bugs.  The list of -rm bugs is:
>   945042 642014 629105 870395 794042 586087 874907 347279 945042
>
> There seem to be differences in perspective about when/if these bugs
> should be reopened.  My preference is to maintain a strong link between
> the changelog and BTS, for future reference, and for future
> maintainers.  Given "changelog closes bugs in wrong way", I feel like
> reopening the bugs that will be closed by the yet-to-be-uploaded
> changelog entry is the correct approach, because it creates a strong
> link between the changelog and BTS.

I think the best thing is to reopen the bug and then close them in the
changelog once it is confirmed that they are closed. That way they are
closed with the right version information. The most important thing is
to ensure that bugs that are not fixed in the new version remain open.

Let me know when the new version is available on mentors.

Ross




signature.asc
Description: OpenPGP digital signature

Re: Understanding "pending uploads"

[Ross Gammon]

Hi Sepi,

On 10/03/2020 18:17, Sepi Gair wrote:
> Sorry, I thought this is a common name for the specific state of
> upload.
>
> There is the source package liblms7compact listed on my QA page[1]. It
> placed in the section named "Pending uploads".
>
> 1. https://qa.debian.org/developer.php?login=sepigair%40email.cz
>
> On Tue, 2020-03-10 at 21:59 +0500, Andrey Rahmatullin wrote:
>> On Tue, Mar 10, 2020 at 05:57:15PM +0100, Sepi Gair wrote:
>>> Hello,
>>>
>>> I've got a sponsor for my package, the package now is pending for
>>> upload. 
>> What do you mean?
>>
Your package is new to Debian, and is sitting in the NEW queue. It is a
manual process where the ftpmaster team check the package for suitability.

https://ftp-master.debian.org/new.html

-- 

Regards,

Ross Gammon
OpenPGP fingerprint FBEE 0190 904F 1EA0 BA6A  300E 53FE 7BBD A689 10FC

I will generally always sign my emails so that you know it is me.
Please encrypt mails to me that contain sensitive information.
See https://www.gnupg.org/ for information.




signature.asc
Description: OpenPGP digital signature

Re: package one package from a git repo with multiple packages

[Ross Gammon]

Hi Rosea,

On 09/03/2020 16:37, Andrey Rahmatullin wrote:
> On Mon, Mar 09, 2020 at 03:20:26PM +0100, rosea.grammostola wrote:
>>> You just need to create a source tarball that is able to build the project
>>> you need. For that you'll need to find out which common files are also
>>> needed.
>>> You'll need to do it manually each time you need to upload a new version,
>>> so I guess you'll want to create a script that helps with that.
>>> There are no specific recommendations because this is almost never needed.
>>
>> First, thanks for your help!
>>
>> Wouldn't this be done most easily with git?
>>
>> - Git cloning the whole repository
>>
>> - Git remove the parts which are not needed
>>
>> - Do a git tag in that reworked repo, to make tarball?
>>
>> - Package from there
>>
>> ?
> If after that you are going to merge the upstream repo master you'll get
> conflicts for all changed stuff that you deleted. But whatever works for
> you.
> 

If you just want to package non-session-manager, why not:
1. Download the tarball from here:
https://git.tuxfamily.org/non/non.git/tag/?id=non-session-manager-v1.2.0
(or the github mirror - whichever is best)
2. Extract the tarball.
3. Begin packaging in the extracted directory
4. Create a git repo & push the files into a Salsa git repo once you are
happy you have something mostly working.

It only makes sense to package from a clone of the upstream repository
if you are (eventually) going to create binary packages for all the
non-* applications in the one source package.

You can always package the other applications separately by downloading
their tarballs when you have the urge. Then each source package can use
the debian/watch file to watch for new tarballs in the same upstream git
repository.

But if you prefer the git approach, then there are several ways you can
package from the upstream git repository (including without a tarball).
Some methods are listed in the git-buildpackage manual:
https://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.import.upstream-git.html

Keep going!

-- 
Regards,

Ross Gammon
FBEE 0190 904F 1EA0 BA6A  300E 53FE 7BBD A689 10FC



signature.asc
Description: OpenPGP digital signature

Re: Fix a watchfile to pick up alpha releases etc.

[Ross Gammon]

On 07/04/2018 09:16 PM, Ross Gammon wrote:
> Hi,
> 
> I have been having some fun with a watchfile for a github project where
> I would like uscan to pickup the recent alpha, beta and rc releases. The
> package is Gramps:
> https://salsa.debian.org/debian/gramps
> 
> Upstream are putting the "alpha" bit after a "-" (e.g. v5.0.0-rc1) as
> recomended by github, and I can't find a way to get the uversionmangle
> to work after much trial and error, and much searching of
> codesearch.debian.net.
> 
> Can anyone put me out of my misery?
> 
> Cheers,
> 
> Ross
> 

False alarm. Don't waste your time. It wasn't a uversionmangle issue, it
was the filenamemangle & URL line that had the mistakes. Using the
examples for github on https://wiki.debian.org/debian/watch (instead of
the weird version I had) makes all the difference.

I helps to stop and have a drink sometimes!

Ross



signature.asc
Description: OpenPGP digital signature

Fix a watchfile to pick up alpha releases etc.

[Ross Gammon]

Hi,

I have been having some fun with a watchfile for a github project where
I would like uscan to pickup the recent alpha, beta and rc releases. The
package is Gramps:
https://salsa.debian.org/debian/gramps

Upstream are putting the "alpha" bit after a "-" (e.g. v5.0.0-rc1) as
recomended by github, and I can't find a way to get the uversionmangle
to work after much trial and error, and much searching of
codesearch.debian.net.

Can anyone put me out of my misery?

Cheers,

Ross



signature.asc
Description: OpenPGP digital signature

Re: Problem with Git Push

[Ross Gammon]

On 01/04/2018 05:05 PM, Gianfranco Costamagna wrote:
> I don't see any collab-maint on salsa
> 

From salsa announcement:

"Collab-maint


If you want to allow other Debian Developers to work on your packages or
software, you can create projects within the
**Debian** group. Every Debian Developer has write access to projects
created in this group.
If you create a project within the Debian group, you are implicitly
welcoming all DDs to contribute directly to the project.

Guest users can only be added to individual projects with the Debian
group, but not to the entire Debian group. This is different to the
policy for the collab-maint group on Alioth."

> https://salsa.debian.org/debian/cligh

So that URL seems the right place for packages that would have gone in
the old collab-maint on Alioth.

Cheers,

Ross



signature.asc
Description: OpenPGP digital signature

Re: BTS and unreleased changelog entries

[Ross Gammon]

On 10/15/2017 05:36 AM, Ross Vandegrift wrote:
> Good question.  I guess I think of a changelog as history - so changes I
> made on 1.15 go with 1.15 whether it was released or not.  But if I
> think of the changelog as telling others about changes in a release,
> then it makes sense to squash them.

It sounds like you need to maintain your packages in a Version Control
system (e.g. git).

That will give you plenty of history about your changes/tests/debugging.

As you say, the changelog is for telling others what changed between
releases.

Cheers,

Ross



signature.asc
Description: OpenPGP digital signature

Bug#867727: RFS: parlatype/1.5.2-1 [ITP]

[Ross Gammon]

Control: tags -1 moreinfo

Hi Gabor,

Good work. We are nearly there!

The only thing I spotted, was the lack of a docbase file to help people
fire up the docs locally:
https://www.debian.org/doc/manuals/maint-guide/dother.en.html#doc-base

Would you like to maintain this within the Debian Multimedia Team? If so:
https://wiki.debian.org/DebianMultimedia/Join
and then follow the stuff in the Develop Packaging link there (to create
the git repository etc).
We can always do this before the next upload if you prefer. Just let me
know.

Some minor things we can work on for next time:
1. Lintian complains about there being no upstream changelog. As you are
upstream, maybe you can fix this? It is a nice service to our users to
see what changed in each version without going online. The Debian
changelog only contains changes in the packaging.
2. It would be nice to add some autopkgtests. For parlatype, that might
just be to run the binary command without a file to check that it
installs & doesn't crash. For the library & gir library you can compile
a simple app against the libraries to check they compile & run OK. If
you search on Debian Codesearch you will find examples.

Regards,

Ross



signature.asc
Description: OpenPGP digital signature

Bug#867727: RFS: parlatype/1.5.2-1 [ITP]

[Ross Gammon]

Control: owner -1 rossgam...@debian.org

Thanks Juhani for the excellent review, and thanks Gabor for your patience.

I plan to take a look at parlatype over the weekend.

Cheers,

Ross




signature.asc
Description: OpenPGP digital signature

Bug#867727: Request for sponsoring Parlatype -- audio player for transcription

[Ross Gammon]

Hi Gabor,

On 08/24/2017 11:13 AM, Gabor Karsay wrote:
> Dear Debian Multimedia Maintainers,
>
> I'm looking for a reviewer or sponsor of my package Parlatype which is
> a minimal audio player that helps you to transcribe speeches,
> interviews, lyrics etc. It's based on GStreamer and GTK+.
>
> It shows the waveform of the audio and I am not aware of any other
> comparable tool in Debian that does that. A similar program is
> Play-it-slowly, but Parlatype offers helpers for transcription, like
> timestamps (drag'n'drop), rewind on pause etc.
>
> Just to clarify: I'm also the upstream author. I filed already ITP and
> RFS bugs here:
>
> ITP: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868886
> RFS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867727
>
> I was not aware of the multimedia packaging team before, my first
> intent was to maintain it myself, i.e. not in a team. I hope that
> somebody from this team is interested and can give me some guidance
> how to proceed.
>
> Thank you
> Gabor Karsay
>
> ___
> pkg-multimedia-maintainers mailing list
> pkg-multimedia-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
>

I would be happy to take a look at this. Unfortunately, I am quite busy
at the moment so I can't promise much this week.

I have cc'd you because you did not say whether you are subscribed to
the Multimedia list. I have also copied in the RFS bug so that other
potential sponsors see this and take over if they are looking for
something to do :-)

Regards,

Ross

Autopkgtest for goocanvas

[Ross Gammon]

Hi Mentors,

Now that lintian reminds me every time, I feel guilty and I am trying to
provide an autopkgtest for goocanvas-2.0.

The problem is that my lack of C foo is letting me down. So far (cribbed
from other examples on debian codesearch), I have the following skeleton
of a smoke test:

---
#!/bin/sh
set -e

cd "$ADTTMP"
cat > test.c << EOF
#include 

int main(void)
{
goo_canvas_new();
return 0;
}

EOF
gcc -Wall -o test test.c $(pkg-config --cflags goocanvas-2.0) \
$(pkg-config --libs goocanvas-2.0)
./test
objdump -p test | grep "goocanvas-2.0"
-

I have tried umpteen different variations of a "main" function based on
the goocanvas docs:
https://developer.gnome.org/goocanvas/unstable/index.html

Running ./test crashes every time :-)

Can someone please put me out of my misery, and suggest a short bit of
code to create a simple goocanvas item?

In the mean time, I will create one for the gir package (I am a bit more
comfortable with python).

Regards,

Ross



signature.asc
Description: OpenPGP digital signature

Bug#866736: RFS: budgie-desktop/10.2.9-3

[Ross Gammon]

On 07/01/2017 05:27 PM, foss.freedom wrote:
> Sorry - I didnt really understand about filing a bug against
> release.debian.org targeting "p-u" - I had a look here but didnt see
> an example https://www.debian.org/Bugs/Reporting

There is a bit more background information in the Developers Reference
about uploading to stable:
https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#upload-stable

It is best to use the reportbug tool to report the bug, as it helps to
make sure you provide all the necessary info.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866759 for a good
example of what the bug should look like.

Cheers,

Ross



signature.asc
Description: OpenPGP digital signature

pkg-ruby-extras scripts [Was: Re: Sbuild & lxc problems]

[Ross Gammon]

Bringing query about the pkg-ruby-extras scripts on mentors list to
debian-ruby. I would like to finally get sbuild & lxc set up on my
Jessie machine so I can use the pkg-ruby-extras script, and I hope that
Josch can help with some improvements to the script for sbuild.

Hi Josch,

Thanks for taking the time to respond to all that!

On 06/25/2017 08:50 AM, Johannes Schauer wrote:
> Hi Ross,
> 
> sbuild maintainer here. :)
> 
> Quoting Ross Gammon (2017-06-23 21:18:13)
>> I mainly use pbuilder/cowbuilder to build my packages, but I would
>> really like to try using the tool from pkg-ruby-extras, because I am
>> told it is very good for test building reverse dependencies and also
>> runs debci to test any autopkgtest testsuites. It uses sbuild.
> 
> pkg-ruby-extras? The alioth group? What is "the tool" you are referring to? If
> this part of your question is ruby specific, then maybe the debian-ruby list 
> is
> a better fit?

You found the tool below :-)

> 
>> However, sbuild does not seem to agree with me, and I have had several
>> attempts over the years to get it going but I gave up each time.
> 
> Please help by filing bugs with the problems you faced! I am aware that many
> things are not well documented that but to make the software better I need to
> know which things need more explanation.
> 

I will do - it was only a lack of time that stopped me before. And also
knowing that it was probably mostly user error.



>> I: Base system installed successfully.
>> I: Configured /usr/sbin/policy-rc.d:
>>+
>>|#!/bin/sh
>>|echo "All runlevel operations denied by policy" >&2
>>|exit 101
>>+
>> I: Configured APT /etc/apt/sources.list:
>>+
>>|deb http://httpredir.debian.org/debian unstable main
>>|deb-src http://httpredir.debian.org/debian unstable main
>>+
>> I: Please add any additional APT sources to
>> /srv/chroots/unstable-amd64-sbuild/etc/apt/sources.list
>> modprobe: FATAL: Module overlay not found.
>> I: schroot chroot configuration written to
>> /etc/schroot/chroot.d/unstable-amd64-sbuild-GlcVID.
>>+
>>|[unstable-amd64-sbuild]
>>|description=Debian unstable/amd64 autobuilder
>>|groups=root,sbuild
>>|root-groups=root,sbuild
>>|profile=sbuild
>>|type=directory
>>|directory=/srv/chroots/unstable-amd64-sbuild
>>|union-type=none
>>+
>> I: Please rename and modify this file as required.
>> W: Not creating symlink /srv/chroots/unstable-amd64-sbuild to
>> /etc/sbuild/chroot/unstable-amd64-sbuild: file already exists
> 
> This is troublesome. It appears you already had a chroot set up?
> 

Yes - probably - I have had many unsuccessful goes at it in the past on
different machines, and I can never remember where I got to.

$ schroot -l
E: /etc/schroot/chroot.d/unstable-amd64-sbuild-GlcVID: line 1
[unstable-amd64-sbuild]: A chroot or alias
‘chroot:unstable-amd64-sbuild’ already exists with this name
I: Duplicate names are not allowed

>> I: Setting reference package list.
>> I: Updating chroot.
>> Err:1 http://httpredir.debian.org/debian unstable InRelease
>>   Temporary failure resolving 'httpredir.debian.org'
>> Reading package lists... Done 
>> W: Failed to fetch
>> http://httpredir.debian.org/debian/dists/unstable/InRelease  Temporary
>> failure resolving 'httpredir.debian.org'
>> W: Some index files failed to download. They have been ignored, or old
>> ones used instead.
> 
> Problem with the network connection?

I don't think so - maybe a regular/intermittent problem with the
redirections? I wonder if it is a good idea to use httpredir anyway. It
appears to be discontinued: https://wiki.debian.org/DebianGeoMirror
Perhaps I should log into the chroot & manually change the sources.list?

> 
>> Reading package lists... Done Building dependency tree  Reading state
>> information... Done Calculating upgrade... Done
>> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>> I: Successfully set up unstable chroot.
>> I: Run "sbuild-adduser" to add new sbuild users.
>> + grep -l ^union-type=
>> /etc/schroot/chroot.d/unstable-amd64-sbuild-GlcVID
>> /etc/schroot/chroo

Sbuild & lxc problems

[Ross Gammon]

I mainly use pbuilder/cowbuilder to build my packages, but I would
really like to try using the tool from pkg-ruby-extras, because I am
told it is very good for test building reverse dependencies and also
runs debci to test any autopkgtest testsuites. It uses sbuild.

However, sbuild does not seem to agree with me, and I have had several
attempts over the years to get it going but I gave up each time. One
time I thing I ran out of room on the root partition halfway through
setting it up (my fault). Once I had fixed the space problem, I had all
sorts of problems working out how to clear out the failed sbuild schroot
(and I can't remember how I did it now). Then the next time I think it
failed with some gpg archive key problem. I got around this by upgrading
to sbuild from jessie-backports. But then it failed for some reason I
can't remember. It is difficult to search for help when everything seems
to be a wrapper for something else, and you can't workout where in the
chain the problem is. I have been around in circles several times :-)

Anyway, that is the background. I am hoping that with some help from
mentors, I will get up and running this time. Here goes:

-

ross@DebianJessieLaptop:~/debian/pkg-ruby-extras$ git remote -v
origin   
https://anonscm.debian.org/cgit/pkg-ruby-extras/pkg-ruby-extras.git (fetch)
origin   
https://anonscm.debian.org/cgit/pkg-ruby-extras/pkg-ruby-extras.git (push)

ross@DebianJessieLaptop:~/debian/pkg-ruby-extras$ setup
+ sudo apt-get install -qy autopkgtest build-essential gem2deb git
git-buildpackage myrepos quilt sbuild lxc debci

+ sudo mkdir -p /root/.gnupg
+ sudo sbuild-update --keygen
Generating archive key.

Not enough random bytes available.  Please do some other work to give
the OS a chance to collect more entropy! (Need 188 more bytes)
.+
.+
gpg: /root/.gnupg/trustdb.gpg: trustdb created
gpg: key 5F4C78AD marked as ultimately trusted
+ sudo sbuild-adduser ross
The user `ross' is already a member of `sbuild'.

# Setup tasks for sudo users:

# BUILD
# HOME directory in chroot, user:sbuild, 0770 perms, from
# passwd/group copying to chroot, filtered
# Maybe source 50sbuild, or move into common location.

Next, copy the example sbuildrc file to the home directory of each user and
set the variables for your system:

  cp /usr/share/doc/sbuild/examples/example.sbuildrc /home/ross/.sbuildrc

Now try a build:

  cd /path/to/source
  sbuild-update -ud 
  (or "sbuild-apt  apt-get -f install"
   first if the chroot is broken)
  sbuild -d  _
+ dpkg --print-architecture
+ chrootname=unstable-amd64-sbuild
+ chroot=/srv/chroots/unstable-amd64-sbuild
+ grep unstable-amd64-sbuild
+ schroot --list --all-source-chroots
+ sudo sbuild-createchroot unstable /srv/chroots/unstable-amd64-sbuild
http://httpredir.debian.org/debian
I: SUITE: unstable
I: TARGET: /srv/chroots/unstable-amd64-sbuild
I: MIRROR: http://httpredir.debian.org/debian
I: Running debootstrap --arch=amd64 --variant=buildd --verbose
--include=fakeroot,build-essential --components=main --resolve-deps
unstable /srv/chroots/unstable-amd64-sbuild
http://httpredir.debian.org/debian
I: Retrieving Release
I: Retrieving Release.gpg
I: Checking Release signature
I: Valid Release signature (key id 126C0D24BD8A2942CC7DF8AC7638D0442B90D010)
I: Retrieving Packages
I: Validating Packages


I: Base system installed successfully.
I: Configured /usr/sbin/policy-rc.d:
   +
   |#!/bin/sh
   |echo "All runlevel operations denied by policy" >&2
   |exit 101
   +
I: Configured APT /etc/apt/sources.list:
   +
   |deb http://httpredir.debian.org/debian unstable main
   |deb-src http://httpredir.debian.org/debian unstable main
   +
I: Please add any additional APT sources to
/srv/chroots/unstable-amd64-sbuild/etc/apt/sources.list
modprobe: FATAL: Module overlay not found.
I: schroot chroot configuration written to
/etc/schroot/chroot.d/unstable-amd64-sbuild-GlcVID.
   +
   |[unstable-amd64-sbuild]
   |description=Debian unstable/amd64 autobuilder
   |groups=root,sbuild
   |root-groups=root,sbuild
   |profile=sbuild
   |type=directory
   |directory=/srv/chroots/unstable-amd64-sbuild
   |union-type=none
   +
I: Please rename and modify this file as required.
W: Not creating symlink /srv/chroots/unstable-amd64-sbuild to
/etc/sbuild/chroot/unstable-amd64-sbuild: file already exists
I: Setting reference package list.
I: Updating chroot.
Err:1 http://httpredir.debian.org/debian unstable InRelease
  Temporary failure resolving 'httpredir.debian.org'
Reading package lists... Done  

Bug#848912: RFS: node-file-sync-cmp/0.1.1-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist
Tags: l10n

Dear mentors,

I am looking for a sponsor for my package "node-file-sync-cmp"

* Package name: node-file-sync-cmp
  Version : 0.1.1-1
  Upstream Author : Martin Geisler <mar...@geisler.net> (http://geisler.net/)
* URL : https://github.com/mgeisler/file-sync-cmp/
* License : Expat
  Section : web

It builds this binary package:

node-file-sync-cmp - Synchronous file comparison

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

  https://mentors.debian.net/package/node-file-sync-cmp


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

dget -x https://mentors.debian.net/debian/pool/main/n/node-file-sync-cmp
/node-file-sync-cmp_0.1.1-1.dsc

Debian packaging can be found here:
https://anonscm.debian.org/cgit/pkg-javascript/node-file-sync-cmp.git

Changes since the last upload:

  * Initial release (Closes: #845025)


Regards,
Ross Gammon



-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-24-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Re: Maintaining C++ library symbols control file with unstable mangled symbols

[Ross Gammon]

On 02/12/16 18:11, Jérémy Lal wrote:

2016-12-02 18:08 GMT+01:00 Ghislain Vaillant :

On 02/12/16 16:36, lumin wrote:

Hi mentors,

I need advise on the way maintaining symbols control file when
the mangled C++ symbols are unstable.

I'm maintaining a package named "Caffe". I migrated the same
source from experimental to unstable, and it FTBFS'ed as you
see at [0], due to the mangled C++ symbols change. Actually
this package FTBFS'ed many times in the history due to
symbols change. (I have no e.g. ppc64el machine, hence
unable to test before upload)


Stopping you right there. Maintaining C++ symbols is notoriously painful,
and I was advised back in my early packaging days to just avoid it.

Perhaps things have changed since, and other people might disagree.

dh-acc and abi-compliance-checker might help you maintain your own
soname. Nothing guaranteed, though.

Jérémy



In the Debian GIS Team we have quite a few C++ library packages where 
the symbols are managed using pkgkde_symbolshelper 
(https://pkg-kde.alioth.debian.org/symbolfiles.html).


It involves a trip via experimental to pickup all the symbol changes on 
all architectures that are built for experimental by the buildd machines.


Cheers,

Ross

Bug#845797: RFS: gramps/4.2.4~dfsg-1~bpo8+1

[Ross Gammon]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking to begin backporting Gramps. I have already done that in Ubuntu a
few times, but feel guilty for not doing the same in Debian. As Gramps is NEW
to jessie-backports, I am asking for a sponsor to do the first upload for me.

I have been added to the ACL for backports, have subscribed to the backports
list, and plan to continue backporting as long as possible.

* Package name: gramps
  Version : 4.2.4~dfsg-1~bpo8+1
  Upstream Author : The Gramps Project
* URL : https://gramps-project.org/
* License : GPL-2
  Section : gnome

It builds this binary package:

gramps - Genealogical research program

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

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

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

dget -x
https://mentors.debian.net/debian/pool/main/g/gramps/gramps_4.2.4~dfsg-1~bpo8+1.dsc

Debian packaging is available here:
https://anonscm.debian.org/cgit/collab-maint/gramps.git

You will need to checkout the jessie-backports branch in the git repo. Then
with a jessie cowbuilder chroot set up, I used the following incantation to
ensure the changes file has all the changelog entries
since jessie:
$ gbp buildpackage --git-pbuilder --git-dist=jessie -v4.1.1~dfsg-3

Changes since the last upload:

  * Rebuild for jessie-backports.
  * Update branch in gbp.conf & Vcs-Git URL.


Regards,
Ross Gammon



-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-24-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#844995: RFS: node-object-inspect/1.1.0-1 [RFP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-object-inspect"

* Package name: node-object-inspect
  Version : 1.1.0-1
  Upstream Author : James Halliday <m...@substack.net> (http://substack.net)
* URL : https://github.com/substack/object-inspect
* License : Expat
  Section : web

It builds this binary package:

node-object-inspect - string representations of objects in node and the browser

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

https://mentors.debian.net/package/node-object-inspect


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

dget -x https://mentors.debian.net/debian/pool/main/n/node-object-inspect/node-
object-inspect_1.1.0-1.dsc

Debian packaging can be found here:
https://anonscm.debian.org/cgit/pkg-javascript/node-object-ispect.git

Changes since the last upload:

  * Initial release (Closes: #814284)


Regards,
Ross Gammon



-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-24-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#844769: RFS: node-resumer/0.0.0-1 [RFP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-resumer"

 * Package name: node-resumer
   Version : 0.0.0-1
   Upstream Author : James Halliday<m...@substack.net>  (http://substack.net)
 * URL :https://github.com/substack/resumer
 * License : Expat
   Section : web

It builds this binary package:

node-resumer  - a through stream that starts paused and resumes on the
 next tick

Unfortunately, it is not possible for me to upload to mentors at the moment.

But the packaging can be found here:

https://anonscm.debian.org/cgit/pkg-javascript/node-resumer.git/

Changes since the last upload:
|

  * Initial release (Closes: #814286)

|Regards,
Ross Gammon

Bug#844565: RFS: node-husl/6.0.1+dfsg-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-husl"

* Package name: node-husl
  Version : 6.0.1+dfsg-1
  Upstream Author : Alexei Boronine <ale...@boronine.com>
* URL : http://www.husl-colors.org/
* License : Expat
  Section : web

It builds these binary packages:

libjs-husl - Human-friendly HSL - Javascript
node-husl  - Human-friendly HSL - NodeJS

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

https://mentors.debian.net/package/node-husl


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

dget -x https://mentors.debian.net/debian/pool/main/n/node-husl/node-
husl_6.0.1+dfsg-1.dsc

Debian packaging can be found here:
https://anonscm.debian.org/cgit/pkg-javascript/node-husl.git

Changes since the last upload:

  * Initial release (Closes: #844230)


Regards,
Ross Gammon



-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-24-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Re: Bug#800406: RFS sayonara/0.8.2

[Ross Gammon]

Hi Lucio,

On 09/19/2016 11:13 PM, Lucio Carreras wrote:
> Hi Ross,
> 
> Maybe you remember, I currently see no chance to go on preparing
> Sayonara player for the Debian repositories. I simply don't have enough
> time. The distribution mechanism for Debian is complicated and when I
> find time again after a few weeks I have to start from the very
> beginning again. It's very time consuming and I cannot imagine how to
> handle this in the future. I'll go on uploading the program to the ppa
> and offer the source code on my website. Maybe there will be someone in
> the future who wants to take care of this task.
> 
> I have a lot of respect for all of you how to manage this all beside
> your jobs.

No problems. We all know how you feel sometimes - especially when
starting out. If I ever get a spare moment, I will take a look and see
if I can finish the package off and get it sponsored myself.

Once it is in the Debian archive, it is quite easy to maintain from that
point, as the workflow begins to stick in the brain. So I hope you will
keep an eye on the package in Debian, and re-consider later on.

Keep up the good work on the package upstream!

Ross



signature.asc
Description: OpenPGP digital signature

Bug#836569: RFS: node-js-yaml/3.6.1+dfsg-1 [RFP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-js-yaml"

* Package name: node-js-yaml
  Version : 3.6.1+dfsg-1
  Upstream Author : Dervus Grim <dervus.g...@gmail.com>
* URL : https://github.com/nodeca/js-yaml
* License : Expat
  Section : web

It builds this binary package:

node-js-yaml - YAML 1.2 parser and serializer

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

  https://mentors.debian.net/package/node-js-yaml


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

dget -x https://mentors.debian.net/debian/pool/main/n/node-js-yaml/node-js-
yaml_3.6.1+dfsg-1.dsc

For Debian packaging, it will eventually be found here:
https://anonscm.debian.org/cgit/pkg-javascript/node-js-yaml.git

Changes since the last upload:

 * Initial release (Closes: #805411)


Regards,
Ross Gammon



-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-24-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#835671: RFS: node-inline-source-map/0.6.1-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-inline-source-map"

* Package name: node-inline-source-map
  Version : 0.6.1-1
  Upstream Author : Thorsten Lorenz <thlor...@gmx.de> (http://thlorenz.com)
* URL : https://github.com/thlorenz/inline-source-map
* License : Expat
  Section : web

It builds this binary package:

node-inline-source-map - base64 encoded source mappings for a generated file

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

https://mentors.debian.net/package/node-inline-source-map


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

dget -x https://mentors.debian.net/debian/pool/main/n/node-inline-source-map
/node-inline-source-map_0.6.1-1.dsc

Packaging can be obtained from:
https://anonscm.debian.org/cgit/pkg-javascript/node-inline-source-map.git

Changes since the last upload:

  * Initial release (Closes: #795114)


Regards,
Ross Gammon



-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-24-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Re: Bug#800406: RFS sayonara/0.8.2

[Ross Gammon]

On 05/22/2016 10:03 AM, Ross Gammon wrote:
> The package is still building here,

OK- Lintian has some complaints:
+++ lintian output +++
P: sayonara source: debian-watch-may-check-gpg-signature

As you are "upstream" this could probably be fixed, but can be left for
the sometine in the future.

I: sayonara: hardening-no-pie usr/bin/sayonara
I: sayonara: hardening-no-bindnow usr/bin/sayonara
I: sayonara: hardening-no-bindnow usr/lib/sayonara/libsayonara_somafm.so
I: sayonara: hardening-no-bindnow usr/lib/sayonara/libsayonara_soundcloud.so

Assuming the build system supports it, we should be able to enable these
hardening options. See: https://wiki.debian.org/Hardening

P: sayonara: no-upstream-changelog

You have an upstream changelog in the resources directory. This could be
installed by overriding dh_install_changelogs. You can always do an
internet search, or use https://codesearch.debian.net/ to find examples
of how it is done.

I: sayonara: description-synopsis-might-not-be-phrased-properly

Hopefully my suggestions in the last email make this go away.

W: sayonara: command-in-menu-file-and-desktop-file sayonara
usr/share/menu/sayonara:6

See:
https://lintian.debian.org/tags/command-in-menu-file-and-desktop-file.html

E: sayonara: postinst-does-not-call-updatemenus usr/share/menu/sayonara

This MUST be fixed before upload, as I think is will cause an automatic
rejection of the package? See:
https://lintian.debian.org/tags/postinst-does-not-call-updatemenus.html
Probably fixing the previous warning will make this go away.

 and I would like to install it and
> have a little play. Assuming nothing goes wrong with that, with the
> above changes I think it is ready to ask a sponsor to take a look at it.

This test will have to wait now as I must be somewhere else for a few hours.

Cheers,

Ross



signature.asc
Description: OpenPGP digital signature

Re: Bug#800406: RFS sayonara/0.8.2

[Ross Gammon]

Hi Lucio,

On 05/13/2016 04:05 PM, Ross Gammon wrote:
> 
> Sorry - I was a bit busy this week. If Gianfranco says we are mostly
> done, then it is probably time to join the pkg-multimedia team! Please
> follow this page to join:
> https://wiki.debian.org/DebianMultimedia/Join
> 
> Once I see saynora pushed to the alioth git repository, I will build,
> install and have a play. If all looks good, it is probably time to
> update the RFS bug to let Gianfranco know that we think it is ready for
> sponsorship.

Now we have sayonara inside the Debian Multimedia repository, I think
there are only a few small things to tidy up:

1. Debian tag: Unfortunately when you import a .dsc, a Debian tag is
created against the debian (master) branch. This tag should reflect the
state of the repository when the package is uploaded. As sayonara has
not been uploaded yet, we should delete this tag (no-one else will have
pulled it yet, so no danger).
$ git push --delete origin debian/0.9.0-1
$ git tag -d debian/0.9.0-1
According to https://wiki.debian.org/DebianMultimedia/DevelopPackaging,
after upload the sponsor should tag the repository (sometimes it is
forgotten, so keep an eye out for that).

2. Maintainer: Also according to
https://wiki.debian.org/DebianMultimedia/DevelopPackaging, the
maintainer should be the Team, and interested team members (e.g. you)
should be "Uploader". Please update debian/control.

3. Package Short Description: This should start with "small" rather than
"Small" and does not need the full stop at the end (debian/control).
See:
https://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#bpp-desc-basics

4. Package Long Description: This looks like a list "It holds a lot of
features like .". It would be better if each new line in the list
started with "* ". Alternatively, it could be a standard paragraph with
lots of commas (e.g. It holds a lot of features like many supported
music and playlist formats, directory view, ). I think I prefer the
list.

5. Now that sayonara is in the Debian Multimedia Team repository, we
need Vcs fields in debian/control:
Vcs-Git: https://anonscm.debian.org/git/pkg-multimedia/sayonara.git
Vcs-Browser: https://anonscm.debian.org/cgit/pkg-multimedia/sayonara.git
This way, people can follow links from the package tracker to inspect
the repository, or find out how to clone it.

The package is still building here, and I would like to install it and
have a little play. Assuming nothing goes wrong with that, with the
above changes I think it is ready to ask a sponsor to take a look at it.

Regards,

Ross



signature.asc
Description: OpenPGP digital signature

Re: Bug#800406: RFS sayonara/0.8.2

[Ross Gammon]

Hi Lucio,

On 05/11/2016 12:28 PM, Gianfranco Costamagna wrote:
>> >So the next step will be to join the multimedia-team?
> 
> please join it now, and put VCS fields under your package.
> (and ask me to create the repository if you want one)
> 
> I see some packages under pkg-multimedia umbrella have no VCS repository, so 
> I guess
> you can avoid that, because you seem to already be upstream

Sorry - I was a bit busy this week. If Gianfranco says we are mostly
done, then it is probably time to join the pkg-multimedia team! Please
follow this page to join:
https://wiki.debian.org/DebianMultimedia/Join

Once I see saynora pushed to the alioth git repository, I will build,
install and have a play. If all looks good, it is probably time to
update the RFS bug to let Gianfranco know that we think it is ready for
sponsorship.

Regards,

Ross




signature.asc
Description: OpenPGP digital signature

Re: Bug#800406: RFS sayonara/0.8.2

[Ross Gammon]

Hi Lucio,

On 05/04/2016 11:25 AM, Lucio Carreras wrote:
> Hello Gianfranco, hello Ross,
> 
> unfortunately, the last message went to my spam folder so I just saw it
> today. Gianfranco, thank you for having a look at the package. I will
> correct those errors. But you are right, there are some some packaging
> problems anyway.

I had wondered... You are welcome to ask here on the mentors list if any
of the packaging problems are proving difficult to fix. Don't be
embarrassed - we have all asked stupid questions here, and learnt from
other peoples questions. Glad it was the Spam folder and not the too
hard basket :-)

> 
>>> gstreamer1.0-plugins-ugly, libqt5sql5-sqlite < -- aren't them picked up by 
>>> shibs:Depends?
> 
> Those libraries are loaded on runtime. The program will start without
> them, but it won't work as intended. They are not available because the
> build process does not depend on them.

OK. Looked strange to me too once Gianfranco mentioned it (especially
the sqlite library), but seems reasonable.

> 
>>>please just call dh_auto_configure and patch the build system to 
>>>automatically take care of the flags.
>>>
>>>I think all the rules hacks can be dropped.
> There was a reason for including these rules. But I'll try to get rid of
> them.
> 
> And thank you Ross for supporting the package. I guess, I'll need your
> help from time to time.

Sure. Once the package is almost ready for upload, I recommend joining
the Debian Multimedia Team and maintaining the package there (in their
git repository). I would be happy to co-maintain it with you. I will be
hoping that you get so good at it that you won't need much help after a
while :-)

Cheers,

Ross



signature.asc
Description: OpenPGP digital signature

Bug#818100: RFS: node-seq/0.3.5-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-seq"

* Package name: node-seq
  Version : 0.3.5-1
  Upstream Author : James Halliday <m...@substack.net> (http://substack.net)
* URL : https://github.com/substack/node-seq
* License : Expat
  Section : web

It builds those binary packages:

node-seq   - Chainable asynchronous flow control

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

  http://mentors.debian.net/package/node-seq


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

dget -x http://mentors.debian.net/debian/pool/main/n/node-seq/node-
seq_0.3.5-1.dsc

The packaging can be found here:
http://anonscm.debian.org/cgit/pkg-javascript/node-seq.git/

Changes since the last upload:

  * Initial release (Closes: #802008)


Regards,
Ross Gammon



-- System Information:
Debian Release: 8.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#816552: RFS: node-json-localizer/0.0.3-1 [RFP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-json-localizer"

* Package name: node-json-localizer
  Version : 0.0.3-1
  Upstream Author : Yohan Boniface
* URL : https://github.com/yohanboniface/json-localizer/
* License : WTFPL
  Section : web

It builds this binary package:

node-json-localizer - Utility to localize a json object

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

  http://mentors.debian.net/package/node-json-localizer


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

dget -x http://mentors.debian.net/debian/pool/main/n/node-json-localizer
/node-json-localizer_0.0.3-1.dsc

Debian packaging can be found here:
http://anonscm.debian.org/cgit/pkg-javascript/node-json-localizer.git

Changes since the last upload:

  * Initial release (Closes: #805413)


Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers wily-updates
  APT policy: (500, 'wily-updates'), (500, 'wily-security'), (500, 'wily'), 
(100, 'wily-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-30-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#816191: RFS: node-function-bind/1.1.0-1 [RFP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-function-bind"

* Package name: node-function-bind
  Version : 1.1.0-1
  Upstream Author : Jake Verbaten <rayn...@gmail.com>
* URL : https://github.com/Raynos/function-bind
* License : Expat
  Section : web

It builds this binary package:

node-function-bind - Implementation of Function.prototype.bind

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

  http://mentors.debian.net/package/node-function-bind


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

dget -x http://mentors.debian.net/debian/pool/main/n/node-function-bind
/node-function-bind_1.1.0-1.dsc

Debian packaging can be found here:
http://anonscm.debian.org/cgit/pkg-javascript/node-function-bind.git/

Changes since the last upload:

  * Initial release (Closes: #814281)


Regards,
Ross Gammon



-- System Information:
Debian Release: 8.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Re: Bug#800406: RFS sayonara/0.8.2

[Ross Gammon]

Hi Lucio,

Sorry I did not spot this email after talking you into contacting Debian
Mentors :-)

I am not a Debian Developer, so I cannot sponsor the package, but I will
write some comments inline below that will hopefully help you on your way.

On 02/15/2016 11:30 AM, Lucio Carreras wrote:
> Dear Debian mentors,
> 
> I am looking for a sponsor for the package "sayonara".
> 
> * Package name: sayonara
> * Version: 0.8.2
> * Author: Lucio Carreras  >
> * Url: http://www.sayonara-player.com
> * License: GPL3
> * Section: audio
> 
> Sayonara is a clear and fast audio player with its main focus on
> managing your music library. There are many features for library
> organization, like a tag editor or a special genre view. It also has
> tabbed playlists, handles webstreams and podcasts, has a stream
> recorder, a Soundcloud plugin and much more.
> 
> 
> There's a git repository at
> 
> https://git.sayonara-player.com/sayonara.git

I have cloned your git repo to do the review, but in the future, I
recommend that you sign up for an account on Debian Mentors, and upload
your package there. This has some advantages:
1. Some sponsors are used to this workflow and prefer to take packages
from there (at least the first time)
2. You go through a similar process to what you will go through when you
are eventually granted upload permisions (it is good practise for later)
3. The web interface gives a sponsor a good indication of the health of
the package (e.g. number of lintian warnings) without having to download it.

See Section 4 of mentors.debian.net/intro-maintainers

> There also exist a Ubuntu PPA
> (https://launchpad.net/~lucioc/+archive/ubuntu/sayonara) and so there
> also exist Debian packages (available at the download section). The
> source code in the git repository also contains a debian directory with
> all neccessary files. It is also tested regularly with a Debian unstable
> chroot, if there are any warnings or errors.

This is a good sign. Some more detailed comments:

debian/changelog:
- As this will be the first upload to Debian, it is best that the
changelog has one simple entry "Initial Release (Closes: #)". This will allow the bug to be automatically closed when the
package is uploaded to the archive. See
https://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#bpp-debian-changelog
- You have set the distribution to stable. New packages should always
target "unstable". It will automatically migrate from there to "testing"
(if there are no problems), and then one day be released as part of the
next stable release.

debian/control
- I recommend joining the Debian Multimedia Team eventually. Then the
Vcs fields can be finalised (surrently commented out). But lets improve
the packaging a little bit more first.
- A space between "Description:" and the short description would be nice
- The long description should probably start with "Sayonara" rather than
"Its" because it will not be clear if read without the short description.

debian/copyright
- The "License:" stanza should be the short name of the license (e.g.
GPL-3+).
- Then the complete license text should be included at the bottom.
See https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/

debian/rules
- I was a bit surprised to so much stuff in debian/rules, as most of the
time the common build systems don't need a lot more than:
%:
dh $@
It might be worth looking at tweaking your cmake build system (as you
are also upstream) so that it is not necessary to override the clean,
build & install targets in debian/rules. This would probably benefit
other non Debian based Linux Distros as well. Probably not critical -
depending on the sponsor though.

You are missing a watch file. This file watches for new tarballs on your
website, and alerts everyone when there is a new version waiting to be
packaged. See https://wiki.debian.org/debian/watch/

debian/README.Debian? This should probably be deleted. You will find a
sponsor much faster if you promise to maintain Saynora yourself (or in a
team). :-)

debian/md5sums - I am not sure this file is needed if building the
package happens the normal way with debhelper?

debian/license.txt - a license.txt in the root of the sourcecode, and
the summarised in debian/copyright should be enough. Please remove this
file.

The package is currently building. I will let you know later if there
are problems with that.

I hope that helps you on the way. If there is something in all that
which is not clear, or you need more help to fix it, just ask on the list.

Keep up the good work, and thanks for taking an interest in getting
Sayonara into Debian proper.

Regards,

Ross



signature.asc
Description: OpenPGP digital signature

Bug#815024: RFS: autotalent/0.2-5

[Ross Gammon]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: autotalent
  Version : 0.2-5
  Upstream Author : Thomas A. Baran <tba...@mit.edu>
* URL : http://tombaran.info/autotalent.html
* License : BSD-3-clause
  Section : sound

It builds this binary package:

autotalent - pitch correction LADSPA plugin

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

  http://mentors.debian.net/package/autotalent


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

dget -x
http://mentors.debian.net/debian/pool/main/a/autotalent/autotalent_0.2-5.dsc

Debian packaging can be found in the Debian Multimedia Team repository:
http://anonscm.debian.org/cgit/pkg-multimedia/autotalent.git

Changes since the last upload:

  * Change uploader from Alessio to me & update Vcs URLs
  * Improve package long description
Thanks to Justin B Rye (Closes: #785260)
  * Bump standards version, no changes required
  * Fix watch file

Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers wily-updates
  APT policy: (500, 'wily-updates'), (500, 'wily-security'), (500, 'wily'), 
(100, 'wily-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-25-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#814662: RFS: tweepy/3.5.0-1 [RC]

[Ross Gammon]

Package: sponsorship-requests
Severity: important

Dear mentors,

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

 * Package name: tweepy
   Version : 3.5.0-1
   Upstream Author : Joshua Roesslein <jroessl...@gmail.com>
 * URL : http://www.tweepy.org/
 * License : MIT
   Section : python

It builds these binary packages:

 python-tweepy - Twitter library for Python
 python-tweepy-doc - Documentation for python-tweepy module
 python3-tweepy - Twitter library for Python 3

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

  http://mentors.debian.net/package/tweepy


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

dget -x
http://mentors.debian.net/debian/pool/main/t/tweepy/tweepy_3.5.0-1.dsc

The Debian packaging can be found here:
https://anonscm.debian.org/cgit/python-modules/packages/tweepy.git

Changes since the last upload:

  * Team upload
  * New upstream release
  * Disable upstream tests (Closes: #804558)
The tests fail as they need internet access
  * Use secure URL for Vcs
  * Make Python 3 package short description unique


Regards,
Ross Gammon



-- System Information:
Debian Release: 8.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#813917: RFS: node-leaflet-formbuilder/0.2.1-1 [ITP]

[Ross Gammon]

Thanks Bas for the fast review.

On 06/02/16 18:02, Sebastiaan Couwenberg wrote:

Hi Ross,

Thanks for your work kosmtik and its dependencies.

I've reviewed the package, and it needs a few changes.

Please update the Source URL in the copyright file to use the URL from
the watch file, the homepage link is not as appropriate for the
copyright file.


Source URL now points at the source.


The Bug-* URLs in upstream/metadata need to be fixed too.


It appears I forgot to run $ duck :-(
Fixed (also in d/control)



Also consider filing an issue upstream to have them include a proper
license file, the only reference to the license is package.json which is
a bit sparse.

Kind Regards,

Bas


https://github.com/yohanboniface/Leaflet.FormBuilder/issues/4
I will now do a pull request.

I assume you are OK with taking the latest from git (I have not 
re-uploaded to mentors).


Cheers,

Ross

Bug#813917: RFS: node-leaflet-formbuilder/0.2.1-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-leaflet-formbuilder"

* Package name: node-leaflet-formbuilder
  Version : 0.2.1-1
  Upstream Author : Yohan Boniface
* URL : https://github.com/yohanboniface/Leaflet.FormBuilder#readme
* License : WTFPL
  Section : web

It builds this binary package:

node-leaflet-formbuilder - Helpers to build forms in Leaflet

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

  http://mentors.debian.net/package/node-leaflet-formbuilder


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

dget -x http://mentors.debian.net/debian/pool/main/n/node-leaflet-
formbuilder/node-leaflet-formbuilder_0.2.1-1.dsc

Debian packaging can be found here:
http://anonscm.debian.org/cgit/pkg-grass/node-leaflet-formbuilder.git

Changes since the last upload:


  * Initial release (Closes: #805415)


Regards,
Ross Gammon



-- System Information:
Debian Release: 8.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#809401: RFS: node-isarray/1.0.0-1

[Ross Gammon]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "node-isarray"

* Package name: node-isarray
  Version : 1.0.0-1
  Upstream Author : Julian Gruber <m...@juliangruber.com>
(http://juliangruber.com)
* URL : https://github.com/juliangruber/isarray
* License : Expat
  Section : web

It builds this binary package:

node-isarray - JavaScript Array#isArray for older browsers

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

  http://mentors.debian.net/package/node-isarray


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

dget -x http://mentors.debian.net/debian/pool/main/n/node-isarray/node-
isarray_1.0.0-1.dsc

The Debian packaging is available here:
http://anonscm.debian.org/cgit/pkg-javascript/node-isarray.git

Changes since the last upload:

  * New upstream release
  * Override dh_auto_build & test targets


Regards,
Ross Gammon



-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#809407: RFS: node-isstream/0.1.2+dfsg-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-isstream"

* Package name: node-isstream
  Version : 0.1.2+dfsg-1
  Upstream Author : Rod Vagg <r...@vagg.org>
* URL : https://github.com/rvagg/isstream
* License : Expat
  Section : web

It builds this binary package:

node-isstream - Determine if an object is a Stream

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

  http://mentors.debian.net/package/node-isstream


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

dget -x http://mentors.debian.net/debian/pool/main/n/node-isstream/node-
isstream_0.1.2+dfsg-1.dsc

The Debian packaging can eventually be found here:
http://anonscm.debian.org/cgit/pkg-javascript/node-isstream.git

Changes since the last upload:

  * Initial release (Closes: #802012)
  * Patch README.md to fix spelling

Regards,
Ross Gammon



-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#808823: RFS: node-cross-spawn-async/2.1.1-1

[Ross Gammon]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "node-cross-spawn-async"

* Package name: node-cross-spawn-async
  Version : 2.1.1-1
  Upstream Author : Indigo United <he...@indigounited.com>
* URL : https://github.com/IndigoUnited/node-cross-spawn-async
* License : Expat
  Section : web

It builds this binary package:

node-cross-spawn-async - Cross platform child_process#spawn

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

  http://mentors.debian.net/package/node-cross-spawn-async


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

dget -x http://mentors.debian.net/debian/pool/main/n/node-cross-spawn-async
/node-cross-spawn-async_2.1.1-1.dsc

The Debian packaging can be found here:
https://anonscm.debian.org/cgit/pkg-javascript/node-cross-spawn-async.git

Changes since the last upload:

  * New upstream release
  * Refresh patches
  * Add node-rimraf build dependency for tests & patch the new test

Regards,
Ross Gammon



-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Re: guitarix package in debian

[Ross Gammon]

On 12/18/2015 08:26 PM, Hermann Meyer wrote:
> 
> 
> Am 18.12.2015 um 18:28 schrieb Víctor Cuadrado Juan:
>> Hi,
>>
>> Thanks again Hermann for looking after the status of the package
>> in Debian :).
>>
>> I have already sent an email to Guitarix's Debian maintainer, Roland
>> Stigge, to see if he keeps being interested on maintaining it (CC
>> m...@qa.debian.org), in case someone was also thinking on pinging him
>> and CCing MIA.

I might just do that in the next few weeks.

>> On 11/12/15 16:58, Hermann Meyer wrote:

[...]

>> I will try to have an NMU ready this weekend before it gets autoremoved.
>> If someone beats me to it, I will be happy too :).


> Great to hear that you've take the ball.
> If you've any trouble or needs help/clarification from upstream, let me
> know.
> I'll be there. :-)

If Roland is indeed MIA, then I would love to see guitarix moved into
the Debian Multimedia Team where it could benefit from more people to
take care of it (including me).

Regards,

Ross



signature.asc
Description: OpenPGP digital signature

Bug#808354: RFS: node-core-util-is/1.0.2-1

[Ross Gammon]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "node-core-util-is"

* Package name: node-core-util-is
  Version : 1.0.2-1
  Upstream Author : Isaac Z. Schlueter <i...@izs.me>
* URL : https://github.com/isaacs/core-util-is
* License : Expat
  Section : web

It builds this binary package:

node-core-util-is - util.is* functions introduced in Node v0.12 for older
versions

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

  http://mentors.debian.net/package/node-core-util-is


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

dget -x http://mentors.debian.net/debian/pool/main/n/node-core-util-is
/node-core-util-is_1.0.2-1.dsc

The Debian packaging can be found here:
http://anonscm.debian.org/cgit/pkg-javascript/node-core-util-is.git

Changes since the last upload:

  * New upstream release
  * Update copyright due to new LICENSE file added upstream
  * Use https for Vcs Browser URL
  * Enable new tests provided by upstream
  * Patch upstream test to require assert instead of tap
  * Unapply patches from source

Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers wily-updates
  APT policy: (500, 'wily-updates'), (500, 'wily-security'), (500, 'wily'), 
(100, 'wily-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-19-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#808092: RFS: osm-gps-map/1.1.0-1

[Ross Gammon]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "osm-gps-map"

* Package name: osm-gps-map
  Version : 1.1.0-1
  Upstream Author : John Stowers <john.stow...@gmail.com>
* URL : https://github.com/nzjrs/osm-gps-map
* License : GPL-2
  Section : science

It builds these binary packages:

gir1.2-osmgpsmap-1.0 - GTK+ library to embed OpenStreetMap maps - Python
bindings
libosmgpsmap-1.0-1 - GTK+ library to embed OpenStreetMap maps
libosmgpsmap-1.0-dbg - GTK+ library to embed OpenStreetMap maps - debugging
symbols
libosmgpsmap-1.0-dev - GTK+ library to embed OpenStreetMap maps - development
files

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

  http://mentors.debian.net/package/osm-gps-map


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

dget -x http://mentors.debian.net/debian/pool/main/o/osm-gps-map/osm-gps-
map_1.1.0-1.dsc

The Debian packaging is available here:
http://anonscm.debian.org/cgit/pkg-grass/osm-gps-map.git

Changes since the last upload:

  [ Ross Gammon ]
  * New upstream release (LP: #1507381)
  * Refresh patch
  * Update copyright file
  * Drop lintian override as it is no longer required
  * Rename -dev & -dbg packages
  * Add Conflict and Replace for renamed packages
  * Switch to dh_autoreconf
  * Update debian/clean file
  * Reinstate d-shlibmove & add option for unversioned -dev package
  * Install built docs instead of source ones
  * Enable parallel builds
  * Drop README.source as quilt is now well known

  [ Bas Couwenberg ]
  * Update library & package name in symbols file for SONAME bump.
  * Use symbol version without debian revision.
  * Update symbols for version 1.1.0.
  * Update Vcs-Browser URL to use HTTPS.


Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers wily-updates
  APT policy: (500, 'wily-updates'), (500, 'wily-security'), (500, 'wily'), 
(100, 'wily-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-19-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Re: guitarix package in debian

[Ross Gammon]

Hi Hermann,

On 12/08/2015 09:59 AM, Hermann Meyer wrote:
> Hello
> 
> I'm the upstream maintainer of the guitarix project, and I've noticed
> that guitarix is marked as autoremoval in debian/testing because of this
> bug:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805666
> 
> The bug mentioned above is fixed in upstream since some time, as I'm
> myself been a debian/sid user.
> 
> I've tried to reach the debian maintainer (Roland Stigge) of the
> guitarix project for some time now, to no avail.
> To avoid the removal, just a new upload of the latest version is needed,
> so I like to ask here, if someone her could do that?

Thanks for helping to take care of guitarix in Debian as well as upstream.

I see on the bug you have correctly tagged it as fixed upstream.

Unfortunately, it sometimes happens that a maintainer goes missing (most
of the time only temporarily). But it is not cool to just take over and
upload a new version.
There is some information here about maintainers that are missing in action:
https://wiki.debian.org/Teams/MIA

As upstream, you could further help by adding a link in the Debian BTS
to the upstream commit that fixes the bug, or attach a patch.

Then someone could more easily do a Non Maintainer Upload (NMU) to keep
guitarix in debian testing (or get it back there after removal).

Regards,

Ross



signature.asc
Description: OpenPGP digital signature

Re: Bug#805656: RFS: node-leaflet-hash/0.2.1-1 [ITP]

[Ross Gammon]

On 11/20/2015 09:16 PM, Sebastiaan Couwenberg wrote:
> Hi Ross,
> 
> Thanks for your work on this package.
> 
> On 20-11-15 20:25, Ross Gammon wrote:
>> I am looking for a sponsor for my package "node-leaflet-hash"
> 
> I pushed some changes to document the license & copyright for the
> embedded copy of leaflet-src.js, and update the Vcs-Browser URL to use
> HTTPS.
> 
> Why do you install lib/leaflet-src.js?

npm2deb did it for me!

> 
> It seems to be included only for its use in test/index.html, and that
> test isn't used by the package. I don't think this files needs to be
> installed, and if it does libjs-leaflet should be used instead.

Hmmm. I think you might be right. A libjs-leaflet package probably
should be added, with the test directory installed so users can run the
test in the browser. README.md is not to helpful on this, so I will give
it a go and report back.

> Kind Regards,
> 
> Bas
> 

Thank you :-)



signature.asc
Description: OpenPGP digital signature

Bug#805656: RFS: node-leaflet-hash/0.2.1-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-leaflet-hash"

* Package name: node-leaflet-hash
  Version : 0.2.1-1
  Upstream Author : Michael Lawrence Evans
* URL : https://github.com/mlevans/leaflet-hash
* License : Expat
  Section : web

It builds this binary package:

node-leaflet-hash - linkable location hashes for leaflet

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

  http://mentors.debian.net/package/node-leaflet-hash


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

dget -x http://mentors.debian.net/debian/pool/main/n/node-leaflet-hash
/node-leaflet-hash_0.2.1-1.dsc

The Debian packaging is available here:
http://anonscm.debian.org/cgit/pkg-javascript/node-leaflet-hash.git

Changes since the last upload:

  * Initial release (Closes: #694137)


Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-31-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Re: Bug#805656: RFS: node-leaflet-hash/0.2.1-1 [ITP]

[Ross Gammon]

On 11/20/2015 09:30 PM, Ross Gammon wrote:
> On 11/20/2015 09:16 PM, Sebastiaan Couwenberg wrote:

[...]

>> I pushed some changes to document the license & copyright for the
>> embedded copy of leaflet-src.js, and update the Vcs-Browser URL to use
>> HTTPS.
>>
>> Why do you install lib/leaflet-src.js?
> 
> npm2deb did it for me!
> 
>>
>> It seems to be included only for its use in test/index.html, and that
>> test isn't used by the package. I don't think this files needs to be
>> installed, and if it does libjs-leaflet should be used instead.
> 
> Hmmm. I think you might be right. A libjs-leaflet package probably
> should be added, with the test directory installed so users can run the
> test in the browser. README.md is not to helpful on this, so I will give
> it a go and report back.

Scratch that. I missed your words above - "embedded copy of
leaflet-src.js". We already have libjs-leaflet in the archive, so
another package of the same name is not a good idea!

As we can't run a HTML test in the browser during the build, your first
suggestion of not installing the embedded copy may be better.

Cheers,

Ross



signature.asc
Description: OpenPGP digital signature

Bug#804451: RFS: node-concat-stream/1.5.1-1 [ITP]

[Ross Gammon]

Whoops- Filled in properly below:

On 11/08/2015 05:56 PM, Ross Gammon wrote:
> * Package name: node-concat-stream
>   Version : 1.5.1-1
>   Upstream Author : [fill in name and email of upstream]
> * URL : [fill in URL of upstreams web site]
> * License : [fill in]
>   Section : web

* Package name: node-concat-stream
  Version : 1.5.1-1
  Upstream Author : Max Ogden <m...@maxogden.com>
* URL : https://github.com/maxogden/concat-stream#readme
* License : Expat
  Section : web



signature.asc
Description: OpenPGP digital signature

Bug#804451: RFS: node-concat-stream/1.5.1-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-concat-stream"

* Package name: node-concat-stream
  Version : 1.5.1-1
  Upstream Author : [fill in name and email of upstream]
* URL : [fill in URL of upstreams web site]
* License : [fill in]
  Section : web

It builds this binary package:

node-concat-stream - writable stream that concatenates strings

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

  http://mentors.debian.net/package/node-concat-stream


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

dget -x http://mentors.debian.net/debian/pool/main/n/node-concat-stream
/node-concat-stream_1.5.1-1.dsc

Debian packaging can be found be found here:
http://anonscm.debian.org/cgit/pkg-javascript/node-concat-stream.git

Changes since the last upload:

  * Initial release (Closes: #796351)


Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-31-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#804252: RFS: node-readable-stream/2.0.3-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-readable-stream"

* Package name: node-readable-stream
  Version : 2.0.3-1
  Upstream Author : Streams WG Team <christopher.s.dickin...@gmail.com>
* URL : https://github.com/nodejs/readable-stream#readme
* License : Expat
  Section : web

It builds this binary package:

node-readable-stream - Streams3, a user-land copy of the stream library from
iojs v2.x

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

http://mentors.debian.net/package/node-readable-stream


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

dget -x http://mentors.debian.net/debian/pool/main/n/node-readable-stream/node-
readable-stream_2.0.3-1.dsc

Debian packaging can be found here:
http://anonscm.debian.org/cgit/pkg-javascript/node-readable-stream.git

Changes since the last upload:

  * Initial release (Closes: #796355)


Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-31-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#803979: RFS: node-string-decoder/0.10.25-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-string-decoder"

* Package name: node-string-decoder
  Version : 0.10.25-1
  Upstream Author : Rod Vagg <r...@va.gg>
* URL : https://github.com/rvagg/string_decoder
* License : Expat
  Section : web

It builds this binary package:

node-string-decoder - string_decoder module from Node core for browsers

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

http://mentors.debian.net/package/node-string-decoder


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

dget -x http://mentors.debian.net/debian/pool/main/n/node-string-decoder/node-
string-decoder_0.10.25-1.dsc

The Debian packaging can be found here:

http://anonscm.debian.org/cgit/pkg-javascript/node-string-decoder.git

Changes since the last upload:

  [ Bas Couwenberg ]
  * Initial release (Closes: #779998)

Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-31-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#802603: RFS: node-defined/1.0.0-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-defined"

* Package name: node-defined
  Version : 1.0.0-1
  Upstream Author : James Halliday <m...@substack.net> (http://substack.net)
* URL : https://github.com/substack/defined
* License : Expat
  Section : web

It builds this binary package:

node-defined - return the first argument that is `!== undefined`

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

  http://mentors.debian.net/package/node-defined


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

dget -x http://mentors.debian.net/debian/pool/main/n/node-defined/node-
defined_1.0.0-1.dsc

Debian packaging can be found here:
http://anonscm.debian.org/cgit/pkg-javascript/node-defined.git/

Changes since the last upload:

  * Initial release (Closes: #802595)


Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-30-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#802516: RFS: node-util-deprecate/1.0.2-1

[Ross Gammon]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "node-util-deprecate"

* Package name: node-util-deprecate
  Version : 1.0.2-1
  Upstream Author : Nathan Rajlich <nat...@tootallnate.net> (http://n8.io/)
* URL : https://github.com/TooTallNate/util-deprecate
* License : MIT
  Section : web

It builds this binary package:

node-util-deprecate - Node.js's `util.deprecate()` function with browser
support

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

http://mentors.debian.net/package/node-util-deprecate


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

dget -x http://mentors.debian.net/debian/pool/main/n/node-util-deprecate/node-
util-deprecate_1.0.2-1.dsc

The Debian packaging can be found here:
https://anonscm.debian.org/cgit/pkg-javascript/node-util-deprecate.git/

Changes since the last upload:

 * New upstream release


Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-30-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#802529: RFS: node-deep-equal/1.0.1-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-deep-equal"

* Package name: node-deep-equal
  Version : 1.0.1-1
  Upstream Author : James Halliday <m...@substack.net> (http://substack.net)
* URL : https://github.com/substack/node-deep-equal#readme
* License : Expat
  Section : web

It builds this binary package:

node-deep-equal - node's assert.deepEqual algorithm

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

  http://mentors.debian.net/package/node-deep-equal


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

dget -x http://mentors.debian.net/debian/pool/main/n/node-deep-equal/node-
deep-equal_1.0.1-1.dsc

Debian packaging can be found here:
http://anonscm.debian.org/cgit/pkg-javascript/node-deep-equal.git

Changes since the last upload:

  * Initial release (Closes: #802518)


Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-30-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

watch file mangling help

[Ross Gammon]

Hi,

Upstream have changed one of my package's versioning on the tarball
(http://anonscm.debian.org/cgit/collab-maint/abcmidi.git).

The last uploaded version was 20150908 and now there is an upstream
tarball with the version "2015.10.08".

The watch file was simple:
version=3
opts=uversionmangle=s/-//g \
http://ifdo.pugmarks.com/~seymour/runabc/top.html abcMIDI-(.*)\.zip

But now a uscan --repack tells me that:
Newest version on remote site is 2015.10.08, local version is 20150908
 => remote site does not even have current version

I am not sure what I should be mangling here, uversionmangle, or
dversionmangle, or both.

Before I just download the tarball manually and be done with it, I
thought I would check if someone could help with a more elegant solution.

Cheers,

Ross



signature.asc
Description: OpenPGP digital signature

Re: watch file mangling help

[Ross Gammon]

On 10/17/2015 12:38 PM, Jakub Wilk wrote:
> On Sat, Oct 17, 2015 at 11:55 AM, Ross Gammon <r...@the-gammons.net> wrote:

[...]

>>> The last uploaded version was 20150908 and now there is an upstream
>>> tarball with the version "2015.10.08".
>>>
>>> The watch file was simple:
>>> version=3
>>> opts=uversionmangle=s/-//g \
>>> http://ifdo.pugmarks.com/~seymour/runabc/top.html abcMIDI-(.*)\.zip
>>>
>>> But now a uscan --repack tells me that:
>>> Newest version on remote site is 2015.10.08, local version is 20150908
>>> => remote site does not even have current version
>>>

[...]

> The upstream versioned was 2013-09-15, and you had uversionmangle rule
> to get rid of hyphens.
> 
> All you need to do is to update the uversionmangle rule so that it gets
> rid of dots instead.

Thanks Jakub. Sometime you don't see something when it is staring you in
the face!

> * Pau Garcia i Quiles <pgqui...@elpauer.org>, 2015-10-17, 12:19:
>> Why are you keeping the old versioning scheme if upstream has changed
>> to a different scheme?

Jakub's simple fix works, and I have asked upstream what the intentions
are going forward. But I probably should remove both hyphens and dots to
be sure!



signature.asc
Description: OpenPGP digital signature

Bug#801449: RFS: node-isarray/0.0.1-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-isarray"

* Package name: node-isarray
  Version : 0.0.1-1
  Upstream Author : Julian Gruber <m...@juliangruber.com>
(http://juliangruber.com)
* URL : https://github.com/juliangruber/isarray
* License : Expat
  Section : web

It builds this binary package:

node-isarray - JavaScript Array#isArray for older browsers

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

http://mentors.debian.net/package/node-isarray

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

dget -x http://mentors.debian.net/debian/pool/main/n/node-isarray/node-
isarray_0.0.1-1.dsc

The Debian packaging can be found here:
http://anonscm.debian.org/cgit/pkg-javascript/node-isarray.git

Changes since the last upload:

  [ Bas Couwenberg ]
  * Initial release (Closes: #780001)


Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-30-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#801449: RFS: node-isarray/0.0.1-1 [ITP]

[Ross Gammon]

Hi Gianfranco,

On 10/10/2015 12:25 PM, Gianfranco Costamagna wrote:
> Control: owner -1 !
> 
> Control: tags -1 moreinfo
> 
> Hi Ross, the package is a little bit small indeed :)
> 
> Do you have any written down sentence from an ftpmaster that the package will 
> pass
> the new queue now?
> 
> I don't want to reupload the package and get another rejection, I would like 
> to read
> a statement where the ftpmasters changed their opinion.
> 
> (I saw something on -devel and js mail list, but AFAIK nothing authoritative)

http://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2015-August/011067.html

We discussed lots of ways we could bundle small libraries together, but
there is no current way to monitor all of the upstream releases of
bundled packages to know when there is a new release, to manage package
dependency version constraints, and to prevent release critical bugs
removing the whole bundle regularly.

There is work going on to improve npm2deb to allow for tarballs to be
repacked to bundle closely related sub-modules (node_modules), and we
are working on the criteria to help make the choice:
https://github.com/LeoIannacone/npm2deb/issues/15

node-isarray is quite generic, and depended on by many other node
modules that are waiting to be packaged, so I don't believe it fits the
criteria for bundling as it stands at the moment.

Regards,

Ross





signature.asc
Description: OpenPGP digital signature

Bug#801452: RFS: node-core-util-is/1.0.1-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-core-util-is"

* Package name: node-core-util-is
  Version : 1.0.1-1
  Upstream Author : Isaac Z. Schlueter <i...@izs.me>
* URL : https://github.com/isaacs/core-util-is
* License : Expat
  Section : web

It builds this binary package:

node-core-util-is - util.is* functions introduced in Node v0.12 for older
versions

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

http://mentors.debian.net/package/node-core-util-is


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

dget -x http://mentors.debian.net/debian/pool/main/n/node-core-util-is/node-
core-util-is_1.0.1-1.dsc

The Debian packaging is available here:
http://anonscm.debian.org/cgit/pkg-javascript/node-core-util-is.git

Changes since the last upload:

  [ Bas Couwenberg ]
  * Initial release (Closes: #780002)


Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-30-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#800403: RFS: node-util-deprecate/1.0.1-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-util-deprecate"

* Package name: node-util-deprecate
  Version : 1.0.1-1
  Upstream Author : Nathan Rajlich <nat...@tootallnate.net>
* URL : https://github.com/TooTallNate/util-deprecate
* License : Expat
  Section : web

It builds this binary package:

node-util-deprecate - Node.js's `util.deprecate()` function with browser
support

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

http://mentors.debian.net/package/node-util-deprecate


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

dget -x http://mentors.debian.net/debian/pool/main/n/node-util-deprecate/node-
util-deprecate_1.0.1-1.dsc

Packaging can be found in the Javascript Team repository at:
http://anonscm.debian.org/cgit/pkg-javascript/node-util-deprecate.git/

Changes since the last upload:

  * Initial release (Closes: #796365)


Regards,
Ross Gammon




-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-28-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#799900: RFS: node-cross-spawn-async/2.0.0-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-cross-spawn-async"

* Package name: node-cross-spawn-async
  Version : 2.0.0-1
  Upstream Author : Nathan Rajlich <nat...@tootallnate.net> (http://n8.io/)
* URL : https://github.com/TooTallNate/util-deprecate
* License : Expat
  Section : web

It builds this binary package:

node-cross-spawn-async - Cross platform child_process#spawn

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

http://mentors.debian.net/package/node-cross-spawn-async


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

dget -x http://mentors.debian.net/debian/pool/main/n/node-cross-spawn-async
/node-cross-spawn-async_2.0.0-1.dsc

The packaging repository can be found here:
http://anonscm.debian.org/cgit/pkg-javascript/node-cross-spawn-async.git

Changes since the last upload:

  * Initial release (Closes: #796337)


Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-28-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#798861: RFS: node-process-nextick-args/1.0.3-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-process-nextick-args"

* Package name: node-process-nextick-args
  Version : 1.0.3-1
  Upstream Author : Calvin Metcalf
* URL : https://github.com/calvinmetcalf/process-nextick-args
* License : Expat
  Section : web

It builds this binary package:

node-process-nextick-args - process.nextTick but always with args

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

http://mentors.debian.net/package/node-process-nextick-args


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

dget -x http://mentors.debian.net/debian/pool/main/n/node-process-nextick-args
/node-process-nextick-args_1.0.3-1.dsc

This package will be maintained in the Debian Javascript Team repository:
http://anonscm.debian.org/cgit/pkg-javascript/node-process-nextick-args.git

Changes since the last upload:

 * Initial release (Closes: #796362)


Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-28-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Re: Bug#798215: RFS: node-typedarray/0.0.6-1 [ITP]

[Ross Gammon]

On 09/07/2015 03:15 PM, roucaries bastien wrote:
> On Mon, Sep 7, 2015 at 3:05 PM, Gianfranco Costamagna
>  wrote:
>> Control: owner -1 !
>> Control: tags -1 moreinfo
>>
>> Hi Ross,
>> 1) control: "priority: extra"
>>
>> as said before on debian-mentors the priority should be optional, unless you 
>> have good reason to
>> have extra
>> https://www.debian.org/doc/debian-policy/ch-archive.html#s-priorities
>>

Whoops - I should have checked that. That is the trouble with using
templates. I have submitted a bug against npm2deb, and a pull request to
fix this. Hopefully that will mean less mistakes from everyone in the
future:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798275

>> 2) "In order to run the tests provided with node-typedarray, it will be
>>
>> necessary to package tape for Debian."
>>
>> well, isn't it better to start from tape then?
>>
> 
> No tape need grunt and a lot of non packaged package that reverse dep
> on this package

Package node modules is like peeling onions, There is always another
layer underneath :-)
I started packaging the latest release of node-cross-spawn only to
discover that it had two new dependencies. These required 12 new modules
not yet in Debian.
I have filed an ITP for node-tape, and intend to enable the tests in
node-typedarray once node-tape gets through the NEW queue:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798278

Regards,

Ross



signature.asc
Description: OpenPGP digital signature

Re: Bug#798215: RFS: node-typedarray/0.0.6-1 [ITP]

[Ross Gammon]

On 09/07/2015 06:35 PM, Ross Gammon wrote:
> Whoops - I should have checked that. That is the trouble with using
> templates. I have submitted a bug against npm2deb, and a pull request to
> fix this. Hopefully that will mean less mistakes from everyone in the
> future:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798275

Whoops again, I forgot to actually fix node-typed array. Done now, and
pushed.



signature.asc
Description: OpenPGP digital signature

Bug#798215: RFS: node-typedarray/0.0.6-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-typedarray"

* Package name: node-typedarray
  Version : 0.0.6-1
  Upstream Author : James Halliday <m...@substack.net> (http://substack.net)
* URL : https://github.com/substack/typedarray
* License : Expat
  Section : web

It builds this binary package:

node-typedarray - TypedArray polyfill for old browsers

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

http://mentors.debian.net/package/node-typedarray


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

dget -x http://mentors.debian.net/debian/pool/main/n/node-typedarray/node-
typedarray_0.0.6-1.dsc

The packaging can be found online at:
http://anonscm.debian.org/cgit/pkg-javascript/node-typedarray.git

Changes since the last upload:

 * Initial release (Closes: #796359)


Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-26-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#796830: RFS: dominate/2.1.5-1 [ITP]

[Ross Gammon]

On 08/25/2015 12:01 PM, Gianfranco Costamagna wrote:
 Control: owner -1 !
 Control: tags -1 moreinfo
 
 Hi Ross!
 
 The packaging looks really good to me, just a problem on VCS.
 
 DPMT recently rejected my application, so I had to reupload everything
 with VCS pointing to collab-maint,
 so I'll happily sponsor the package once your application gets approved.
 (feel free to go on irc OFTC/#debian-python, to ask if you can join the team
 and about the team policy)
 
 
 
 cheers,
 
 Gianfranco
 
 

Hi Gianfranco,

I have diverted the VCS to collab-maint and pushed the packaging there:
http://anonscm.debian.org/cgit/collab-maint/dominate.git/

If you prefer me to re-upload to mentors, let me know.

No doubt, I will have other python modules to work on one day, and I
will try to join DPMPT again then. They are obviously busy (or picky!).

Regards,

Ross



signature.asc
Description: OpenPGP digital signature

Bug#796830: RFS: dominate/2.1.5-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package dominate

* Package name: dominate
  Version : 2.1.5-1
  Upstream Author : Tom Flanagan t...@zkpq.ca
* URL : https://github.com/Knio/dominate
* License : LGPL-3+
  Section : python

It builds these binary packages:

python-dominate - Python 2 library for creating and manipulating HTML documents
python3-dominate - Python 3 library for creating and manipulating HTML
documents

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

http://mentors.debian.net/package/dominate


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

dget -x
http://mentors.debian.net/debian/pool/main/d/dominate/dominate_2.1.5-1.dsc

I hope to maintain this package under the Python Modules Packaging Team if they
will have me. In which case I will update this bug with the URL to the team
repository on Alioth.

Changes since the last upload:

  * Initial release (Closes: #796518)


Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-26-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#796296: RFS: node-os-tmpdir/1.0.1-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package node-os-tmpdir

* Package name: node-os-tmpdir
  Version : 1.0.1-1
  Upstream Author : Sindre Sorhus sindresor...@gmail.com
* URL : https://github.com/sindresorhus/os-tmpdir
* License : Expat
  Section : web

It builds this binary package:

node-os-tmpdir - Node.js os.tmpdir() ponyfill

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

http://mentors.debian.net/package/node-os-tmpdir


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

dget -x http://mentors.debian.net/debian/pool/main/n/node-os-tmpdir/node-os-
tmpdir_1.0.1-1.dsc

The packaging can also be found here:
https://anonscm.debian.org/cgit/pkg-javascript/node-os-tmpdir.git

Changes since the last upload:

  * Initial release (Closes: #785462)

Please note that I am now a DM. So after initial sponsorship, you could grant
me upload rights once you are happy with my work on the package.

Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-26-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#794908: RFS: node-convert-source-map/1.1.1-1

[Ross Gammon]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package node-convert-source-map

* Package name: node-convert-source-map
  Version : 1.1.1-1
  Upstream Author : Thorsten Lorenz thlor...@gmx.de
* URL : https://github.com/thlorenz/convert-source-map/
* License : Expat
  Section : web

It builds this binary package:

node-convert-source-map - Converts a source-map from/to between formats

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

http://mentors.debian.net/package/node-convert-source-map


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

dget -x http://mentors.debian.net/debian/pool/main/n/node-convert-source-map
/node-convert-source-map_1.1.1-1.dsc

The packaging can be found here:
http://anonscm.debian.org/cgit/pkg-javascript/node-convert-source-map.git

Changes since the last upload:

  * New upstream release
  * Drop testsuite stanza as no longer required
  * Fix New Issues URL in metadata

Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-25-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150807222002.3175.92455.reportbug@localhost

Bug#794345: RFS: node-coffeeify/1.1.0-1 [RC]

[Ross Gammon]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package node-coffeeify

* Package name: node-coffeeify
  Version : 1.1.0-1
  Upstream Author : Johan Nordberg h...@johan-nordberg.com
* URL : https://github.com/jnordberg/coffeeify
* License : Expat
  Section : web

It builds this binary package:

node-coffeeify - browserify plugin for coffee-script

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

http://mentors.debian.net/package/node-coffeeify


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

dget -x http://mentors.debian.net/debian/pool/main/n/node-coffeeify/node-
coffeeify_1.1.0-1.dsc

Packaging can be found on Alioth:
https://anonscm.debian.org/cgit/pkg-javascript/node-coffeeify.git

Changes since the last upload:

  * New upstream release
  * Fix node-convert-source-map dependency version
(Closes: #793856)
  * Drop testsuite stanza as no longer required for autopkgtest


Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-25-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150801205731.12289.22389.reportbug@localhost

Bug#788475: RFS: goocanvas-2.0/2.0.2-2 [ITA]

[Ross Gammon]

On 08/01/2015 09:35 AM, Alberto Garcia wrote:
 On Thu, Jun 11, 2015 at 08:44:03PM +0200, Ross Gammon wrote:
 
 I am looking for a sponsor for my package goocanvas-2.0

 * Package name: goocanvas-2.0
   Version : 2.0.2-2
   Upstream Author : Damon Chaplin da...@gnome.org
 * URL : https://wiki.gnome.org/action/show/Projects/GooCanvas
 * License : LGPL-2
   Section : libs
 
 Hello, I just came back from holidays and saw this. I took a look at
 your changes and I think you have done a pretty good job. I will be
 happy to sponsor this package.
 
 Since it's been a while since you created this, do you need / want to
 make any changes before the upload or can I just upload it as it is
 now?
 
 Thanks!
 
 Berto

Hi Berto,

Welcome back. I am also just back from my holidays (and a week away from
home with work).

There was nothing more I wanted to change, so it would be great if you
could sponsor it!

My next steps would be to do a tidy up of the old goocanvas package
and it's bugs so that it is clear that it is dead upstream and will only
exist in the medium term.

Regards,

Ross



signature.asc
Description: OpenPGP digital signature

Bug#789628: RFS: netcdf-cxx-legacy/4.2-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package netcdf-cxx-legacy

* Package name: netcdf-cxx-legacy
  Version : 4.2-1
  Upstream Author : University Corporation for Atmospheric Research/Unidata
* URL : http://www.unidata.ucar.edu/software/netcdf/
* License : NetCDF
  Section : science

It builds these binary packages:

libnetcdf-c++4 - legacy NetCDF C++ interface
libnetcdf-cxx-legacy-dbg - debugging symbols for legacy NetCDF C++ interace
libnetcdf-cxx-legacy-dev - legacy NetCDF C++ interface - development files

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

http://mentors.debian.net/package/netcdf-cxx-legacy


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

dget -x http://mentors.debian.net/debian/pool/main/n/netcdf-cxx-legacy/netcdf-
cxx-legacy_4.2-1.dsc

More information about hello can be obtained from
http://www.unidata.ucar.edu/software/netcdf/

Changes since the last upload:

  [ Nico Schlömer ]
  * Initial release. (Closes: #789622)

  [ Bas Couwenberg ]
  * Add myself to Uploaders.
  * Align dependencies in control file.
  * Rename source package to netcdf-cxx-legacy.
  * Switch Maintainer to Debian GIS Project.
  * Change priority to optional.
  * Reorder control fields.
  * Bump Standards-Version to 3.9.6.
  * Drop Suggests on non-existing package.
  * Change description to match netcdf-cxx.
  * Update copyright file.
  * Don't install duplicate license.
  * Override dh_install to use --list-missing.
  * Update watchfile.
  * Also install examples.
  * Add gbp.conf to use pristine-tar by default.
  * Rename library package to match SONAME.
  * Enable parallel builds.
  * Add symbols file using pkg-kde-symbolshelper.

  [ Ross Gammon ]
  * Add Breaks/Replace on old C++ library
  * Mention netcdf-3 version in d/control long description


Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers utopic-updates
  APT policy: (500, 'utopic-updates'), (500, 'utopic-security'), (500, 
'utopic'), (100, 'utopic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-41-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150622195742.19936.25338.reportbug@localhost

Re: packaging Advanced Gtk+ Sequencer - automatic debian build

[Ross Gammon]

Hi Joël,

On 06/16/2015 04:28 PM, Joël Krähemann wrote:
 Hi, could someone please take a look at my repository:
 
 http://anonscm.debian.org/cgit/pkg-multimedia/gsequencer.git

I am also a member of the multimedia team and have seen your commits
rolling in. You are getting close to having something ready for
sponsorship. But on a quick (not complete check) there is still some
work to do (see below).

 Please tell me what I have to do that it gets processed by the automatic
 debian build system. Further what is still left to do so.

Coming to the mentors list was a very good idea. There are many
experienced guys here that can help out.
The best thing to do next is to prove you can build your package by
uploading the built package to the mentors website. The website will
also tell any reviewer whether you have fixed all the relevant lintian
errors. See here for information:
https://mentors.debian.net/intro-maintainers

 Note there aren't any signed tags, yet. Should I rebase and add tags for
 old commits?

Normal practise is to sign a tag when you import the upstream release.
Then when the package is uploaded to the debian archive, there should be
a signed tag for the last commit before the upload.
There is information on tagging specific to the multimedia team here:
https://wiki.debian.org/DebianMultimedia/DevelopPackaging

 best regards
 Joël Krähemann
 

Now for some comments:
debian/changelog - Your changelog entry looks a little unfinished. It
should close your ITP bug, and as it is a new package it really only
needs one entry which is something like:
  * Initial release (Closes: #)   is the ITP bug number

debian/copyright - You only list the copyright for files in the debian
directory. You should also list the copyright for the upstream source code.

debian/debhelper.log - This file is the resulting log from a previous
build of the package to help with troubleshooting. It should be deleted.

debian/rules - You should remove all the unnecessary commenting. It is
normally okay to leave the verbose option commented out so that it can
be quickly added in when you are troubleshooting.

Some references that you might want to read (again?):
https://www.debian.org/doc/manuals/maint-guide/index.en.html
https://wiki.debian.org/UpstreamGuide (* as I know you are also upstream).

Keep going!

Cheers,

Ross



signature.asc
Description: OpenPGP digital signature

Re: Fwd: goocanvas-2.0 uploaded to mentors.debian.net

[Ross Gammon]

Hi Berto,

Thanks for that. A new version has just been uploaded to mentors.

On 06/01/2015 10:47 PM, Alberto Garcia wrote:
 On Sun, May 31, 2015 at 09:47:15PM +0200, Ross Gammon wrote:
 
 Before I request sponsorship, I would be grateful if someone could
 give it a review.
 
 There's a typo in the changelog (desciptions - descriptions).

Fixed.

 I also think that now you should be able to make gir1.2-goocanvas-2.0
 (and probably libgoocanvas-2.0-dev) Multi-Arch: same.

Yes. This is done now, and the patch dropped so that the typelib is is
installed in the multi-arch path.

 Otherwise it looks good to me.
 
 Thanks for the work!
 
 Berto

I have pushed the package to collab-maint, and added the usual packaging
stuff for a git repository (e.g. gbp.conf).

During a final test I also discovered that the package did not build
twice in a row. This took a little while for me to fix.

As I think my usual sponsor for collab-maint packages is busy for a few
weeks, I will submit an RFS bug very soon.

Regards,

Ross



signature.asc
Description: OpenPGP digital signature

Fwd: goocanvas-2.0 uploaded to mentors.debian.net

[Ross Gammon]

Hi Mentors,

I intend to adopt goocanvas, which has been orphaned and has had the
latest package sitting in experimental for quite a while.

At first I thought it would need a transition. But as suggested by
Alberto, I have renamed the source package (goocanvas-2.0) so that it
can be installed alongside the old goocanvas. This is what has already
been done in Ubuntu.

Before I request sponsorship, I would be grateful if someone could give
it a review.

At the moment it has collab-maint in the VCS fields, but I have not
pushed it there yet. I believe the most appropriate place to maintain
this package would be in the Debian Gnome Team alongside the other
applications hosted by Gnome. I have copied the Gnome Team in in case
they agree.

I have tested that it installs fine over the top of the version in
experimental (that is why I used a Debian -2 version), but I would like
another pair of eyes to check the Breaks/Replace for Ubuntu (they
unfortunately chose slightly different package names). In my Wily VM, an
install forces the removal of the libraries.

The links to the package on mentors can be found below.

Regards,

Ross

 Forwarded Message 
Subject: goocanvas-2.0 uploaded to mentors.debian.net
Date: Sun, 31 May 2015 19:16:48 + (UTC)
From: mentors.debian.net supp...@mentors.debian.net
To: rossgam...@mail.dk

Hi.

Your upload of the package 'goocanvas-2.0' to mentors.debian.net was
successful. Others can now see it. The URL of your package is:
http://mentors.debian.net/package/goocanvas-2.0

The respective dsc file can be found at:
http://mentors.debian.net/debian/pool/main/g/goocanvas-2.0/goocanvas-2.0_2.0.2-2.dsc

If you do not yet have a sponsor for your package you may want to go to
http://mentors.debian.net/sponsors/rfs-howto/goocanvas-2.0
and set the Seeking a sponsor option to highlight your package on the
welcome page.

You can also send an RFS (request for sponsorship) to the debian-mentors
mailing list. Your package page will give your suggestions on how to
send that mail.

Good luck in finding a sponsor!

Thanks,

-- 
mentors.debian.net






signature.asc
Description: OpenPGP digital signature

Re: Bug#786571: RFS: osm-gps-map/1.0.2-3 [uploaded]

[Ross Gammon]

On 05/23/2015 03:02 AM, Sebastiaan Couwenberg wrote:
 Hi Ross,
 
 Thanks for your work on this package.
 
 On 05/23/2015 12:21 AM, Ross Gammon wrote:
 I am looking for a sponsor for my package osm-gps-map
 
 I've sponsored the uploaded, but there are a couple of unused
 substitution variables in the control file you may want to have a look at.
 
 Kind Regards,
 
 Bas
 

Thanks Bas,

I will look at that and get something ready for the next upload.

Regards,

Ross



signature.asc
Description: OpenPGP digital signature

Bug#786571: RFS: osm-gps-map/1.0.2-3

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package osm-gps-map

* Package name: osm-gps-map
  Version : 1.0.2-3
  Upstream Author : John Stowers john.stow...@gmail.com
* URL : http://nzjrs.github.io/osm-gps-map/
* License : GPL-2
  Section : science

It builds these binary packages:

gir1.2-osmgpsmap-1.0 - GTK+ library to embed OpenStreetMap maps - Python
bindings
libosmgpsmap-1.0-0 - GTK+ library to embed OpenStreetMap maps
libosmgpsmap-1.0-0-dbg - GTK+ library to embed OpenStreetMap maps - debugging
symbols
libosmgpsmap-1.0-0-dev - GTK+ library to embed OpenStreetMap maps - development
files

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

http://mentors.debian.net/package/osm-gps-map


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

dget -x http://mentors.debian.net/debian/pool/main/o/osm-gps-map/osm-gps-
map_1.0.2-3.dsc

More information about hello can be obtained from https://github.com/nzjrs/osm-
gps-map

Debian Packaging is available at:
http://anonscm.debian.org/cgit/pkg-grass/osm-gps-map.git/

Changes since the last upload:

  * Start new Debian revision
  * Fix watch file
  * Bump standards version, no changes required
  * Update Vcs URL to use cgit instead of gitweb
  * Fix duplicate section in d/control
  * Drop file from d/copyright that is no longer shipped
  * Reveal hidden compile flags in buildlog
  * Fix CFLAG append in d/rules so default hardening options are used
  * Add upstream metadata
  * Add lintian override for hardening-no-fortify warning

Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers utopic-updates
  APT policy: (500, 'utopic-updates'), (500, 'utopic-security'), (500, 
'utopic'), (100, 'utopic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-38-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/2015052159.32425.16414.reportbug@localhost

Re: Bug#784132: RFS: pyshp/1.2.1-2

[Ross Gammon]

On 05/03/2015 02:39 PM, Paul Wise wrote:
 On Sun, May 3, 2015 at 7:21 PM, Ross Gammon wrote:
 
 I am looking for a sponsor for my package pyshp
 
 I don't intend to sponsor this (I guess sebastic or dapal will) but
 here is a review:
 

Thanks very much for the review Paul. I mainly wanted to fix the
watchfile and URLs, but of course there is always more to fix than the
time available :-)

You are correct that sebastic normally sponsors things in the GIS team,
and he already fixed most of what you found and then uploaded. I will
look into the rest soon (including sorting out the upstream stuff).

Regards,

Ross





signature.asc
Description: OpenPGP digital signature

Bug#784132: RFS: pyshp/1.2.1-2

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package pyshp

* Package name: pyshp
  Version : 1.2.1-2
  Upstream Author : Joel Lawhead jlawh...@geospatialpython.com
* URL : https://github.com/GeospatialPython/pyshp
* License : MIT
  Section : python

It builds these binary packages:

python-pyshp - read/write support for ESRI Shapefile format
python3-pyshp - read/write support for ESRI Shapefile format - Python 3.x

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

http://mentors.debian.net/package/pyshp


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

dget -x http://mentors.debian.net/debian/pool/main/p/pyshp/pyshp_1.2.1-2.dsc

Changes since the last upload:

  [ Ross Gammon ]
  * Fix watchfile using pypi redirector  future proof with mangles
  * Change Vcs Browser URL to use cgit instead of gitweb
  * Upstream homepage switched from Google code to Github
  * Bump standards version, no changes required

  [ Bas Couwenberg ]
  * Update uversionmangle in watch file to match more traditional pre-releases.


Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers utopic-updates
  APT policy: (500, 'utopic-updates'), (500, 'utopic-security'), (500, 
'utopic'), (100, 'utopic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-36-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150503112117.27279.7526.reportbug@localhost

Bug#770149: python-instagram

[Ross Gammon]

Hi Jörg,

I am glad to see you working on this, as one of my packages will
eventually depend on python-instagram!

On 04/06/2015 11:31 PM, Jörg Frings-Fürst wrote:

 
 
 Please can someone review this package[1].
 
 Thanks.
 
 CU
 Jörg
 
 [1] 
 http://mentors.debian.net/debian/pool/main/p/python-instagram/python-instagram_1.3.0+git20150406~e885e7d-1.dsc
 
 

Therefore, I thought I would give you a review for what it is worth (I
am not a DD so I cannot sponsor it):

- The package builds fine in a chroot and the clean target is working fine.
- piuparts reports no problems.
- Lintian is happy.
- The watch file is not working, but that is okay as upstream do not do
releases or tags.

I am wondering why d/control has Provides: ${python:Provides}? Python
Policy mentions it (and generally discourages its use). Mainly I am
curious about it.

One minor comment about d/copyright is that according to the upstream
README  LICENSE files, the copyright says 2014, Facebook, Inc. (not
Instagram, and not in 2015)

I also noticed that setup.py still says MIT (not reflecting the recent
change to BSD). You might want to report that upstream.

Here's hoping you find a sponsor soon.

Regards,

Ross




signature.asc
Description: OpenPGP digital signature

Bug#781701: [Pkg-javascript-devel] Bug#781701: RFS: node-convert-source-map/1.0.0-1 [ITP]

[Ross Gammon]

Thanks for the review :-)

On 02/04/15 19:47, Sebastiaan Couwenberg wrote:

Hi Ross,

Thanks for your work on this package.

On 04/01/2015 08:53 PM, Ross Gammon wrote:

I am looking for a sponsor for my package node-convert-source-map

There are some minor issues that needs to be addressed before the upload
to the archive.


debian/control:

Testsuite: autopkgtest

AFAIK this is not an official header yet, it should be XS-Testsuite.


Fixed. I am still fine tuning my set up on the new Jessie laptop. cme 
fix dpkg-control got more things correct than I am used to on my desktop 
machine, but I clearly cannot completely trust it!




debian/copyright:

It contains an incorrect copyright year, npm2deb tends to get this
wrong. The LICENSE file specifies 2013.



Fixed.


The upstream sources contain an example, you should consider including
it in the package.



Added a node-convert-source-map.examples file.


Since inline-source-map is not packaged yet, you can't run the tests. If
it get packaged in the future you should consider running the tests
during the build process.



Added a d/TODO file to remind me to check if the tests can be enabled 
next time.



Kind Regards,

Bas



Updated on alioth  uploaded fresh to Mentors.

Regards,

Ross


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/551ea801.4040...@mail.dk

Bug#781763: RFS: node-coffeeify/1.0.0-1 [ITP]

[Ross Gammon]

On 03/04/15 19:14, Sebastiaan Couwenberg wrote:

On 04/03/2015 05:56 PM, Ross Gammon wrote:

Thanks again for another review Bas.

On 02/04/15 19:59, Sebastiaan Couwenberg wrote:

You may want to consider extending Use_through2.patch to cover all files
that use the through module, there are some tests that require it too.
Since the test dependencies cannot be satisfied in Debian strictly
required.

I have fixed (I hope) all the other issues, but have one question before
I finish. The package.json file also requires through. Should we leave
this pristine so users know what upstream intended to be used (through),
or also patch it to show what we used (through2)?

I think the package.json installed by the Debian package should reflect
the dependencies used by the package not npm.

Kind Regards,

Bas

Okay - sounds logical. I updated the patch  pushed the change to 
alioth. I am assuming you will take the change from there, and I am 
therefore deleting the version on mentors.


Thanks for the clarification.

Ross


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/551ece5f.40...@the-gammons.net

Bug#781763: [Pkg-javascript-devel] Bug#781763: RFS: node-coffeeify/1.0.0-1 [ITP]

[Ross Gammon]

Thanks again for another review Bas.

On 02/04/15 19:59, Sebastiaan Couwenberg wrote:

You may want to consider extending Use_through2.patch to cover all files
that use the through module, there are some tests that require it too.
Since the test dependencies cannot be satisfied in Debian strictly required.
I have fixed (I hope) all the other issues, but have one question before 
I finish. The package.json file also requires through. Should we leave 
this pristine so users know what upstream intended to be used (through), 
or also patch it to show what we used (through2)?


Cheers,

Ross


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/551eb815.2010...@mail.dk

Bug#781763: RFS: node-coffeeify/1.0.0-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package node-coffeeify

* Package name: node-coffeeify
  Version : 1.0.0-1
  Upstream Author : Johan Nordberg h...@johan-nordberg.com
* URL : https://github.com/jnordberg/coffeeify
* License : Expat
  Section : web

It builds this binary package:

node-coffeeify - browserify plugin for coffee-script

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

http://mentors.debian.net/package/node-coffeeify


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

dget -x http://mentors.debian.net/debian/pool/main/n/node-coffeeify/node-
coffeeify_1.0.0-1.dsc

The Debian packaging can be cloned with:

debcheckout --user username git://git.debian.org/pkg-javascript/node-
coffeeify.git --git-track '*'

Changes since the last upload:

  * Initial release (Closes: #780698)
  * Patch index.js to use through2 instead of through


Regards,
Ross Gammon



-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150402172409.13070.68982.report...@rosco-laptop.home

Bug#781701: RFS: node-convert-source-map/1.0.0-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package node-convert-source-map

* Package name: node-convert-source-map
  Version : 1.0.0-1
  Upstream Author : Thorsten Lorenz thlor...@gmx.de (http://thlorenz.com)
* URL : https://github.com/thlorenz/convert-source-map
* License : Expat
  Section : web

It builds this binary package:

node-convert-source-map - Converts a source-map from/to between formats

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

http://mentors.debian.net/package/node-convert-source-map


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

dget -x 
http://mentors.debian.net/debian/pool/main/n/node-convert-source-map/node-convert-source-map_1.0.0-1.dsc

The packaging can be cloned using:

debcheckout --user username 
git://git.debian.org/pkg-javascript/node-convert-source-map.git --git-track '*'

Changes since the last upload:

  * Initial release (Closes: #780699)


Regards,
Ross Gammon



-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150401185317.12879.56171.report...@rosco-laptop.home

Bug#781059: RFS: netcdf4-python/1.1.7-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package netcdf4-python

* Package name: netcdf4-python
  Version : 1.1.7-1
  Upstream Author : University Corporation for Atmospheric Research/Unidata
* URL : http://unidata.github.io/netcdf4-python/
* License : ISC, Expat
  Section : science

It builds these binary packages:

python-netcdf4 - Python interface to the netCDF4 (network Common Data Form)
library
python3-netcdf4 - Python 3 interface to the netCDF4 (network Common Data Form)
library

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

http://mentors.debian.net/package/netcdf4-python


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

dget -x
http://mentors.debian.net/debian/pool/main/n/netcdf4-python/netcdf4-python_1.1.7-1.dsc

The packaging can be found at git://anonscm.debian.org/pkg-
grass/netcdf4-python.git.

Changes since the last upload:

  [ Ross Gammon ]
  * Initial release (Closes: #778417).
  * Patch nc4tonc3 tool to fix indentation failure.
  * Add missing manpages.

  [ Bas Couwenberg ]
  * Switch to github release tarballs
  * Help netCDF4 to find HDF5 library
  * Add python3 package.
  * Install utilities in Python 3 package only.
  * Remove RPATH from library.


Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers trusty-security
  APT policy: (990, 'trusty-security'), (900, 'trusty-updates'), (500, 
'trusty'), (100, 'trusty-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13.0-46-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150323220525.10796.87258.reportbug@localhost

Bug#779667: RFS: node-bluebird/2.9.13+dfsg-1 [ITP]

[Ross Gammon]

Control: tags -1 moreinfo

Okay - it turns out that for node-bluebird to work in Debian, we need to
build the javascript using their build script, and thus need lots of
extra dependencies packaged.

I am working on these other packages, so this RFS is on hold for a bit.

Regards,

Ross



signature.asc
Description: OpenPGP digital signature

Bug#780695: RFS: node-cli-table/0.3.1-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package node-cli-table

* Package name: node-cli-table
  Version : 0.3.1-1
  Upstream Author : Guillermo Rauch guille...@learnboost.com
* URL : https://github.com/Automattic/cli-table
* License : MIT
  Section : web

It builds this binary package:

node-cli-table - Pretty unicode tables for the CLI

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

http://mentors.debian.net/package/node-cli-table


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

dget -x http://mentors.debian.net/debian/pool/main/n/node-cli-table/node-cli-
table_0.3.1-1.dsc

The Debian packaging can be found here:

http://anonscm.debian.org/cgit/pkg-javascript/node-cli-table.git/

Changes since the last upload:


  * Initial release (Closes: #780342)
  * Patched example to find installed cli-table
  * Add a manual test using installed example


Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers trusty-security
  APT policy: (990, 'trusty-security'), (900, 'trusty-updates'), (500, 
'trusty'), (100, 'trusty-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13.0-46-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150317215033.27152.55326.reportbug@localhost

Bug#779667: RFS: node-bluebird/2.9.13+dfsg-1 [ITP]

[Ross Gammon]

On 03/04/2015 11:47 PM, Sebastiaan Couwenberg wrote:
 Thanks for the fixes. I've pushed some more changes for various things
 I encountered.

Thanks for those. Using npm2deb for the first time made me miss some of
my normal steps.

 
 Did you notice that the upstream build process requires itself?

No - I did notice that the upstream build (and tests) did not work, but
not that the require was the reason for it. I was looking to see if we
could use tools/build.js to build the minified js instead of using
uglify. After giving up, my thought was to work with upstream to fix it
later - but I am happy to do that now instead.

 The tools/build.js script also does some modifications to the source
 when it generates the js/main/ code from the source.
 
 If installing the unmodified source is not sufficient, we may need to
 find a different solution to replace build.js to bootstrap this package.

I might raise an issue upstream and see what they say. It would be good
to have the upstream build and tests working.

 I haven't tested this yet.

After the doing that, I suppose the final thing is to repack to remove
the pre-built minified js.

Cheers,

Ross



signature.asc
Description: OpenPGP digital signature

Re: Adopting orphan package: arpwatch -- Ethernet/FDDI station activity monitor

[Ross Gammon]

Hi Kim,

On 03/04/2015 05:17 PM, Kim Christensen wrote:

 I have found that the arpwatch package has been orphaned for more
 than a 905 days now, and would like to adopt it. This would be my
 first package and the first endeavour into helping out in any way, so
 I'm looking for pointers in the right direction. 
 
 Orphan bug report:
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686996
 
 As you can see there has been some interest in adopting it, but none
 of those people has accepted it. I've been doing local packages for my
 own systems for the past years, and I've been reading the maintenance
 guides for that. 

Sounds like your first step should be to state your intention to adopt
on that bug report. Lucas gives good instructions how to do that in the
lest entry on the bug.

 
 So if I understand the developer's manual correctly, I would need a
 sponsor for proxying the maintenance of this package. If and when I
 get a sponsor, I would send my updates to that person for QA and final
 upload to the repository. Am I correct? If not, please help me figure
 this out :-)

That's pretty much how it goes. The best thing is to pull together the
package, and when you think it is ready, upload it to mentors.debian.net.

Ask for some reviews for your package on this list, and you should
receive comments to help improve it.

Once you have a positive review, create a RFS bug (Request For Sponsor),
and hopefully a sponsor will offer to work with you and do an upload.

See here for more help on the process:
https://mentors.debian.net/intro-maintainers

Regards,

Ross



signature.asc
Description: OpenPGP digital signature