ampache package

2019-11-04 Thread Andreas Natanael Nielsen

Hey

I would like to know if the package: ampache is going to be available in 
future releases?



Regards
*Andreas*


Bug#944110: anacron: Incorrect behavoiur when using @monthly period_name

2019-11-04 Thread Santiago Castillo Oli

Package: anacron
Version: 2.3-28
Severity: normal

Dear Maintainer,

I see that @monthly is not a feature of anacron upstream, but it belongs 
to a debian patch.


I have found that @monthly period_name doesnt work well sometimes.

Let's see an example: I have an job that was last executed by anacron on 
the first of october.
The expected behaviour would be that the next execution will happen on 
the first of november.

But the truth is that the next execution happens on the 31st of october.

Looking at lock.c code I see:

 if (jr->named_period)
    {
    int period = 0, bypass = 0;
    switch (jr->named_period)
    {
    case 1:
    period = days_last_month ();
    bypass = days_this_month ();
    break;
    case 2:
    period = days_last_year ();
    bypass = days_this_year ();
    break;
    default:
    die ("Unknown named period for %s (%d)", jr->ident, 
jr->named_period);

    }
    if (day_delta < period && day_delta != bypass)
    {
    /* Job is still too young */
    xclose (jr->timestamp_fd);
    return 0;
    }
    }



Last execution (with MMDD notation): 20191001

Current day: 20191031

day_delta=30

period=30 (Number of days in september)

bypass=31 (Number of days in octuber)

(day_delta < period && day_delta != bypass) = (30 < 30 && 30 !=31) = 
(FALSE && TRUE) = FALSE, so the job is executed today



In this case the job is run on the 1st and on the 31st day of october. 
Two times in a month. The next one will be at the end of november.
I think this is wrong. If first run is on 1st day it should be again the 
first day of following months, assuming that the machine is turned up 
everyday.



Not sure about (day_delta < period && day_delta != bypass). It doesn't 
work in this case, but it doesnt work with another dates: (i.e.: last 
execution on january 31st, won't run on february, but on the first of 
march))




Can this be fixed, please?


Thank you and regards.





-- System Information:
Debian Release: 10.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.19.0-6-686-pae (SMP w/2 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_ES.UTF-8 (charmap=UTF-8)

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages anacron depends on:
ii  debianutils  4.8.6.1
ii  libc6    2.28-10
ii  lsb-base 10.2019051400

Versions of packages anacron recommends:
ii  cron [cron-daemon]   3.0pl1-134
ii  rsyslog [system-log-daemon]  8.1901.0-1

Versions of packages anacron suggests:
ii  exim4-daemon-light [mail-transport-agent]  4.92-8+deb10u3
ii  powermgmt-base 1.34

-- no debconf information



Processing of xmldiff_2.4-1_source.changes

2019-11-04 Thread Debian FTP Masters
xmldiff_2.4-1_source.changes uploaded successfully to localhost
along with the files:
  xmldiff_2.4-1.dsc
  xmldiff_2.4.orig.tar.gz
  xmldiff_2.4-1.debian.tar.xz
  xmldiff_2.4-1_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)



xmldiff_2.4-1_source.changes ACCEPTED into unstable

2019-11-04 Thread Debian FTP Masters



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 Nov 2019 12:15:11 -0300
Source: xmldiff
Architecture: source
Version: 2.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Thiago Andrade Marques 
Changes:
 xmldiff (2.4-1) unstable; urgency=medium
 .
   * QA upload.
   * New upstream version 2.4.
   * debian/copyright: updated the upstream copyright years and added a
   new upstream.
   * debian/manpage/:
   - Duplicated the code of create-man.sh to generate two manpages.
   - Updated all files to generate updated 2.4 manpages.
