Bug#830827: RFS: wvstreams/4.6.1-9 [QA, RC]

[Gert Wollny]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for the package "wvstreams"

 * Package name: wvstreams
   Version : 4.6.1-9
   Upstream Author : Net Integration Technologies Inc. et al. 
 * URL : https://github.com/apenwarr/wvstreams/
 * License : LGPL-2.1 
   Section : libs

It builds those binary packages:

 libuniconf4.6 - C++ network libraries for rapid application
    development
 libwvstreams-dev - Development libraries and header files for 
    libwvstreams4.6Package: sponsorship-requests
  libwvstreams4.6-base - C++ network libraries for rapid application 
    development
 libwvstreams4.6-doc - Documentation for WvStreams
 libwvstreams4.6-extras - C++ network libraries for rapid application
    development
 uniconf-tools - Tools to interface with UniConf
 uniconfd   - Server that manages UniConf elements

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

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


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

 dget -x https://mentors.debian.net/debian/pool/main/w/wvstreams/wvstre
ams_4.6.1-9.dsc

Changes since the last upload:

  * d/p/gcc-6: Patch to fix compilation with gcc-6, Closes: #811659
  * run 'cme fix dpkg-control', updated standards version to 3.9.8 
  * d/compat, d/control: update compat level to 9
  * d/watch: Point to new github source location 
  * d/control: add new Github home page
  * d/uniconfd.init: source /lib/lsb/init-functions if available
  * d/rules: Add and install overrides for missing manpage of dev test 
program and the Doxygen created embedded javascript library 
  * d/rules: remove irrelevant *.md5 files from -doc package

Regards,
Gert 

Bug#829151: RFS: setcolortemperature/1.1-1 ITP

[Sean Whitton]

On Mon, Jul 11, 2016 at 05:13:22PM +, Gianfranco Costamagna wrote:
> src:setcolortemperature
> binary: sct
> 
> please choose one, and use the same, you can't usually expect users to install
> a package and expect a binary called in another way.
> 
> I seem to be pedantic, but I really like to have them called in the same way

Aren't there different rationales for source and binary package names?
This is what I have been thinking:

- source package name should be upstream's name, because it's the
  *source*
- binary package name is whatever makes most sense for someone typing
  apt-get

-- 
Sean Whitton

Bug#829151: RFS: setcolortemperature/1.1-1 ITP

[Gianfranco Costamagna]

Hi,


>K == Kelvin, not kilo.

this is what happens when one person is not using google :)
thanks you all!

G.

Bug#829151: RFS: setcolortemperature/1.1-1 ITP

[Jakub Wilk]

* Gianfranco Costamagna , 2016-07-11, 17:13:

are you sure it is 6500K?

6500K should be equal to "650"


K == Kelvin, not kilo.

--
Jakub Wilk

Bug#829151: RFS: setcolortemperature/1.1-1 ITP

[Andrew Shadura]

On 11 Jul 2016 19:18, "Gianfranco Costamagna" 
wrote:
>
> Hi,
>
> >This has been fixed. Now when -h is passed usage is printed and if the
>
> >temperature passed is wrong usage will also be printed.
>
>
> I still see nothing when called with no parameters :)
>
> (well you might print something like "temperature reset to the default
value (65K) or similar)
>
> BTW
> If no arguments are passed sct resets the display to the default
temperature (6500K)
>
>
> are you sure it is 6500K?
>
> 6500K should be equal to "650"
> (note: I didn't check, I just want to avoid a bad number here)

K here is kelvins, not thousands :)

-- 
Cheers,
  Andrew

Bug#829151: RFS: setcolortemperature/1.1-1 ITP

[Gianfranco Costamagna]

Hi,

>This has been fixed. Now when -h is passed usage is printed and if the

>temperature passed is wrong usage will also be printed.


I still see nothing when called with no parameters :)

(well you might print something like "temperature reset to the default value 
(65K) or similar)

BTW
If no arguments are passed sct resets the display to the default temperature 
(6500K)


are you sure it is 6500K?

6500K should be equal to "650"
(note: I didn't check, I just want to avoid a bad number here)

>Fixed.
>Added



nice!


>> other stuff LGTM
sorry but I missed something:

src:setcolortemperature
binary: sct

please choose one, and use the same, you can't usually expect users to install
a package and expect a binary called in another way.

I seem to be pedantic, but I really like to have them called in the same way

thanks for caring and understanding I hope :)

