RE: get 403 Forbidden when upload package to mentors.

[Xu, Guangxin]

Hi Paul:
Thanks for reply.
I tried this before, it's not working , so Giafranco suggest me use ftp.


I tried this again, it still failed
gxxu@zion-debian:~/works/pbuild/libyami-utils$ tsocks dput mentors 
libyami-utils_1.0.0-1_source.changes
Checking signature on .changes
gpg: Signature made Tue 18 Oct 2016 05:16:22 AM PDT using RSA key ID FF093896
gpg: Good signature from "Xu Guangxin "
Good signature on 
/home/gxxu/works/pbuild/libyami-utils/libyami-utils_1.0.0-1_source.changes.
Checking signature on .dsc
gpg: Signature made Tue 18 Oct 2016 05:16:19 AM PDT using RSA key ID FF093896
gpg: Good signature from "Xu Guangxin "
Good signature on 
/home/gxxu/works/pbuild/libyami-utils/libyami-utils_1.0.0-1.dsc.
Uploading to mentors (via http to mentors.debian.net):
  Uploading libyami-utils_1.0.0-1.dsc: Upload failed: 500 Internal Server Error

thanks

> -Original Message-
> From: paul.is.w...@gmail.com [mailto:paul.is.w...@gmail.com] On Behalf Of
> Paul Wise
> Sent: Tuesday, November 1, 2016 12:56 PM
> To: debian-mentors@lists.debian.org
> Subject: Re: get 403 Forbidden when upload package to mentors.
> 
> On Tue, Nov 1, 2016 at 12:45 PM, Xu, Guangxin wrote:
> 
> > I am behind a firewall, is it related?
> 
> Most likely.
> 
> > Or I need configure something.
> 
> Try using http instead of ftp to do the upload.
> 
> > Uploading to mentors-ftp (via ftp to mentors.debian.net):
> >   Uploading libyami-utils_1.0.0-1.dsc: 425 Security: Bad IP connecting.
> 
> Somehow this managed to create an empty dsc file. I've removed it now so you
> can try http.
> 
> --
> bye,
> pabs
> 
> https://wiki.debian.org/PaulWise

Re: How long to wait between RFA and QA upload?

[Adam Borowski]

On Tue, Nov 01, 2016 at 09:10:29AM +0800, gustavo panizzo (gfa) wrote:
> Recently I NMU'ed tsocks, as the shape of the package wasn't good [1]
> in the RFS email I said that I'd try to get the package orphaned so I can do 
> a proper QA upload.
> 
> The maintainer orphaned the package 2 days ago, #842555.
> 
> I don't want to adopt the package, but I do use it so I want to see it
> in good shape, how long should I wait for others that may adopt the
> package before I do a QA upload?.

One second, it's how long it takes to read whether the WNPP bug says "RFA"
or "O" -- the former doesn't make the package orphaned yet.

> I was going to send a notice regarding my QA upload to the O bug but I
> think it may discourage people from adopting the package.

Any problem you fix is one problem less for the adopter.

> The only guidance I found is 2 weeks,
> https://qa.debian.org/orphaned.html

That's for an empty upload just to set the Maintainer: field, something that
sounds like a waste of your time, buildd cycles and mirror bandwidth. 

Orphaned packages are up for grabs the moment the O is filed.


Meow!
-- 
A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol, 1kg
raspberries, 0.4kg sugar; put into a big jar for 1 month.  Filter out and
throw away the fruits (can dump them into a cake, etc), let the drink age
at least 3-6 months.

Re: Bug#842528: RFS: wide-dhcpv6/20080615-17 -- DHCPv6 server/client for automatic IPv6 hosts configuration

[Adam Borowski]