Checksums-Sha1:
 cdb0fd08fb188b5f4979013a5a67aba994a86fa0 1930 xmldiff_2.4-1.dsc
 02085e0fcce184a56fb1058ff4bb84306c61680c 93437 xmldiff_2.4.orig.tar.gz
 d44f242f27aba624d297d1e733e2a46a1aecfa5c 8064 xmldiff_2.4-1.debian.tar.xz
 81aa897562a1d0f00c4e6994aeea950e93a390bf 6923 xmldiff_2.4-1_source.buildinfo
Checksums-Sha256:
 c140d90d26392a2a5a94d15ee8b99c1a5671bef208e1665490269a1bb05c 1930 
xmldiff_2.4-1.dsc
 3391b2fec2583352e522eda39b8e1a999e364fa6f6e25f3baf52e3e3aa5e9015 93437 
xmldiff_2.4.orig.tar.gz
 2ee0e501c6025f0fc2fc4da3610ad7d75d240ea5cb5e3a07220ec5a248ebae38 8064 
xmldiff_2.4-1.debian.tar.xz
 69c1d9b18105bc3299a30f9dc5ed115671fd86786a6c2c25e05e82084e704abe 6923 
xmldiff_2.4-1_source.buildinfo
Files:
 f291ee78699a4ae69557f63328a8e160 1930 misc optional xmldiff_2.4-1.dsc
 d61ea3d9a36a110cd2a1562c08fbd307 93437 misc optional xmldiff_2.4.orig.tar.gz
 4b1a2d149b2e31959df3ff102cdb3823 8064 misc optional xmldiff_2.4-1.debian.tar.xz
 a0747bfb8cb2907ef3cb368d4054aa31 6923 misc optional 
xmldiff_2.4-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAl3AXu8ACgkQ3mO5xwTr
6e864w/+I3y+bZcs4xWecvk1qKsackSnvZMkxVHiBLGN7WOanwBjsGYJwimoipOo
zmiAc5TYTyQ/3qGgIiKhTbhfoLKph/VtgnGGN3JMUOfx+401bdPEOh6x7YwFqlHf
0VdIJSaxVspyqqdNACD32bA6Gto2aGD1AWzwqlcFVdJtWLtEgLNvQphBvIBdDGkV
7qaE0OAqQyOP1EH/qvr44LGNyHuv944XU2ON1BkOEqOw1upL6H8HOhLXybKbgsxV
4SkcIE/XmHtUwJG6kU17PzwUQGlH7Ocf16K4m9aoZZ6REh3Ocl+jWfv1DiX7Ndl9
p1h7Jryo+z1CHH7a3EUIlPKM1QDiIO1NcPMnbKP6B2OfzJma+9P/CHX4rDE8CUPC
tn/I94pF65BJazgZIh19qZhBYKxAbfCzsCH7NXxEFNj3HV3HN+fQzK5qzqJY46Yc
qrNa/f+ahC8mELFyMsGr/lDOrJltegTLijMEr28yqrGddsa23azz/uKsfNiR1WAc
rSDEwRqr+uiNLeupYLm6tJ4wPuVEI49SVe0Hsc4/xVDgQSQl4LRem7Vsqdl9HH1n
LyntE3WWWz2C6D90W5WBQaWHPuK5WFaGdp2LSzx15ansMh33mp12nVDzDFfFgHib
fjGcyUR1iM4jH4tm/dNVUCYwbMzJTBb6EJAzEAqyMP6vILZZGXw=
=jb11
-END PGP SIGNATURE-


Thank you for your contribution to Debian.



Bug#944131: splitpatch: please make the build reproducible

2019-11-04 Thread Chris Lamb
Source: splitpatch
Version: 1.0+20190128+git3b2edf2-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0] we noticed that
splitpatch could not be built reproducibly.