Gianfranco

Re: How to upgrade my gpg key to debian standards?

[Ansgar Burchardt]

On Sun, 2016-07-10 at 18:39 -0400, Paul Elliott wrote:
> I am looking at upgrading my gpg key.
> 
> What parameters should I use?

[1] has a guide which options to use to make sure that you use strong
hashes for the (self-)signatures on your key.  I'm not sure if GnuPG
upstream has changed their defaults since that documentation was
written.

  [1] https://keyring.debian.org/creating-key.html

Ansgar

Bug#830682: marked as done (RFS: engauge-digitizer/8.3-1)

[Debian Bug Tracking System]

Your message dated Mon, 11 Jul 2016 14:43:14 + (UTC)
with message-id <486149716.1690997.1468248194305.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#830682: RFS: engauge-digitizer/8.3-1
has caused the Debian Bug report #830682,
regarding RFS: engauge-digitizer/8.3-1
to be marked as done.

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

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


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


Dear mentors,

  I am looking for a sponsor for my package "engauge-digitizer"

 * Package name: engauge-digitizer
   Version : 8.3-1   
   Upstream Author : Mark Mitchell 
 * URL : https://github.com/markummitchell/engauge6
 * License : GPL-2+
   Section : science

  It builds those binary packages:

engauge-digitizer - interactively extracts numbers from bitmap graphs or 
maps
 engauge-digitizer-doc - engauge-digitizer user manual and tutorial

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

  https://mentors.debian.net/package/engauge-digitizer


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

dget -x 
https://mentors.debian.net/debian/pool/main/e/engauge-digitizer/engauge-digitizer_8.3-1.dsc

  More information about hello can be obtained from https://www.example.com.

  Changes since the last upload:

  * New upstream release
- New grid line removal dialog (Closes: #426421) 
- Raw data export format for multiple curves available (Closes: 426579)
- Crosshair customizable (Closes: #426340) 
  * Updated description in control to be consistent with appdata
  * Removed obsolete dependency on libpng  
  * Enabled support for jpeg2000 and pdf formats 
  * Patch add_search_path_for_help included upstream 
  * Added appdata information
  * Use provided .desktop file


  Regards,
   Tobias Winchen
--- End Message ---
--- Begin Message ---
Hi,
>  I am looking for a sponsor for my package "engauge-digitizer"



LGTM, in unstable in a few hours.

thanks,

G.--- End Message ---

Re: Call for review: Improving RFS template for mentors.debian.net

[HAYASHI Kentaro]

On Sun, Jul 10, 2016 at 10:23 PM, Jakub Wilk  wrote:
>>>   Collect 'QA upload.' information by debianqa plugin
>>>   https://github.com/debexpo/debexpo/pull/42
>
> Um, that's... unusual way to search for a string. Have you tried using
regular expressions? :)
>
> Or alternatively, it might be simpler to look at the Maintainer field.
The e-mail address should be packa...@qa.debian.org for all QA uploads.


Hi,
As you suggested, it is simple to check Maintainer field. I got it. Thank
you for feedback!


> P.S. Does anyone knows the way to check [RC] case easily - the package
contains fixed RC bugs
>
> debexpo already knows about bugs the upload would close and their
severities. For example https://mentors.debian.net/package/aspell-sk reads:
>

Ah, I found that I had better to look into closedbugs plugin, Thanks!

--
Kentaro Hayashi 

Bug#830788: RFS: ifstat/1.1-9

[Gianfranco Costamagna]

control: owner -1 !
control: tags -1 moreinfo


>I am looking for a sponsor for my package "ifstat"


here we are sir

>More information about hello can be obtained from https://www.example.com.

interesting website, indeed!
>  * Update to debhelper version 9 (Closes: #817499, #828348).
>  * Add multiarch support.
>  * Fix bandwidth spelling in manpage (Closes: #617336).
>  * Use dpkg-buildflags for hardening.
>
>-- Goswin von Brederlow   Mon, 11 Jul 2016 12:03:29 +0200
>
>
>The changes are purely packaging (except the spelling) related and a straight
>update from the old rules file to dh. It blocks some transitions so it's
>mildly important to get uploaded soon.


what about adding a "convert to quilt mode" and "extract patches"? :)
I really would like to see it quilt converted

mkdir debian/source
echo "3.0 (quilt)" >> debian/source/format
dpkg-source --commit
extract the patch and split it in debian/patches directory
(and debian/patches/series file to list them)

this isn't strictly required by policy, but I *really* appreciate
it, this is why I'm tagging moreinfo.


thanks for considering it :)

G.

Re: pbuilder error

[Gianfranco Costamagna]

Hi,


>H. I see your fixbadproxy config being copied, so I wonder whats up,
>but its quite obvious that the options didn't take effect at all as, as
>mentioned (in the quote), the first two are very noisy.


interestingly enough, it works on my machine, but it doesn't under pbuilder
chroots, even if it is being copied correctly :)