On Mon, Oct 31, 2016 at 11:36:02PM +, Gianfranco Costamagna wrote:
> >However the buildd seems not like my upload this time.
> >I guess it's caused by parallel support from debhelper 10.
> 
> not outdated, just like mine, we don't use parallel in building
> 
> DEB_BUILD_OPTIONS=parallel=8 can reproduce the issue (and bad me
> I didn't check that)
> probably some dependencies are not handled correctly in Makefile.in
> and having parallel enabled by default in compat 10 can't work.

No one's using a 1-core conventional computer these days.  By failing to set
parallel=X you gain nothing but wait much longer, and miss issues like this.

Why won't you put "export DEB_BUILD_OPTIONS=parallel=8" into your ~/.bashrc?
It's not like your number of cores changes, and even if it does, you can
export DEB_BUILD_OPTIONS=parallel=`nproc`

(Please don't use `grep ^processor /proc/cpuinfo` nor `getconf
_NPROCESSORS_ONLN` as neither is portable enough.)

-- 
A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol, 1kg
raspberries, 0.4kg sugar; put into a big jar for 1 month.  Filter out and
throw away the fruits (can dump them into a cake, etc), let the drink age
at least 3-6 months.

Build-Depends on source itself

[Jerome BENOIT]

Dear mentors,

for one of my package, libgap-sage [1], the source material used for build
is in fact seded meterial from an other package, gap: grossely the sed process
is the main part of libgap package: is there a standard way to use the Debian
source package of gap inside my own package libgap-sage ?
Any hint or example is welcome.

Thanks in advance,
Jerome


[1] https://packages.qa.debian.org/libg/libgap-sage.html
-- 
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B

Re: Build-Depends on source itself

[Paul Wise]

On Tue, Nov 1, 2016 at 12:43 PM, Jerome BENOIT wrote:

> for one of my package, libgap-sage [1], the source material used for build
> is in fact seded meterial from an other package, gap: grossely the sed process
> is the main part of libgap package: is there a standard way to use the Debian
> source package of gap inside my own package libgap-sage ?
> Any hint or example is welcome.

At this time there is no way for source packages to build-depend on
other source packages.

The most often used workaround for this is binary packages with
-source at the end of their names:

$ aptitude search -- -source$

If you can provide some details about your situation, we can probably
find a better solution.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Build-Depends on source itself

[Jerome BENOIT]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear mentors,

for one of my package, libgap-sage [1], the source material used for build
is in fact seded meterial from an other package, gap: grossely the sed process
is the main part of libgap package: is there a standard way to use the Debian
source package of gap inside my own package libgap-sage ?
Any hint or example is welcome.

Thanks in advance,
Jerome

 
[1] https://packages.qa.debian.org/libg/libgap-sage.html
- -- 
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B
-BEGIN PGP SIGNATURE-

iQQcBAEBCgAGBQJYGB1rAAoJED+SGaZ/NsaL+TUgALx4hUZVrTaZELF6szZXMunC
kFDTosjret1CmpDtNzaxeqpgvbc4csca/a9KUqd8ryigSmwEATN9dd6bZs+aE8Xn
sw8Xuk1yqf91AW76z87pVnX0FBuBKdaSKJpQGqgOa/uiNZ/iw7QBUAawhMeTNGPr
iOvRbqPp36c5pmEZI92Oc0nKpxrXfAKclbwXd/Neqpbb/LoRlxiBhau3KXJRQuwa
CCFLm783c8RqImeJnRCnFTB2VsqGO2fRLxR6+x0xyYQxKY4EZn6yD6adQQf8PUT3
t+z+P89JrFqwCAZrn8Sxg5BuQ1azF3lEoVxPr30GrWjoK6T3tNblYtSRrnmPJsNT
vR4QN7RKClfH2dqgDDmqKRlOsjtYchY7TxjdY6gl4vKxAoj1yEy4NTC3H5VLww54
aj1hBacYXVaEHvxKC0ojiLd7TLUbWv5/rmUp+mGsTaKEN5RD7pf4WrCr9dWuZM/6
QHG8Tz/xxAfYXeVmDccJfKzqg7N+/vKpUOnmRceMInatXEnhMeqz6r/XMktlFDNg
jINVvS2Gc/Z17bzK/4vZSGFR7/UhRzW3nE/uG2hN9fSlSLsv5qQ96wHnuIslBmtM
gyRaHRK7GPo7rptbQ6fuGgX6ZS13LZGNBRALgw8+sDp/M4ju5wOKWhb0sXUDjSk/
3JuzWmToUdUjMisbiqyo0G53Na0Eoy6ZLjO7Q6l4KGdfm+EiSN/To3LN/b9pLH0M
hi92CPMVuzm72cpdwgAArmRTJoIcuvG5r9e73PdTqoOd+IEgqNCd2THrGFixsOVp
ZXTJ8O49Vi9q8cpQM8MCUH1GR4TMBNCSns604Tv+DJgj/GQQ9TBGv3crR80b7bNo
4QTllXYAkZDDu/c2YDQV31bni36ivVQmfmHpiFkAkdjsNXNlMxWKPBijrIo/+Xmz
rjcPlmiDWzZDMlfPvM6r+TOOUnDCaV9VkYnVWdu72hWp4Sr0IlDnp34I5wHuWQWP
ECMSFoUh84MaD3DK8hRfhU7ORMDEPOCNPfo/lg/kwzYtfxxt99berq6NrvSy57j9
LoRyShy09n44gKkd5gKvp31Ir55da3vXuMu+PI6q+9aMY4mpGm8HPMu0fta8MvCb
fv6Eth7bni1ITcm4B8EmjqZdY7ahRxZJs51zLky8B9AssFW8BOP0eRai6a2v0OiO
dNSO+fZryRn+pqEWwho5XuVyqPeI3qq2AOrAdWqcMuWgY8iFuqRwzXimDp5+voI+
jrmdTvTSU+/1noanBHgHYbv7HUgzc3YEpLyA0RVcQv41NshIICFLPeLU7H3Jv5/v
ebTpp4oqyLVXKLjnACqcukiPWM9D4P7DEGSj7ZmXRpBJzg535CAFzAGylmNs2BQ=
=Xt8K
-END PGP SIGNATURE-

Re: get 403 Forbidden when upload package to mentors.

[Paul Wise]

On Tue, Nov 1, 2016 at 12:45 PM, Xu, Guangxin wrote:

> I am behind a firewall, is it related?

Most likely.

> Or I need configure something.

Try using http instead of ftp to do the upload.

> Uploading to mentors-ftp (via ftp to mentors.debian.net):
>   Uploading libyami-utils_1.0.0-1.dsc: 425 Security: Bad IP connecting.

Somehow this managed to create an empty dsc file. I've removed it now
so you can try http.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

RE: get 403 Forbidden when upload package to mentors.

[Xu, Guangxin]

Hi G.:
I tried this before; it will report bad IP connecting
I am behind a firewall, is it related? 
Or I need configure something.

Thanks.

gxxu@zion-debian:~/works/pbuild/libyami-utils$ tsocks dput mentors-ftp 
libyami-utils
libyami-utils-1.0.0/  libyami-utils_1.0.0-1_amd64.changes   
libyami-utils_1.0.0-1_source.changes
gxxu@zion-debian:~/works/pbuild/libyami-utils$ tsocks dput mentors-ftp 
libyami-utils_1.0.0-1_source.changes
Checking signature on .changes
gpg: Signature made Tue 18 Oct 2016 05:16:22 AM PDT using RSA key ID FF093896
gpg: Good signature from "Xu Guangxin "
Good signature on 
/home/gxxu/works/pbuild/libyami-utils/libyami-utils_1.0.0-1_source.changes.
Checking signature on .dsc
gpg: Signature made Tue 18 Oct 2016 05:16:19 AM PDT using RSA key ID FF093896
gpg: Good signature from "Xu Guangxin "
Good signature on 
/home/gxxu/works/pbuild/libyami-utils/libyami-utils_1.0.0-1.dsc.
Uploading to mentors-ftp (via ftp to mentors.debian.net):
  Uploading libyami-utils_1.0.0-1.dsc: 425 Security: Bad IP connecting.


> -Original Message-
> From: Gianfranco Costamagna [mailto:costamagnagianfra...@yahoo.it]
> Sent: Monday, October 31, 2016 7:13 PM
> To: Xu, Guangxin ; debian-mentors@lists.debian.org
> Cc: Yu, Jiankang ; Li, Jocelyn 
> Subject: Re: get 403 Forbidden when upload package to mentors.
> 
> Hi,
> 
> >  Uploading libyami_1.0.0.orig.tar.gz: Upload failed: 503 Service Unavailable
> 
> 
> 
> 
> sometimes it happens, just try again
> ftp://mentors.debian.net/
> seems empty now
> 
> G.

Re: Data updates in debian packages

[Russ Allbery]

Ole Streicher  writes:

> We need it to put correct time on astronomical registrations, so it is
> most important to have them once they are effective. Having them in
> advance would be an additional plus, however, since f.e. a computer may
> be disconnected during/after the observation, if that happens on a place
> without internet connection.

Christian's data is excellent.  I can also add that, having followed the
project for a while, I think it's pretty safe to assume that tzdata will
have the updated leap seconds in a released version and therefore in a
Debian stable package before the leap second takes effect with a high
level of reliability, and probably at least several months before.

I was mostly worried if you needed the data ASAP after an IERS
announcement, since the leap second data is sufficiently ancillary to the
tz project that it probably wouldn't, by itself, trigger a new release.
So the update would wait for some other time zone change to be rolled into
a release.

-- 
Russ Allbery (r...@debian.org)   

Re: How long to wait between RFA and QA upload?

[Paul Wise]

On Tue, Nov 1, 2016 at 9:10 AM, gustavo panizzo (gfa) wrote:

> The only guidance I found is 2 weeks,
> https://qa.debian.org/orphaned.html

That doesn't say to wait before doing QA uploads.

> how long should I wait between an O bug and a QA upload?

Waiting shouldn't be needed at all. Check that the O bug doesn't have
any potential adopters though.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

How long to wait between RFA and QA upload?

[gustavo panizzo (gfa)]

Hello

Recently I NMU'ed tsocks, as the shape of the package wasn't good [1]
in the RFS email I said that I'd try to get the package orphaned so I can do a 
proper QA upload.

The maintainer orphaned the package 2 days ago, #842555.

I don't want to adopt the package, but I do use it so I want to see it
in good shape, how long should I wait for others that may adopt the
package before I do a QA upload?.

I was going to send a notice regarding my QA upload to the O bug but I
think it may discourage people from adopting the package.

The only guidance I found is 2 weeks,
https://qa.debian.org/orphaned.html


TL;DR

how long should I wait between an O bug and a QA upload?

thanks!

[1] we can further discuss this, but I don't think is necessary at this point

-- 
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333

keybase: https://keybase.io/gfa


signature.asc
Description: PGP signature

Bug#842528: RFS: wide-dhcpv6/20080615-17 -- DHCPv6 server/client for automatic IPv6 hosts configuration

[Gianfranco Costamagna]

Hi,


>Thanks for your trust!

>
>However the buildd seems not like my upload this time.
>I guess it's caused by parallel support from debhelper 10.
>Maybe because my PC is outdated :-P
>
>I'll try to fix this in couple of days.


not outdated, just like mine, we don't use parallel in building

DEB_BUILD_OPTIONS=parallel=8 can reproduce the issue (and bad me
I didn't check that)
probably some dependencies are not handled correctly in Makefile.in
and having parallel enabled by default in compat 10 can't work.

G.

Bug#842528: RFS: wide-dhcpv6/20080615-17 -- DHCPv6 server/client for automatic IPv6 hosts configuration

[Roger Shimizu]

On Tue, Nov 1, 2016 at 1:45 AM, Gianfranco Costamagna
 wrote:
> Hi Roger,
>
>>I am looking for a sponsor for my package "wide-dhcpv6"
>
> done
>>If it's convenient for you, please kindly setup DM upload permission
>>of this package for me.
>
> oh well, I gave them to you before reading the whole email :)

Dear Gianfranco,

Thanks for your trust!

However the buildd seems not like my upload this time.
I guess it's caused by parallel support from debhelper 10.
Maybe because my PC is outdated :-P

I'll try to fix this in couple of days.

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Bug#842641: Sv: Bug#842641: RFS: autoconf/2.69-10~bpo8+1

[Ben Pfaff]

On Mon, Oct 31, 2016 at 04:50:49PM +, Kristian Klausen wrote:
> BTW Ben if you want to take care for the backport by yourself, I'm happy to 
> cancel
> or give you the task :)

Please, be my guest, you are welcome to take this.  Thank you.

Bug#838941: RFS: duperemove/0.11~beta3-3 ITP

[Gianfranco Costamagna]

Hi,
>thanks for the review, I've fixed licenses now, can you review again?


lets see
> interval_tree_generic.h: GPL (v2 or later) (with incorrect FSF address)



still wrong (missing the later clause)

xxhash.c
^^ wrong license

G.

Bug#842520: RFS: glances/2.7.1.1-1

[Gianfranco Costamagna]

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

Hi,

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


missing licenses and copyrights:
e.g.

+++ glances-2.7.1.1/.ci/appveyor/install.ps12016-09-18 21:06:28.0 
+0200
@@ -0,0 +1,85 @@
+# Sample script to install Python and pip under Windows
+# Authors: Olivier Grisel and Kyle Kastner
+# License: CC0 1.0 Universal: http://creativecommons.org/publicdomain/zero/1.0/


+ * @license AngularJS v1.5.8
+ * (c) 2010-2016 Google, Inc. http://angularjs.org
+ * License: MIT
+ */


+ * @license
+ * lodash 
+ * Copyright jQuery Foundation and other contributors 
+ * Released under MIT license 
+ * Based on Underscore.js 1.8.3 
+ * Copyright Jeremy Ashkenas, DocumentCloud and Investigative Reporters & 
Editors


seems that they haven't been removed, but became embedded code copies,
so your debian/*.link removals is probably wrong


2) outdated copyright years

- * Copyright 2012-2015 The Dojo Foundation 
- * Copyright 2009-2015 Jeremy Ashkenas, DocumentCloud and Investigative 
Reporters & Editors
+ * Copyright 2011-2015 Twitter, Inc.
+ * Copyright 2011-2015 Twitter, Inc.
+ * Copyright jQuery Foundation and other contributors 
+ * Copyright Jeremy Ashkenas, DocumentCloud and Investigative Reporters & 
Editors

+# Copyright (C) 2015 Angelo Poerio 

Copyright: 2011-2015 Twitter, Inc



and so on

G.

Bug#842528: RFS: wide-dhcpv6/20080615-17 -- DHCPv6 server/client for automatic IPv6 hosts configuration

[Gianfranco Costamagna]

Hi Roger,


>I am looking for a sponsor for my package "wide-dhcpv6"


done
>If it's convenient for you, please kindly setup DM upload permission
>of this package for me.


oh well, I gave them to you before reading the whole email :)

G.

Bug#841222: Acknowledgement (RFS: patat)

[Félix Sipma]

Hi,

On 2016-10-30 10:14-0700, Sean Whitton wrote:
> I noticed that you've published your patch-queue/master branch.  Since
> that is a branch you will rebase, it's not a good idea to publish it
> (the gbp documentation recommends against publishing it).  Anyone who
> needs the branch can reconstruct it with `gbp pq import`.

OK, I unpublished patch-queue/master.

> Unfortunately, patat doesn't build against sid at present.  Hopefully
> this will be resolved within the next week or so.  In the meantime,
> there is some stuff you can improve:
> 
> On Tue, Oct 25, 2016 at 10:34:11PM +0200, Félix Sipma wrote:
>> On 2016-10-23 11:51-0700, Sean Whitton wrote:
>>> You should use "Forwarded: not-needed" (see DEP-3).
>> 
>> This does not seem to work with gbp-pq (see #785274), I propose to add this 
>> as
>> soon as gbp-pq supports DEP-3.
> 
> Indeed.  Dmitry Bogatov pointed out to me that you can put the
> Forwarded: header at the end of the patch description (just before the
> ---) and then gbp won't remove it.

It seems like gbp _does_ remove the Forwarded: header put just before the
---...

> I wanted to confirm that you'd forwarded your --version patch, but I
> couldn't without this header :)

This particular patch is not needed anymore (fixed upstream). I pushed a new
version to my repo, and will put this new version on mentors as soon as pandoc
gets installable again.

> 2. You can fix all of these Lintian tags, except possibly
> hardening-no-fortify-functions.  You should definitely deal with
> the warnings.
> 
> W: patat-dbgsym: debug-file-with-no-debug-symbols
 
 I've updated debian/rules to something matching
 stylish-haskell.
> 
> Your d/rules is fine, though I think that the override_dh_compress stanza
> is not needed: policy says you should only compress files above a
> certain size, and presumably dh_compress isn't compressing the README
> because it is smaller than that size.
> 
> On the next upload of stylish-haskell I will probably remove that
> stanza -- sorry to mislead you!

OK, I removed the override_dh_compress stanza.

> I: patat: spelling-error-in-binary usr/bin/patat Nam Name
> I: patat: spelling-error-in-binary usr/bin/patat isn't isn't
> I: patat: spelling-error-in-binary usr/bin/patat forward forward
> I: patat: spelling-error-in-binary usr/bin/patat upto up to
> I: patat: spelling-error-in-binary usr/bin/patat discontigous 
> discontiguous
> I: patat: spelling-error-in-binary usr/bin/patat uncomplete incomplete
> I: patat: spelling-error-in-binary usr/bin/patat The The
 
 Not sure about this one... Is "patat" too generic for lintian? I've
 added this to debian/lintian-overrides.
>>> 
>>> I don't understand.  It is pointing out misspellings, such as
>>> 'uncomplete', somewhere in the upstream source.  You can add a quilt
>>> patch to fix them, and forward it upstream.
>> 
>> As I didn't found anything matching these errors in the source, I thought it
>> was a generic error message concerning the binary name.
>> 
>> Now, that I understood the purpose of this check, I can only found these
>> mistakes in the binary itself, so I guess these are in the dependencies...
> 
> Okay.  In that case you should override them, with a comment in the
> overrides file explaining why.

I guess it is better to not override this warning, so that we don't forget that
the dependencies needs to be fixed.

> I: patat: hardening-no-bindnow usr/bin/patat I: patat:
> hardening-no-pie usr/bin/patat
> 
> I think that in order to pass hardening options to gcc, if you're
> willing to work on that, you'll need to abandon the CDBS build system
> you're using at present.  See the Makefile for keysafe[1] (not yet in
> Debian) to see how to pass the options, and the rules file for the
> stylish-haskell package to see how to do without CDBS.
 
 After reading this Makefile, I'm not sure how keysafe avoids
 hardening-no-bindnow and hardening-no-pie... Do you have any clue?
>>> 
>>> The Makefile propagates LDFLAGS, CFLAGS and CPPFLAGS through to ghc.
>>> Then you enable all hardening in your d/rules,[1] and the right flags
>>> get set by debhelper.
>>> 
>>> [1] https://wiki.debian.org/Hardening
>> 
>> I would like to wait a little before adding this: the default flags added to
>> gcc seems quite new, so I propose to have a look again when things stabilize.
> 
> Fair enough.
> 
> FWIW keysafe's hardening is working fine, except for PIE, which has to
> be disabled for Haskell atm.  https://git.spwhitton.name/keysafe

OK.

> 3. Please run upstream's test suite during the package build.
 
 Should be done now, I'm not sure about how I run tests... See
 debian/rules override_dh_auto_test
> 
> Okay.  I can't test this atm because patat can't be built in sid, but
> what you did looks sane.

OK.

>>> If help2man is insufficient, see again stylish-haskell where I use
>>> asciidoctor.
>> 
>> I'll try t

Bug#842641: RFS: autoconf/2.69-10~bpo8+1

[Gianfranco Costamagna]

Hi Alex, Ben, Kristian


>Gianfranco, are you planning to take responsibility for uploading this
>as it changes in Debian proper?  It is probably not a big
>responsibility, because autoconf changes rarely.  I'm willing to sponsor

>the uploads.

I would prefer Kristian to take care of this, but yeah, I'm planning
to help/sponsor him for jessie lifespan, since I'm interested in connman
backports, and meh, we are talking about one/two uploads each year :)

Kristian, are you happy with that?
You set yourself as uploader for the backport, so I take the answer as "yes"
(and the upload will show under my ddpo account, so I'll see probably issues 

too here)

BTW Ben if you want to take care for the backport by yourself, I'm happy to 
cancel
or give you the task :)

Gianfranco

Bug#842641: RFS: autoconf/2.69-10~bpo8+1

[Ben Pfaff]

On Mon, Oct 31, 2016 at 04:24:10PM +0100, Alexander Wirt wrote:
> On Mon, 31 Oct 2016, Ben Pfaff wrote:
> 
> > On Mon, Oct 31, 2016 at 11:16:18AM +0100, Gianfranco Costamagna wrote:
> > > Hi Ben,
> > > 
> > > > I am looking for a sponsor for my package "autoconf".
> > > > Some packages depends on the new --runstatedir option which was added 
> > > > in 2.69-9,
> > > > before they can be built for jessie-backports. Ex connman.
> > > > Is this request okay with you Ben, or do you want to handle it?
> > > 
> > > I sponsored this upload in deferred/10, let me know if it sounds good to 
> > > you
> > > (being in lowNMU threshold helps here :)  thanks for that)
> > 
> > Thanks for helping.  I was planning to sponsor, but it's even easier
> > since you got to it first.
> Autoconf is a very important package and I don't think we want a backport
> that is not maintained by a regular uploader.

Gianfranco, are you planning to take responsibility for uploading this
as it changes in Debian proper?  It is probably not a big
responsibility, because autoconf changes rarely.  I'm willing to sponsor
the uploads.

Bug#842641: RFS: autoconf/2.69-10~bpo8+1

[Alexander Wirt]

On Mon, 31 Oct 2016, Ben Pfaff wrote:

> On Mon, Oct 31, 2016 at 11:16:18AM +0100, Gianfranco Costamagna wrote:
> > Hi Ben,
> > 
> > > I am looking for a sponsor for my package "autoconf".
> > > Some packages depends on the new --runstatedir option which was added in 
> > > 2.69-9,
> > > before they can be built for jessie-backports. Ex connman.
> > > Is this request okay with you Ben, or do you want to handle it?
> > 
> > I sponsored this upload in deferred/10, let me know if it sounds good to you
> > (being in lowNMU threshold helps here :)  thanks for that)
> 
> Thanks for helping.  I was planning to sponsor, but it's even easier
> since you got to it first.
Autoconf is a very important package and I don't think we want a backport
that is not maintained by a regular uploader.

Alex- Backports ftpmaster

> 

Bug#842641: RFS: autoconf/2.69-10~bpo8+1

[Ben Pfaff]

On Mon, Oct 31, 2016 at 11:16:18AM +0100, Gianfranco Costamagna wrote:
> Hi Ben,
> 
> > I am looking for a sponsor for my package "autoconf".
> > Some packages depends on the new --runstatedir option which was added in 
> > 2.69-9,
> > before they can be built for jessie-backports. Ex connman.
> > Is this request okay with you Ben, or do you want to handle it?
> 
> I sponsored this upload in deferred/10, let me know if it sounds good to you
> (being in lowNMU threshold helps here :)  thanks for that)

Thanks for helping.  I was planning to sponsor, but it's even easier
since you got to it first.

Bug#842703: RFS: gnome-shell-extension-hard-disk-led/13, ITP 842701: -- Shows harddisk activity (IO speed read/write and LED) in GNOME Shell)

[Jonathan Carter (highvoltage)]

Package: sponsorship-requests
Severity: wishlist

Dear mentors (cc debian-python),

I am looking for a sponsor for my package "bundlewrap":

* Package name: gnome-shell-extension-hard-disk-led
  Version : 13~git20160916.6fe27b2-1
  Upstream Author : bigi 
* URL : https://github.com/biji/harddiskled
* License : GPL-3+
  Programming Lang: JavaScript
  Description : Shows harddisk activity (IO speed read/write and
LED) in GNOME Shell

It builds the following binary package:

gnome-shell-extension-hard-disk-led - Shows harddisk activity (IO speed
read/write and LED) in GNOME Shell)

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

https://mentors.debian.net/package/gnome-shell-extension-hard-disk-led

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

dget -x
https://mentors.debian.net/debian/pool/main/g/gnome-shell-extension-hard-disk-led/gnome-shell-extension-hard-disk-led_13~git20160916.6fe27b2-1.dsc

You can also find me (highvoltage) on #debian-mentors.

Thanks for your time and patience!

-Jonathan

Re: get 403 Forbidden when upload package to mentors.

[Gianfranco Costamagna]

Hi,

>  Uploading libyami_1.0.0.orig.tar.gz: Upload failed: 503 Service Unavailable




sometimes it happens, just try again
ftp://mentors.debian.net/
seems empty now

G.

Re: Non-NEW backports rejected with "ACL dm: NEW uploads are not allowed"

[Gianfranco Costamagna]

Hi,

>With Distribution: jessie-backports, golang-gopkg-cheggaaa-pb.v1 has
>now been accepted. But golang-github-fatih-color is still rejected
>with the same error "ACL dm: NEW uploads are not allowed". I tried
>ploading the latter both without and with an orig tarball.
>
>I attached once more the (unsigned) .changes file.



I don't see any error, and also rmadison agrees with me

$ rmadison -u debian golang-github-fatih-color
golang-github-fatih-color | 0.0~git20160225.0.4f7bcef-1~bpo8+1 | 
jessie-backports | source
golang-github-fatih-color | 1.0.0-2| testing
  | source
golang-github-fatih-color | 1.0.0-2| unstable   
  | source


$ rmadison -u debian golang-github-fatih-color-dev
golang-github-fatih-color-dev | 0.0~git20160225.0.4f7bcef-1~bpo8+1 | 
jessie-backports | all
golang-github-fatih-color-dev | 1.0.0-2| testing
  | all
golang-github-fatih-color-dev | 1.0.0-2| unstable   
  | all

so, I would just try again :)

G.

Bug#842656: marked as done (RFS: groonga/6.1.0-2)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 10:39:03 + (UTC)
with message-id <1847794046.1985399.1477910343...@mail.yahoo.com>
and subject line Re: Bug#842656: RFS: groonga/6.1.0-2
has caused the Debian Bug report #842656,
regarding RFS: groonga/6.1.0-2
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.)


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

Dear mentors,

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

* Package name: groonga
  Version : 6.1.0-2
  Upstream Author : Groonga Project 
* Url : http://groonga.org/
* Licenses: LGPL-2.1
  Section : database

It builds those binary packages:

  * groonga
  * groonga-server-common
  * groonga-server-gqtp
  * libgroonga-dev
  * libgroonga0
  * groonga-tokenizer-mecab
  * groonga-token-filter-stem
  * groonga-plugin-suggest
  * groonga-bin
  * groonga-httpd
  * groonga-doc
  * groonga-examples
  * groonga-munin-plugins

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

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

Alternatively, one can download the package with dget using this command:
dget -x 
https://mentors.debian.net/debian/pool/main/g/groonga/groonga_6.1.0-2.dsc


More information about groonga can be obtained from
http://groonga.org/

Changes since last upload:

* debian/patches/fix-nginx-FTBFS-on-kfreebsd.patch
- Add patch to fix FTBFS on kFreeBSD.

Regards,


pgpt193gZBtnL.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hi,

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


I moved the changelog entry to the latest version
(the copyright fixes belongs to this version) and sponsored
+groonga (6.1.0-2) unstable; urgency=medium
+
+  * debian/patches/fix-nginx-FTBFS-on-kfreebsd.patch
+- Add patch to fix FTBFS on kFreeBSD.
+  * debian/copyright
+- Add copyright about bundled ngx-mruby.
+
+ -- Kentaro Hayashi   Sun, 30 Oct 2016 07:31:31 +0900

G.


pgpEWkdeO5t3U.pgp
Description: PGP signature
--- End Message ---

Bug#842673: marked as done (RFS: nfft/3.3.2-1)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 10:35:33 + (UTC)
with message-id <134626101.1960891.1477910133...@mail.yahoo.com>
and subject line Re: Bug#842673: RFS: nfft/3.3.2-1
has caused the Debian Bug report #842673,
regarding RFS: nfft/3.3.2-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.)


-- 
842673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842673
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 "nfft"

* Package name: nfft
  Version : 3.3.2-1
  Upstream Author : Prof. Dr. Daniel Potts 


* URL : http://www-user.tu-chemnitz.de/~potts/nfft/
* License : GPL-2+
  Section : science

It builds those binary packages:

  libnfft3-2 - library for computing non-uniform Fourier transforms
  libnfft3-dev - development files for the NFFT library
  libnfft3-doc - documentation for the NFFT library
  libnfft3-double2 - library for computing non-uniform Fourier 
transforms (double prec
  libnfft3-long2 - library for computing non-uniform Fourier transforms 
(long-double
  libnfft3-single2 - library for computing non-uniform Fourier 
transforms (single prec


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


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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/n/nfft/nfft_3.3.2-1.dsc


Successful build on debomatic:


http://debomatic-amd64.debian.net/distribution#unstable/nfft/3.3.2-1/buildlog

Changes since the last upload:

  * New upstream version 3.3.2
  * Drop superfluous query for DEB_HOST_ARCH_CPU.

Regards,
Ghislain Vaillant
--- End Message ---
--- Begin Message ---
Hi,


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


done!

G.--- End Message ---

Bug#842673: RFS: nfft/3.3.2-1

[Ghislain Vaillant]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: nfft
  Version : 3.3.2-1
  Upstream Author : Prof. Dr. Daniel Potts 


* URL : http://www-user.tu-chemnitz.de/~potts/nfft/
* License : GPL-2+
  Section : science

It builds those binary packages:

  libnfft3-2 - library for computing non-uniform Fourier transforms
  libnfft3-dev - development files for the NFFT library
  libnfft3-doc - documentation for the NFFT library
  libnfft3-double2 - library for computing non-uniform Fourier 
transforms (double prec
  libnfft3-long2 - library for computing non-uniform Fourier transforms 
(long-double
  libnfft3-single2 - library for computing non-uniform Fourier 
transforms (single prec


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


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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/n/nfft/nfft_3.3.2-1.dsc


Successful build on debomatic:


http://debomatic-amd64.debian.net/distribution#unstable/nfft/3.3.2-1/buildlog

Changes since the last upload:

  * New upstream version 3.3.2
  * Drop superfluous query for DEB_HOST_ARCH_CPU.

Regards,
Ghislain Vaillant

Bug#842641: marked as done (RFS: autoconf/2.69-10~bpo8+1)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 11:16:18 +0100
with message-id 
and subject line Re: RFS: autoconf/2.69-10~bpo8+1
has caused the Debian Bug report #842641,
regarding RFS: autoconf/2.69-10~bpo8+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.)


-- 
842641: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842641
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 "autoconf".
Some packages depends on the new --runstatedir option which was added in 2.69-9,
before they can be built for jessie-backports. Ex connman.
Is this request okay with you Ben, or do you want to handle it?


 * Package name    : autoconf
 Version : 2.69-10~bpo8+1
 Upstream Author : autoc...@gnu.org
 * URL : https://www.gnu.org/software/autoconf/autoconf.html
 * License : GPL-3+
 Section : devel

It builds those binary packages:

  autoconf   - automatic configure script builder
 autoconf-doc - automatic configure script builder documentation

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/a/autoconf/autoconf_2.69-10~bpo8+1.dsc

More information about hello can be obtained from 
https://www.gnu.org/software/autoconf/autoconf.html

Changes since the last upload:


autoconf (2.69-10~bpo8+1) jessie-backports; urgency=medium

  * Rebuild for jessie-backports.

 -- Kristian Klausen   Sun, 30 Oct 2016 22:40:42 +


Regards,
 Kristian Klausen
--- End Message ---
--- Begin Message ---
Hi Ben,

> I am looking for a sponsor for my package "autoconf".
> Some packages depends on the new --runstatedir option which was added in 
> 2.69-9,
> before they can be built for jessie-backports. Ex connman.
> Is this request okay with you Ben, or do you want to handle it?

I sponsored this upload in deferred/10, let me know if it sounds good to you
(being in lowNMU threshold helps here :)  thanks for that)

I also sponsored connman in deferred/15, the debdiff is attached

--- connman-1.33/debian/changelog   2016-10-14 17:50:00.0 +0200
+++ connman-1.33/debian/changelog   2016-10-31 11:11:12.0 +0100
@@ -1,3 +1,10 @@
+connman (1.33-1~bpo8+1) jessie-backports; urgency=medium
+
+  * Rebuild for jessie-backports.
+  * Enforce autoconf minimum version
+
+ -- Kristian Klausen   Sun, 30 Oct 2016 18:45:55 +0100
+
 connman (1.33-1) unstable; urgency=medium
 
   [ Alexander Sack ]
@@ -42,6 +49,12 @@
 
  -- Alexander Sack   Tue, 06 Sep 2016 15:38:03 +0200
 
+connman (1.32-0.1~bpo8+1) jessie-backports; urgency=medium
+
+  * Rebuild for jessie-backports.
+
+ -- Kristian Klausen   Wed, 11 May 2016 22:59:23 +0200
+
 connman (1.32-0.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru connman-1.33/debian/control connman-1.33/debian/control
--- connman-1.33/debian/control 2016-10-14 17:50:00.0 +0200
+++ connman-1.33/debian/control 2016-10-31 11:11:12.0 +0100
@@ -2,10 +2,12 @@
 Maintainer: Alexander Sack 
 Uploaders: Mathieu Trudel-Lapierre ,
Shawn Landden ,
-   Alf Gaida 
+   Alf Gaida ,
+   Kristian Klausen 
 Section: net
 Priority: optional
 Build-Depends: debhelper (>= 10),
+   autoconf (>= 2.69-9~),
libudev-dev,
libglib2.0-dev,
libdbus-1-dev,

Kristian I hope it is ok for you :)

G.
diff -Nru connman-1.33/debian/changelog connman-1.33/debian/changelog
--- connman-1.33/debian/changelog   2016-10-14 17:50:00.0 +0200
+++ connman-1.33/debian/changelog   2016-10-31 11:11:12.0 +0100
@@ -1,3 +1,10 @@
+connman (1.33-1~bpo8+1) jessie-backports; urgency=medium
+
+  * Rebuild for jessie-backports.
+  * Enforce autoconf minimum version
+
+ -- Kristian Klausen   Sun, 30 Oct 2016 18:45:55 +0100
+
 connman (1.33-1) unstable; urgency=medium
 
   [ Alexander Sack ]
@@ -42,6 +49,12 @@
 
  -- Alexander Sack   Tue, 06 Sep 2016 15:38:03 +0200
 
+connman (1.32-0.1~bpo8+1) jessie-backports; urgency=medium
+
+  * Rebuild for jessie-backports.
+
+ -- Kristian Klausen   Wed, 11 May 2016 22:59:23 +0200
+
 connman (1.32-0.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru connman-1.33/debian/control connman-1.33/debian/control
--- connman-1.33/debian/control 2016-10-14 17:50:00.0 +0200
+++ connman-1.33/debian/control 2016-10-31 11:11:12.000

Re: Data updates in debian packages

[Christian Seiler]

On 10/31/2016 10:30 AM, Ole Streicher wrote:
>  debian/triggers --
> interest /usr/share/zoneinfo/leap-seconds.list
> ---8<--
> 
> However, I now get the following error when I try to update tzdata:
> 
> dpkg: cycle found while processing triggers:
>  chain of packages whose triggers are or may be responsible:
>   casacore-data-tai-utc -> casacore-data-tai-utc
>  packages' pending triggers which are or may be unresolvable:
>   casacore-data-tai-utc: /usr/share/zoneinfo/leap-seconds.list
> dpkg: error processing package casacore-data-tai-utc (--configure):
>  triggers looping, abandoned
> Errors were encountered while processing:
>  casacore-data-tai-utc
> 
> What is my mistake here?

Well, if your package Depends: on tzdata, then you created a cycle:
tzdata wants to trigger your package, but your package depends on
tzdata.

What you'll want to do is

interest-noawait ...

instead of

interest ...

A detailed explanation is man 5 deb-triggers together with
/usr/share/doc/dpkg-dev/triggers.txt.gz, but it's not easy to grok.
However, the recommendation in man 5 deb-triggers is something you
should follow, i.e. use -noawait triggers unless you really need
-await triggers for some reason.

Regards,
Christian

Re: Data updates in debian packages

[Ole Streicher]

Paul Wise  writes:
> On Sat, Oct 29, 2016 at 8:45 PM, Ole Streicher wrote:
>> The package in question (casacore) wants them in a specific format "CASA
>> table" (which is uniformly used within that package), and dependent
>> packages access this in that specific format. The only way would be to
>> create this table from another leap second table (instead of our current
>> source usno.navy.mil), and to update this every time the original table
>> is updated (which I would have to learn how to do this).
>
> You can use dpkg triggers to update files in response to packages
> updating other files.

I tried this, namely (the source package and has only one binary
package):

 debian/triggers --
interest /usr/share/zoneinfo/leap-seconds.list
---8<--

 debian/postinst --
#!/bin/sh

set -e

case "$1" in
triggered|configure)
casacore-update-tai_utc
;;
abort-upgrade|abort-remove|abort-deconfigure)
;;
*)
echo "postinst called with unknown argument \`$1'" >&2
exit 1
;;
esac

#DEBHELPER#
---8<--

However, I now get the following error when I try to update tzdata:

dpkg: cycle found while processing triggers:
 chain of packages whose triggers are or may be responsible:
  casacore-data-tai-utc -> casacore-data-tai-utc
 packages' pending triggers which are or may be unresolvable:
  casacore-data-tai-utc: /usr/share/zoneinfo/leap-seconds.list
dpkg: error processing package casacore-data-tai-utc (--configure):
 triggers looping, abandoned
Errors were encountered while processing:
 casacore-data-tai-utc

What is my mistake here?

Best regards

Ole

Re: Data updates in debian packages

[Ole Streicher]

Christian Seiler  writes:
> On 10/31/2016 09:07 AM, Ole Streicher wrote:
[leap seconds]
>> We need it to put correct time on astronomical registrations, so it is
>> most important to have them once they are effective. Having them in
>> advance would be an additional plus, however, since f.e. a computer may
>> be disconnected during/after the observation, if that happens on a place
>> without internet connection.
>
> Data might help here, so I've looked at the past 3 leap seconds that
> were introduced [...]
>
> What this does say is that stable/updates and oldstable (LTS) had
> updated leap seconds information slightly less than 3 months before
> the leap second, in some cases even a bit earlier. [...]
>
> Hope this information helps in you evaluating this.

Thank you very much for this detailed information! This helps a lot for
the decision (we will depend on tzdata), and it gives also a good
argument for discussion upstream.

Best regards

Ole

Re: Data updates in debian packages

[Christian Seiler]

On 10/31/2016 09:07 AM, Ole Streicher wrote:
> Russ Allbery  writes:
>> The required timeliness depends a lot on what you're using leap seconds
>> for, and in particular if you need to know about them far in advance, or
>> if it's only necessary to have an updated table before the leap second
>> itself arrives.
> 
> We need it to put correct time on astronomical registrations, so it is
> most important to have them once they are effective. Having them in
> advance would be an additional plus, however, since f.e. a computer may
> be disconnected during/after the observation, if that happens on a place
> without internet connection.

Data might help here, so I've looked at the past 3 leap seconds that
were introduced (I don't think it makes sense to go further back,
because the one before that was 2009, and that's probably too long
ago to draw conclusions):

Leap second | Jun 2012 | Jun 2015 | Dec 2016
+--+--+-
IERS ann.   |   2012-01-05 |   2015-01-05 |   2016-07-06
tzdata rel. | 2012a 2012-03-01 | 2015a 2015-01-29 | 2016g 2016-09-13
sid | 2012b 2012-03-06 | 2015a 2015-01-31 | 2016g 2016-09-28
stable  | 2016c 2012-05-05 | 2015a 2015-02-01 | 2016g 2016-10-03
stable PR   |   2012-05-12 |   2015-09-05 |   not yet
|  |  (now oldstable) | 
oldstable   | (Lenny EOL)  | 2015c 2015-04-17 | 2016h 2016-10-26

"stable" means stable/updates (former volatile), "stable PR" means
the stable point release that gathered up the all stable/updates,
stable-security and stable/proposed-updates and "oldstable" means
squeeze-lts and wheezy-security. (In both cases they were already LTS,
no leap second in the last 6 years has fallen into a window where we
had oldstable not being LTS.)

Note that the "stable PR" metric just shows you that you don't want
to run a system that needs up to date leap seconds data without
having stable/updates enabled, just because point releases are too
infrequent. (But that would apply to a new package tracking just
the leap seconds data from IERS as well.)

What this does say is that stable/updates and oldstable (LTS) had
updated leap seconds information slightly less than 3 months before
the leap second, in some cases even a bit earlier. If we are going
to assume that in a perfect storm this might be a bit worse, then I
think one can say that roughly 2 months in advance of a leap second
any officially supported Debian version will have updated an tzdata
package. (If you enable the proper repositories.)

(Btw. leap-seconds.list was only introduced upstream in 2013, and
packaged in the binary package in 2015; before that only the binary
rules files for each time zone contained the leap second info. See
. However, since this is used by
DSA, this is going to be kept around.)

Hope this information helps in you evaluating this.

Regards,
Christian

Re: Data updates in debian packages

[Ole Streicher]

Russ Allbery  writes:
> The required timeliness depends a lot on what you're using leap seconds
> for, and in particular if you need to know about them far in advance, or
> if it's only necessary to have an updated table before the leap second
> itself arrives.

We need it to put correct time on astronomical registrations, so it is
most important to have them once they are effective. Having them in
advance would be an additional plus, however, since f.e. a computer may
be disconnected during/after the observation, if that happens on a place
without internet connection.

Best regards

Ole