This is because my previous patch used $$(shell …) instead of $(shell
…) (note the change of number of dollar signs...) so that we were
still embedding today's date into the pod2man --center argument.

Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/reproducible-build.patch   1969-12-31 16:00:00.0 
-0800
--- b/debian/patches/reproducible-build.patch   2019-11-04 10:30:30.092883126 
-0800
@@ -0,0 +1,18 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2019-11-04
+
+--- splitpatch-1.0+20190128+git3b2edf2.orig/man/pod2man.mk
 splitpatch-1.0+20190128+git3b2edf2/man/pod2man.mk
+@@ -39,9 +39,9 @@ MANSECT  ?= 1
+ 
+ DATE_FMT = %Y-%m-%d
+ ifdef SOURCE_DATE_EPOCH
+-PODCENTER ?= $$(shell date -u -d "@$(SOURCE_DATE_EPOCH)" "+$(DATE_FMT)" 
2>/dev/null || date -u -r "$(SOURCE_DATE_EPOCH)" "+$(DATE_FMT)" 2>/dev/null || 
date -u "+$(DATE_FMT)")
++PODCENTER ?= $(shell date -u -d "@$(SOURCE_DATE_EPOCH)" "+$(DATE_FMT)" 
2>/dev/null || date -u -r "$(SOURCE_DATE_EPOCH)" "+$(DATE_FMT)" 2>/dev/null || 
date -u "+$(DATE_FMT)")
+ else
+-PODCENTER ?= $$(date "$(DATE_FMT)")
++PODCENTER ?= $(date "$(DATE_FMT)")
+ endif
+ 
+ # Directories
--- a/debian/patches/series 1969-12-31 16:00:00.0 -0800
--- b/debian/patches/series 2019-11-04 10:30:28.792869453 -0800
@@ -0,0 +1 @@
+reproducible-build.patch


Processed: Re: splitpatch: please make the build reproducible

2019-11-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 944131 https://github.com/jaalto/splitpatch/pull/8
Bug #944131 [src:splitpatch] splitpatch: please make the build reproducible
Set Bug forwarded-to-address to 'https://github.com/jaalto/splitpatch/pull/8'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
944131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944131
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#944131: splitpatch: please make the build reproducible

2019-11-04 Thread Chris Lamb
forwarded 944131 https://github.com/jaalto/splitpatch/pull/8
thanks

I've forwarded this upstream here:

  https://github.com/jaalto/splitpatch/pull/8


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-



Re: ampache package

2019-11-04 Thread Neil Williams
On Mon, 4 Nov 2019 13:06:16 +0100
Andreas Natanael Nielsen  wrote:

> Hey
> 
> I would like to know if the package: ampache is going to be available
> in future releases?

Probably not.
https://tracker.debian.org/pkg/ampache

"This package is not in any development repository. This probably means that 
the package has been removed (or has been renamed). Thus the information here 
is of little interest ... the package is going to disappear unless someone 
takes it over and reintroduces it."

https://www.debian.org/doc/manuals/developers-reference/pkgs.html#reintroducing-pkgs

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



pgp4PG_QJVZja.pgp
Description: OpenPGP digital signature


Bug#944131: marked as done (splitpatch: please make the build reproducible)

2019-11-04 Thread Debian Bug Tracking System
Your message dated Tue, 05 Nov 2019 02:40:32 +
with message-id 
and subject line Bug#944131: fixed in splitpatch 1.0+20190128+git3b2edf2-2
has caused the Debian Bug report #944131,
regarding splitpatch: please make the build reproducible
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.)


-- 
944131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944131
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: splitpatch
Version: 1.0+20190128+git3b2edf2-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0] we noticed that
splitpatch could not be built reproducibly.

This is because my previous patch used $$(shell …) instead of $(shell
…) (note the change of number of dollar signs...) so that we were
still embedding today's date into the pod2man --center argument.

Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/reproducible-build.patch   1969-12-31 16:00:00.0 
-0800
--- b/debian/patches/reproducible-build.patch   2019-11-04 10:30:30.092883126 
-0800
@@ -0,0 +1,18 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2019-11-04
+
+--- splitpatch-1.0+20190128+git3b2edf2.orig/man/pod2man.mk
 splitpatch-1.0+20190128+git3b2edf2/man/pod2man.mk