>I know, experts call it "placebo effect". ;)

lol true!

>[APT developer snip]

I fully trusted your statement even before, I usually blindly trust people 
answering
here, just I wanted you to write it down, to make it visible to future 
"googlings" :)

>It probably was a bad idea to use such a catchy option name for such
>a limited purpose code… or perhaps it a very clever april fouls joke
>– who could tell the difference…


yep indeed, the date is suspicious enough ;)


thanks David for the nice followup!

have a nice day,

Gianfranco

Re: Call for review: Improving RFS template for mentors.debian.net

[Gianfranco Costamagna]

HI,

>>Thank you for feedback.

>>But I hadn't ever seen such tag.
>>https://mentors.debian.net/sponsor/rfs-howto
>
>There's no standard tag for this, and I don't think we need one.
>
>If there's no tag in the subject, then the upload is supposed to be

>"regular".

I bet to disagree sir :)
I personally think no tag might mean
- missing tag
- user forgot it
- regular upload.

Sometimes I like being explicit rather than implicit.
And I saw people using [update] [package refresh] [regular update]
tags.
I personally prefer an "Update" tag, rather than having users guess/invent
new words for something that is regular [1].

(I probably wont continue this discussion, I don't have a strong enough
opinion here, the above is all I can think/say on the matter ;) )


[1] https://xkcd.com/927

Bug#830788: RFS: ifstat/1.1-9

[Goswin von Brederlow]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 Package name: ifstat
 Version : 1.1-9
 Upstream Author : Gal Roualland 
 URL : http://gael.roualland.free.fr/ifstat/
 License : GPL
 Section : net

It builds those binary packages:

ifstat- InterFace STATistics Monitoring
libifstat-dev - Ifstat Development Files

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

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


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

  dget -x https://mentors.debian.net/debian/pool/main/i/ifstat/ifstat_1.1-9.dsc

More information about hello can be obtained from https://www.example.com.

Changes since the last upload:

