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

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

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

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 `-

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

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

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)

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)

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

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*