+@@ -39,9 +39,9 @@ MANSECT  ?= 1
+ 
+ DATE_FMT = %Y-%m-%d
+ ifdef SOURCE_DATE_EPOCH
+-PODCENTER ?= $$(shell date -u -d "@$(SOURCE_DATE_EPOCH)" "+$(DATE_FMT)" 
2>/dev/null || date -u -r "$(SOURCE_DATE_EPOCH)" "+$(DATE_FMT)" 2>/dev/null || 
date -u "+$(DATE_FMT)")
++PODCENTER ?= $(shell date -u -d "@$(SOURCE_DATE_EPOCH)" "+$(DATE_FMT)" 
2>/dev/null || date -u -r "$(SOURCE_DATE_EPOCH)" "+$(DATE_FMT)" 2>/dev/null || 
date -u "+$(DATE_FMT)")
+ else
+-PODCENTER ?= $$(date "$(DATE_FMT)")
++PODCENTER ?= $(date "$(DATE_FMT)")
+ endif
+ 
+ # Directories
--- a/debian/patches/series 1969-12-31 16:00:00.0 -0800
--- b/debian/patches/series 2019-11-04 10:30:28.792869453 -0800
@@ -0,0 +1 @@
+reproducible-build.patch
--- End Message ---
--- Begin Message ---
Source: splitpatch
Source-Version: 1.0+20190128+git3b2edf2-2