ifstat (1.1-9) unstable; urgency=low

  * Update to debhelper version 9 (Closes: #817499, #828348).
  * Add multiarch support.
  * Fix bandwidth spelling in manpage (Closes: #617336).
  * Use dpkg-buildflags for hardening.

 -- Goswin von Brederlow   Mon, 11 Jul 2016 12:03:29 +0200


The changes are purely packaging (except the spelling) related and a straight
update from the old rules file to dh. It blocks some transitions so it's
mildly important to get uploaded soon.

Regards,
 Goswin von Brederlow

Re: How to upgrade my gpg key to debian standards?

[Gianfranco Costamagna]

Hi,



>I am looking at upgrading my gpg key.
>
>What parameters should I use?
>
>Is there a standard way to get all the people that signed
>the old key to sign the new key?


some general answering should tell that it is up to the developers to
sign the new one, or ask you to meet in person.

"trust" in this case depends on many factors, some of them are just human :)

is the old key too weak to still be considered secure?

yes: I'm afraid you should try to use an additional channel to ask them to 
resign
a new one (e.g. text them with mobile phone, skype call, or something else)

no: (this is what I did)

GPG1 old key (signed by him)

GPG2 new one (not signed)

Send an email signed by GPG1 and attach a text file with the same mail content 
but signed inline
with key 2

so, the developer will see the same content signed with both keys, and will 
probably accept
that as secure enough method

some text might be
"Hi, we meet in A, you signed my key GPG1 full fingerprint, now I'm changing it 
with a new GPG2 full fingerprint
and I would like to ask you to sign it, and I'm attaching the same content 
signed with the new key, to
let you know I'm the owner of it, of course since you already have my phone 
number XXX and my skype/whatever
you can just drop me a text/videocall to make sure its me to ask this"

In my case I was replacing a 2k key with a 4k one, so I got some signatures 
with not many troubles
spamming on irc with my account, with whatsapp/text/skype in other cases was 
enough to make sure they were
trusting me.

But that said, it really depends on them, and on your process to make them 
confident that you are the owner/requester
for the different signing.

I hope this helps, maybe this should be reviewed by somebody authoritative and 
put on a wiki,
I'm not aware of such "standardized" process

Gianfranco

Bug#830711: marked as done (RFS: adabrowse/4.0.3-7)

[Debian Bug Tracking System]

Your message dated Mon, 11 Jul 2016 11:23:46 +0200
with message-id <20160711092346.GA4264@pegase>
and subject line RFS: adabrowse/4.0.3-7
has caused the Debian Bug report #830711,
regarding RFS: adabrowse/4.0.3-7
to be marked as done.

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

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


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

Hello,

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

 * Package name: adabrowse
   Version : 4.0.3-7
   Upstream Author : Thomas Wolf 
 * URL : http://home.datacomm.ch/t_wolf/tw/ada95/adabrowse/
 * License : GPL-2+
   Section : devel

  It builds those binary packages:

adabrowse  - HTML generator for Ada 95 library unit specifications

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

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


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

dget -x
https://mentors.debian.net/debian/pool/main/a/adabrowse/adabrowse_4.0.3-7.dsc

The package has been transitioned to the gnat-6 compiler and thus fixes
bugs #827099 and #830401. I would be glad if someone uploaded this
package for me.

Regards,
Adrian
--- End Message ---
--- Begin Message ---
Hello.
I have updated your package in the unstable distribution.--- End Message ---

Re: How to upgrade my gpg key to debian standards?

[Elena ``of Valhalla'']

On 2016-07-10 at 22:53:46 +, Sean Whitton wrote:
> - https://debian-administration.org/users/dkg/weblog/48
> - https://help.riseup.net/en/security/message-security/openpgp/best-practices
> - the hopenpgp-tools package to check your key -- very useful!

I would also recommend:

https://wiki.debian.org/Subkeys

And possibly 

https://wiki.debian.org/GnuPG/AirgappedMasterKey
https://wiki.debian.org/GnuPG/SmartcardSubkeys

-- 
Elena ``of Valhalla''

Bug#830756: RFS: minetest-mod-animals (ITP)

[Julien Puydt]

Package: sponsorship-requests
Severity: wishlist

  Dear mentors,

  I am looking for a sponsor for my package "minetest-mod-animals"

 * Package name: minetest-mod-animals
   Version : 2.5.0-1
   Upstream Author : sapier
 * URL : https://github.com/sapier/animals_modpack
 * License : CC-BY-SA-3.0
   Section : games

  It builds those binary packages:

minetest-mod-animals - Minetest mod providing animals

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


  https://mentors.debian.net/package/minetest-mod-animals


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

dget -x 
https://mentors.debian.net/debian/pool/main/m/minetest-mod-animals/minetest-mod-animals_2.5.0-1.dsc


  It is packaged within the Debian Games Team:
Vcs-Git: https://anonscm.debian.org/git/pkg-games/minetest-mod-animals.git
Vcs-Browser: 
https://anonscm.debian.org/cgit/pkg-games/minetest-mod-animals.git


  Regards,
   Julien Puydt

Bug#830753: RFS: minetest-mod-animalmaterials (ITP)

[Julien Puydt]

Package: sponsorship-requests
Severity: wishlist

  Dear mentors,

  I am looking for a sponsor for my package "minetest-mod-animalmaterials"

 * Package name: minetest-mod-animalmaterials
   Version : 0.1.3-1
   Upstream Author : sapier
 * URL : https://github.com/sapier/animalmaterials
 * License : CC-BY-SA-3.0, CC-0 and animalmaterials-license
   Section : games

  It builds those binary packages:

minetest-mod-animalmaterials - Minetest mod providing models for 
animals


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


  https://mentors.debian.net/package/minetest-mod-animalmaterials


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

dget -x 
https://mentors.debian.net/debian/pool/main/m/minetest-mod-animalmaterials/minetest-mod-animalmaterials_0.1.3-1.dsc


  It is packaged within the Debian Games Team repository:
Vcs-Git: 
https://anonscm.debian.org/git/pkg-games/minetest-mod-animalmaterials.git 

 Vcs-Browser: 
https://anonscm.debian.org/cgit/pkg-games/minetest-mod-animalmaterials.git



  Regards,
   Julien Puydt