We believe that the bug you reported is fixed in the latest version of
splitpatch, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 944...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thiago Andrade Marques  (supplier of updated splitpatch 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 Nov 2019 20:37:29 -0300
Source: splitpatch
Architecture: source
Version: 1.0+20190128+git3b2edf2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Thiago Andrade Marques 
Closes: 944131
Changes:
 splitpatch (1.0+20190128+git3b2edf2-2) unstable; urgency=medium
 .
   * QA upload.
   * debian/control:
   - Added 'Rules-Requires-Root: no' in source stanza.
   - Bumped Standards-Version to 4.4.1.
   * debian/copyright: added rights for Thiago Andrade Marques.
   * debian/patches/010_reproducible-build.patch: added to
   fix an unreproducible condition. Thanks to Chris Lamb
   . (Closes: #944131)
   * debian/salsa-ci.yml: added to provide CI tests for Salsa.
Checksums-Sha1:
 795c0b70f391f9cc00a8556d5740ae3a93f18e3c 2016 
splitpatch_1.0+20190128+git3b2edf2-2.dsc
 f44bf056d1a590866d95f66a765b34fae83117d7 7016 
splitpatch_1.0+20190128+git3b2edf2-2.debian.tar.xz
 0a8571b451c42dc1192b81209d0911abbca26326 5262 
splitpatch_1.0+20190128+git3b2edf2-2_source.buildinfo
Checksums-Sha256:
 fcabe93152c19cf660d63abadaffc66d1d091d7df27088ca17b793d959b8f39b 2016 
splitpatch_1.0+20190128+git3b2edf2-2.dsc
 c8800da03d91f7087e79fa4e83cc76dee625f920a562daa5326dc466a10987f6 7016 
splitpatch_1.0+20190128+git3b2edf2-2.debian.tar.xz
 ac46d48f44a568782d4164fef6186fe22ab3d650ec66efa63d0d775a63592312 5262 
splitpatch_1.0+20190128+git3b2edf2-2_source.buildinfo
Files:
 a4bc

splitpatch_1.0+20190128+git3b2edf2-2_source.changes ACCEPTED into unstable

2019-11-04 Thread Debian FTP Masters



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 Nov 2019 20:37:29 -0300
Source: splitpatch
Architecture: source
Version: 1.0+20190128+git3b2edf2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Thiago Andrade Marques 
Closes: 944131
Changes:
 splitpatch (1.0+20190128+git3b2edf2-2) unstable; urgency=medium
 .
   * QA upload.
   * debian/control:
   - Added 'Rules-Requires-Root: no' in source stanza.
   - Bumped Standards-Version to 4.4.1.
   * debian/copyright: added rights for Thiago Andrade Marques.
   * debian/patches/010_reproducible-build.patch: added to
   fix an unreproducible condition. Thanks to Chris Lamb
   . (Closes: #944131)
   * debian/salsa-ci.yml: added to provide CI tests for Salsa.
Checksums-Sha1:
 795c0b70f391f9cc00a8556d5740ae3a93f18e3c 2016 
splitpatch_1.0+20190128+git3b2edf2-2.dsc
 f44bf056d1a590866d95f66a765b34fae83117d7 7016 
splitpatch_1.0+20190128+git3b2edf2-2.debian.tar.xz
 0a8571b451c42dc1192b81209d0911abbca26326 5262 
splitpatch_1.0+20190128+git3b2edf2-2_source.buildinfo
Checksums-Sha256:
 fcabe93152c19cf660d63abadaffc66d1d091d7df27088ca17b793d959b8f39b 2016 
splitpatch_1.0+20190128+git3b2edf2-2.dsc
 c8800da03d91f7087e79fa4e83cc76dee625f920a562daa5326dc466a10987f6 7016 
splitpatch_1.0+20190128+git3b2edf2-2.debian.tar.xz
 ac46d48f44a568782d4164fef6186fe22ab3d650ec66efa63d0d775a63592312 5262 
splitpatch_1.0+20190128+git3b2edf2-2_source.buildinfo
Files:
 a4bc38f60ece20a56fd864575a18ab24 2016 text optional 
splitpatch_1.0+20190128+git3b2edf2-2.dsc
 295490829e5431f91a946c1ea36a5fa2 7016 text optional 
splitpatch_1.0+20190128+git3b2edf2-2.debian.tar.xz
 5777fb079b816e9d1627184deacb0bc2 5262 text optional 
splitpatch_1.0+20190128+git3b2edf2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAl3A1kUACgkQ3mO5xwTr
6e+Xvw//bNtShFp3uDvKbA9Cuua/obIjWRPz0JMPYygO2ByoadPABcfWVSxYdxPF
5w25UPHyC+AE/mpobOUin0aD9GLGei6vfbGV9ZKtXJEYYCa/9q/PUIMPrTTW5ijB
H+8gzVvuifVUur0ozVSZpKYRl26BhnFK/OYJvs5XIdeFGD20/m9bpAaDCZUo7gCn
Lnl1LfAZsjOeb+Q1+Mrz2hfcPO/DQIc8/vGrzb1+SOFyl3jokDzTiMT9poFx+liZ
241mZ9mae5mZICZ+OPm5z0sU1sAQiLf1gr/2qj4FhHz3ZGr50JNb7iY7bpy2szDR
AZs5xB+QWThnMRWFW7tboQm8vCwxpNcMSQ8h65Se5wfyI6baJQ4WljpfWOguRCdv
OZ2SY3SNhEzB6C3uPBmToLOgnu79Byi138J1SMzhr5p3NjKCYQbqiwbYgUukQcft
k4OZ6HEwSEbccYdaVLf6wvPhlFNefNBEq8bwaZq09/NRIA0fNkD434iJFnLqACW+
3EMLbQo0kE3m91FOj/4Qu0cwh7MSBYSqig9avbSHx71Z4O/wp8vNDkPXfXwtWIRU
OSZKd8Rgl3xqdAGKNV+O1bdyb0UYYQmUuegvvg/YHcH37Ewaxrp2B50pLQmZU9En
4tfeqcDXJq0V/h/8IAaqMzGiwsUzLr7ctZ0L0icyfxRmCzCiD6A=
=NLZm
-END PGP SIGNATURE-


Thank you for your contribution to Debian.