libstroke is marked for autoremoval from testing

[Debian testing autoremoval watch]

libstroke 0.5.1-7 is marked for autoremoval from testing on 2016-07-26

It is affected by these RC bugs:
128745: libstroke0-dev: aclocal is confused by libstroke .m4 files 
302907: libstroke0-dev: Need more quoting of autoconf macro files.

Bug#829027: [jw...@debian.org: Re: Bug#829027: libstroke: missing/obsolete coypright information]

[Sean Whitton]

Hello Hamish, Vincent,

On Fri, Jul 01, 2016 at 10:19:48AM +1000, Hamish Moffatt wrote:
> Looking around quickly I think the URL in the copyright file should have
> been www.etla.net/libstroke, which certainly appears to have been valid at
> the time of upload:
> https://web.archive.org/web/20011217134508/http://www.etla.net/libstroke/
> 
> The etla.net home page seems to have stopped mentioning libstroke in early
> 1999, after the first upload of libstroke.
> https://web.archive.org/web/19990208013017/http://www.etla.net/

Thank you for getting back to me so quickly, Hamish.  It seems like we
can fix this bug by just replacing the URL in the copyright file.

On Fri, Jul 01, 2016 at 02:31:20AM +0200, Vincent Lefevre wrote:
> http://www.etla.net/ has a link to http://etla.net/libstroke/ in 1999.
> I suspect that the maintainer forgot to update the URL in the new
> package versions after the link has been removed.

Yes, probably right.

> > No, there's no such requirement.
> 
> This makes the first requirement completely useless: the maintainer
> could have downloaded the sources 10 years before the software is
> Debianized with URLs obsolete for years, so that no-one can check.

If the purpose of the requirement is for FTP-master verification, as I
suggested, I suspect that they would reject something that was no longer
available at the time of upload.  So it's not useless.

If the requirement was that the website remained available so long as
the package is in Debian, the Debian archive would suddenly be beholden
to a lot of random webservers across the Internet staying online.  That
would be counter-productive.

-- 
Sean Whitton

Bug#829027: [jw...@debian.org: Re: Bug#829027: libstroke: missing/obsolete coypright information]

[Hamish Moffatt]

Hi Sean,

I honestly have no recollection of the order of events.

Looking around quickly I think the URL in the copyright file should have 
been www.etla.net/libstroke, which certainly appears to have been valid 
at the time of upload:

https://web.archive.org/web/20011217134508/http://www.etla.net/libstroke/

The etla.net home page seems to have stopped mentioning libstroke in 
early 1999, after the first upload of libstroke.

https://web.archive.org/web/19990208013017/http://www.etla.net/





regards,

Hamish

On 01/07/16 09:50, Sean Whitton wrote:

Dear Hamish,

I'm sorry to bother you about a package you have orphaned, but do you
recall where you downloaded the original sources for libstroke?

In the copyright file you said that you got them from etla.org, but per
the below e-mail, they weren't available from etla.org at the time you
uploaded the package to Debian.  Did you download them in 1999 and then
just not get around to uploading until 2002?

Hopefully we don't have an unfixable RC bug here.

Thanks!

- Forwarded message from Jakub Wilk  -

Date: Fri, 1 Jul 2016 01:19:23 +0200
From: Jakub Wilk 
To: Vincent Lefevre , 829...@bugs.debian.org
Cc: Sean Whitton 
Subject: Re: Bug#829027: libstroke: missing/obsolete coypright information
User-Agent: Mutt/1.5.23.1 (2014-03-12)
Message-ID: <20160630231923.ga2...@jwilk.net>

* Vincent Lefevre , 2016-06-30, 14:34:

The Debian policy manual says:

"In addition, the copyright file must say where the upstream sources
(if any) were obtained, and should name the original authors."

This clause is made up of two requirements:

1. "the copyright file must say where the upstream sources ... were
obtained"

2. "the copyright file ... should name the original authors"

libstroke does not violate the first requirement: the copyright file
does say where the upstream sources /were/ obtained, even though they
can no longer be obtained there.

According to archive.org, http://www.etla.net/ stopped mentioning libstroke
somewhere between February and March 1999. The current upstream release was
first uploaded in 2002, when the link was already invalid.


I thought that it would still be needed as long as the package is in
Debian (so that users could check too) so that the location should
implicitly still be valid.

No, there's no such requirement.

Bug#829027: libstroke: missing/obsolete coypright information

[Vincent Lefevre]

On 2016-07-01 01:19:23 +0200, Jakub Wilk wrote:
> * Vincent Lefevre , 2016-06-30, 14:34:
> > > > The Debian policy manual says:
> > > > 
> > > > "In addition, the copyright file must say where the upstream
> > > > sources (if any) were obtained, and should name the original
> > > > authors."
> > > 
> > > This clause is made up of two requirements:
> > > 
> > > 1. "the copyright file must say where the upstream sources ... were
> > > obtained"
> > > 
> > > 2. "the copyright file ... should name the original authors"
> > > 
> > > libstroke does not violate the first requirement: the copyright file
> > > does say where the upstream sources /were/ obtained, even though
> > > they can no longer be obtained there.
> 
> According to archive.org, http://www.etla.net/ stopped mentioning libstroke
> somewhere between February and March 1999. The current upstream release was
> first uploaded in 2002, when the link was already invalid.

http://www.etla.net/ has a link to http://etla.net/libstroke/ in 1999.
I suspect that the maintainer forgot to update the URL in the new
package versions after the link has been removed.

> > I thought that it would still be needed as long as the package is in
> > Debian (so that users could check too) so that the location should
> > implicitly still be valid.
> 
> No, there's no such requirement.

This makes the first requirement completely useless: the maintainer
could have downloaded the sources 10 years before the software is
Debianized with URLs obsolete for years, so that no-one can check.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: tagging 811723, tagging 811719, tagging 811717, found 811707 in 1.03+repack-3, tagging 811702 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 811723 + sid stretch
Bug #811723 [fcitx-unikey] fcitx-unikey: FTBFS with GCC 6: narrowing conversion
Added tag(s) stretch and sid.
> tags 811719 + sid stretch
Bug #811719 [fbterm] fbterm: FTBFS with GCC 6: narrowing conversion
Added tag(s) stretch and sid.
> tags 811717 + sid stretch
Bug #811717 [ivtools] ivtools: FTBFS with GCC 6: narrowing conversion
Added tag(s) stretch and sid.
> found 811707 1.03+repack-3
Bug #811707 [src:ucl] gcc-6 fails to compile a valid code
Marked as found in versions ucl/1.03+repack-3.
> tags 811702 + sid stretch
Bug #811702 [librg-blast-parser-perl] FTBFS with GCC 6: macro passed X 
arguments, takes Y
Added tag(s) sid and stretch.
> tags 811699 + sid stretch
Bug #811699 [mswatch] FTBFS with GCC 6: macro passed X arguments, takes Y
Added tag(s) sid and stretch.
> tags 811673 + sid stretch
Bug #811673 [pyodbc] FTBFS with GCC 6: cannot convert x to y
Added tag(s) sid and stretch.
> tags 811672 + sid stretch
Bug #811672 [qt4-perl] FTBFS with GCC 6: cannot convert x to y
Added tag(s) stretch and sid.
> tags 811671 + sid stretch
Bug #811671 [audacity] FTBFS with GCC 6: cannot convert x to y
Added tag(s) sid and stretch.
> tags 811663 + sid stretch
Bug #811663 [tora] FTBFS with GCC 6: cannot convert x to y
Added tag(s) sid and stretch.
> tags 811657 + sid stretch
Bug #811657 [libbpp-core] FTBFS with GCC 6: cannot convert x to y
Added tag(s) sid and stretch.
> tags 811656 + sid stretch
Bug #811656 [starvoyager] FTBFS with GCC 6: cannot convert x to y
Added tag(s) sid and stretch.
> tags 811655 + sid stretch
Bug #811655 [starplot] FTBFS with GCC 6: cannot convert x to y
Added tag(s) stretch and sid.
> tags 811654 + sid stretch
Bug #811654 [open-invaders] FTBFS with GCC 6: cannot convert x to y
Added tag(s) stretch and sid.
> tags 811653 + sid stretch
Bug #811653 [libaria] FTBFS with GCC 6: cannot convert x to y
Added tag(s) stretch and sid.
> tags 811647 + sid stretch
Bug #811647 [scorched3d] FTBFS with GCC 6: cannot convert x to y
Added tag(s) stretch and sid.
> tags 811645 + sid stretch
Bug #811645 [ams] FTBFS with GCC 6: cannot convert x to y
Added tag(s) sid and stretch.
> tags 811644 + sid stretch
Bug #811644 [idba] FTBFS with GCC 6: cannot convert x to y
Added tag(s) stretch and sid.
> tags 811643 + sid stretch
Bug #811643 [bloboats] FTBFS with GCC 6: cannot convert x to y
Added tag(s) sid and stretch.
> tags 811640 + sid stretch
Bug #811640 [dasher] FTBFS with GCC 6: cannot convert x to y
Added tag(s) stretch and sid.
> tags 811635 + sid stretch
Bug #811635 [libfolia] FTBFS with GCC 6: cannot convert x to y
Added tag(s) sid and stretch.
> tags 811634 + sid stretch
Bug #811634 [meshlab] FTBFS with GCC 6: cannot convert x to y
Added tag(s) stretch and sid.
> tags 811632 + sid stretch
Bug #811632 [hupnp] FTBFS with GCC 6: cannot convert x to y
Added tag(s) sid and stretch.
> tags 811629 + sid stretch
Bug #811629 [tagua] FTBFS with GCC 6: cannot convert x to y
Added tag(s) stretch and sid.
> tags 811628 + sid stretch
Bug #811628 [kyototycoon] FTBFS with GCC 6: cannot convert x to y
Added tag(s) sid and stretch.
> tags 811621 + sid stretch
Bug #811621 [critterding] FTBFS with GCC 6: cannot convert x to y
Added tag(s) sid and stretch.
> tags 811619 + sid stretch
Bug #811619 [gbgoffice] FTBFS with GCC 6: cannot convert x to y
Added tag(s) sid and stretch.
> tags 811616 + sid stretch
Bug #811616 [warmux] FTBFS with GCC 6: cannot convert x to y
Added tag(s) sid and stretch.
> tags 811595 + sid stretch
Bug #811595 [upx-ucl] FTBFS with GCC 6: statement indented as if it were 
guarded by
Added tag(s) sid and stretch.
> tags 811594 + sid stretch
Bug #811594 [chordii] FTBFS with GCC 6: statement indented as if it were 
guarded by
Added tag(s) sid and stretch.
> tags 811591 + sid stretch
Bug #811591 [ifhp] FTBFS with GCC 6: statement indented as if it were guarded by
Ignoring request to alter tags of bug #811591 to the same tags previously set
> tags 811588 + sid stretch
Bug #811588 [grail] FTBFS with GCC 6: statement indented as if it were guarded 
by
Added tag(s) sid and stretch.
> tags 811585 + sid stretch
Bug #811585 [clutter-gesture] FTBFS with GCC 6: statement indented as if it 
were guarded by
Added tag(s) stretch and sid.
> tags 811584 + sid stretch
Bug #811584 [phalanx] FTBFS with GCC 6: statement indented as if it were 
guarded by
Added tag(s) stretch and sid.
> tags 811582 + sid stretch
Bug #811582 [ion] FTBFS with GCC 6: statement indented as if it were guarded by
Added tag(s) stretch and sid.
> tags 811578 + sid stretch
Bug #811578 [confetti] FTBFS with GCC 6: statement indented as if it were 
guarded by
Added tag(s) sid and stretch.
> tags 829109 + sid stretch
Bug #829109 [src:acepack] acepack: FTBFS: dh_clean: Compatibility levels before 
5 are no longer supported (level 4 requested)
Added tag(s) sid and stretch.
> tags 822711 + sid stretch
Bug #822711 {Done: Paul Wise } [chromium-bsu] chromium-bsu: 
FTBFS with GCC 6: call 

Bug#829027: [jw...@debian.org: Re: Bug#829027: libstroke: missing/obsolete coypright information]

[Sean Whitton]

Dear Hamish,

I'm sorry to bother you about a package you have orphaned, but do you
recall where you downloaded the original sources for libstroke?

In the copyright file you said that you got them from etla.org, but per
the below e-mail, they weren't available from etla.org at the time you
uploaded the package to Debian.  Did you download them in 1999 and then
just not get around to uploading until 2002?

Hopefully we don't have an unfixable RC bug here.

Thanks!

- Forwarded message from Jakub Wilk  -

Date: Fri, 1 Jul 2016 01:19:23 +0200
From: Jakub Wilk 
To: Vincent Lefevre , 829...@bugs.debian.org
Cc: Sean Whitton 
Subject: Re: Bug#829027: libstroke: missing/obsolete coypright information
User-Agent: Mutt/1.5.23.1 (2014-03-12)
Message-ID: <20160630231923.ga2...@jwilk.net>

* Vincent Lefevre , 2016-06-30, 14:34:
>>> The Debian policy manual says:
>>> 
>>> "In addition, the copyright file must say where the upstream sources
>>> (if any) were obtained, and should name the original authors."
>> 
>> This clause is made up of two requirements:
>> 
>> 1. "the copyright file must say where the upstream sources ... were
>> obtained"
>> 
>> 2. "the copyright file ... should name the original authors"
>> 
>> libstroke does not violate the first requirement: the copyright file
>> does say where the upstream sources /were/ obtained, even though they
>> can no longer be obtained there.

According to archive.org, http://www.etla.net/ stopped mentioning libstroke
somewhere between February and March 1999. The current upstream release was
first uploaded in 2002, when the link was already invalid.

> I thought that it would still be needed as long as the package is in
> Debian (so that users could check too) so that the location should
> implicitly still be valid.

No, there's no such requirement.

-- 
Jakub Wilk

- End forwarded message -

-- 
Sean Whitton

Processed: Re: Bug#828540: sendmail: FTBFS with openssl 1.1.0

[Debian Bug Tracking System]

Processing control commands:

> tag -1 help
Bug #828540 [src:sendmail] sendmail: FTBFS with openssl 1.1.0
Added tag(s) help.

-- 
828540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828540
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#828540: sendmail: FTBFS with openssl 1.1.0

[Andreas Beckmann]

Control: tag -1 help

Hi Kurt,

maybe you can help me getting sendmail (which I'm QA maintaining for 
some years now) to work with the new openssl.

On 2016-06-26 12:24, Kurt Roeckx wrote:
> https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/sendmail_8.15.2-4_amd64-20160529-1535

> If you have problems making things work, feel free to contact us.

in debian/configure.ac we have

if test $ac_cv_header_openssl_ssl_h = yes; then
AC_CHECK_LIB(ssl, SSL_library_init,
[sm_have_tls=yes]
,[sm_have_tls=no]
,[-lcrypto])

if test $sm_have_tls != yes; then
AC_MSG_WARN([Could not find -lssl (libssl-dev)])
fi;
fi;

which fails. The whole autotools stuff is only used for the debian packaging.
That fails because SSL_library_init is now a macro instead of a function.
Maybe this check is superfluous and could just be removed.
If I do this, building fails due to some API changes:

gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I. 
-I../../include-DSOCKETMAP -DMAP_REGEX -DNEWDB -DNIS -DNISPLUS -DLDAPMAP  
-DHASFCHMOD=1 -DHASSETRLIMIT=1 -DHASFLOCK=0 -DUSESETEUID=1 -DHASGETUSERSHELL=1 
-DNETINET6  -D_PATH_SENDMAILPID=\"/var/run/sendmail/mta/sendmail.pid\" 
-DIP_SRCROUTE=1 -DLDAP_REFERRALS -D_FFR_LDAP_URI -D_FFR_LDAP_SETVERSION 
-DLDAP_DEPRECATED  -DTCPWRAPPERS -DSASL -I/usr/include/sasl -DSTARTTLS  
-D_FFR_QUEUE_SCHED_DBG -D_FFR_SKIP_DOMAINS -D_FFR_GROUPREADABLEAUTHINFOFILE 
-D_FFR_DAEMON_NETUNIX -D_FFR_NO_PIPE -D_FFR_SHM_STATUS -D_FFR_RHS 
-D_FFR_MAIL_MACRO -D_FFR_QUEUEDELAY=1 -D_FFR_BADRCPT_SHUTDOWN 
-D_FFR_RESET_MACRO_GLOBALS -D_FFR_TLS_1 -D_FFR_TLS_EC 
-D_FFR_DEAL_WITH_ERROR_SSL   -Wdate-time -D_FORTIFY_SOURCE=2  -c -o tls.o tls.c
tls.c: In function 'get_dh512':
tls.c:70:4: error: dereferencing pointer to incomplete type 'DH {aka struct 
dh_st}'
  dh->p = BN_bin2bn(dh512_p, sizeof(dh512_p), NULL);
^
tls.c: In function 'inittls':
tls.c:929:22: warning: implicit declaration of function 'BIO_s_file_internal' 
[-Wimplicit-function-declaration]
   crl_file = BIO_new(BIO_s_file_internal());
  ^
tls.c:929:22: warning: passing argument 1 of 'BIO_new' makes pointer from 
integer without a cast [-Wint-conversion]
In file included from /usr/include/openssl/ssl.h:48:0,
 from ./sendmail.h:125,
 from tls.c:11:
/usr/include/openssl/bio.h:538:6: note: expected 'const BIO_METHOD * {aka const 
struct bio_method_st *}' but argument is of type 'int'
 BIO *BIO_new(const BIO_METHOD *type);
  ^
tls.c:1006:6: warning: 'RSA_generate_key' is deprecated 
[-Wdeprecated-declarations]
  (rsa_tmp = RSA_generate_key(RSA_KEYLENGTH, RSA_F4, NULL,
  ^
In file included from /usr/include/openssl/rsa.h:13:0,
 from /usr/include/openssl/x509.h:31,
 from /usr/include/openssl/ssl.h:50,
 from ./sendmail.h:125,
 from tls.c:11:
/usr/include/openssl/rsa.h:193:1: note: declared here
 DEPRECATEDIN_0_9_8(RSA *RSA_generate_key(int bits, unsigned long e, void
 ^
tls.c:1213:4: warning: 'DSA_generate_parameters' is deprecated 
[-Wdeprecated-declarations]
dsa = DSA_generate_parameters(bits, NULL, 0, NULL,
^
In file included from /usr/include/openssl/dh.h:13:0,
 from /usr/include/openssl/dsa.h:31,
 from /usr/include/openssl/x509.h:32,
 from /usr/include/openssl/ssl.h:50,
 from ./sendmail.h:125,
 from tls.c:11:
/usr/include/openssl/dsa.h:121:1: note: declared here
 DEPRECATEDIN_0_9_8(DSA *DSA_generate_parameters(int bits,
 ^
tls.c:1298:5: warning: implicit declaration of function 
'SSL_CTX_set_tmp_rsa_callback' [-Wimplicit-function-declaration]
 SSL_CTX_set_tmp_rsa_callback(*ctx, tmp_rsa_key);
 ^
tls.c: In function 'tmp_rsa_key':
tls.c:1747:2: warning: 'RSA_generate_key' is deprecated 
[-Wdeprecated-declarations]
  rsa_tmp = RSA_generate_key(RSA_KEYLENGTH, RSA_F4, NULL, NULL);
  ^
In file included from /usr/include/openssl/rsa.h:13:0,
 from /usr/include/openssl/x509.h:31,
 from /usr/include/openssl/ssl.h:50,
 from ./sendmail.h:125,
 from tls.c:11:
/usr/include/openssl/rsa.h:193:1: note: declared here
 DEPRECATEDIN_0_9_8(RSA *RSA_generate_key(int bits, unsigned long e, void
 ^
tls.c: In function 'x509_verify_cb':
tls.c:1974:10: error: dereferencing pointer to incomplete type 'X509_STORE_CTX 
{aka struct x509_store_ctx_st}'
   if (ctx->error == X509_V_ERR_UNABLE_TO_GET_CRL)
  ^
: recipe for target 'tls.o' failed


The file in question is sendmail/tls.c


Since I'm used to neither openssl nor the sendmail source code (and I 
have no use for sendmail at all, now that it passes the piuparts 
tests), I'm not going to write a patch for supporting openssl 1.1.0 
along 1.0.2.
I

Bug#829027: libstroke: missing/obsolete coypright information

[Jakub Wilk]

* Vincent Lefevre , 2016-06-30, 14:34:

The Debian policy manual says:

"In addition, the copyright file must say where the upstream sources 
(if any) were obtained, and should name the original authors."


This clause is made up of two requirements:

1. "the copyright file must say where the upstream sources ... were 
obtained"


2. "the copyright file ... should name the original authors"

libstroke does not violate the first requirement: the copyright file 
does say where the upstream sources /were/ obtained, even though they 
can no longer be obtained there.


According to archive.org, http://www.etla.net/ stopped mentioning 
libstroke somewhere between February and March 1999. The current 
upstream release was first uploaded in 2002, when the link was already 
invalid.


I thought that it would still be needed as long as the package is in 
Debian (so that users could check too) so that the location should 
implicitly still be valid.


No, there's no such requirement.

--
Jakub Wilk

sendmail_8.14.4-8+deb8u1_amd64.changes ACCEPTED into proposed-updates->stable-new

[Debian FTP Masters]

Mapping jessie to stable.
Mapping stable to proposed-updates.

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 30 Jun 2016 19:44:19 +0200
Source: sendmail
Binary: sendmail-bin rmail sensible-mda libmilter1.0.1 libmilter1.0.1-dbg 
libmilter-dev sendmail-doc sendmail sendmail-base sendmail-cf
Architecture: source all
Version: 8.14.4-8+deb8u1
Distribution: jessie
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Description:
 libmilter-dev - Sendmail Mail Filter API (Milter) (development files)
 libmilter1.0.1 - Sendmail Mail Filter API (Milter)
 libmilter1.0.1-dbg - Sendmail Mail Filter API (Milter) (debug symbols)
 rmail  - MTA->UUCP remote mail handler
 sendmail   - powerful, efficient, and scalable Mail Transport Agent (metapacka
 sendmail-base - powerful, efficient, and scalable Mail Transport Agent (arch 
inde
 sendmail-bin - powerful, efficient, and scalable Mail Transport Agent
 sendmail-cf - powerful, efficient, and scalable Mail Transport Agent (config ma
 sendmail-doc - powerful, efficient, and scalable Mail Transport Agent 
(documenta
 sensible-mda - Mail Delivery Agent wrapper
Closes: 826120
Changes:
 sendmail (8.14.4-8+deb8u1) jessie; urgency=medium
 .
   * QA upload.
   * Cherry-pick some patches from RHEL 6: RHBA-2015:1299-3
   * sendmail-8.14.4-client-port.patch: sendmail {client_port} not set
 correctly on little endian machines (8.15.1).
   * sendmail-8.14.4-ldap-fix.patch: do not abort with an assertion if the
 connection to an LDAP server is lost (8.14.5).  (Closes: #826120)
Checksums-Sha1:
 20a8c8ed56976a1d0cdcba720dbcb0c556d6b9e1 2633 sendmail_8.14.4-8+deb8u1.dsc
 57f98bd3bed73bc0a4ae11bfbca5c6c3edaf16f1 395708 
sendmail_8.14.4-8+deb8u1.debian.tar.xz
 885eadecd8598b930bf08932263958b9f8beaaea 860072 
sendmail-doc_8.14.4-8+deb8u1_all.deb
 d3925201da60c5db3e688c5e555a38a882e88076 217032 
sendmail_8.14.4-8+deb8u1_all.deb
 9c5d4c996e8dadf5dcf68b0594d2d37a37a14820 338772 
sendmail-base_8.14.4-8+deb8u1_all.deb
 e018e6c75ecd2b5e73ed0cc13c87553287a9f93a 286120 
sendmail-cf_8.14.4-8+deb8u1_all.deb
Checksums-Sha256:
 7905979c082e448532fc97117a9ebefd0786ceacc5dd7ec9e9b217d31b6aa671 2633 
sendmail_8.14.4-8+deb8u1.dsc
 f96cc4ee67802ac029dd7a271777945d6ab5c1b53f97b1f36e23437f8cf655b9 395708 
sendmail_8.14.4-8+deb8u1.debian.tar.xz
 567a10f5f0c121f2bb0ba48dc118d9301c360322c156e5118bc6070b691760d7 860072 
sendmail-doc_8.14.4-8+deb8u1_all.deb
 8e23689d5d7b2174f1a66c1d26e85736e9f04dc2aca4f911426add6620224f74 217032 
sendmail_8.14.4-8+deb8u1_all.deb
 650fae36c16f0839776a8d40a8384d4b4647f533daf73cc68652e54679a99177 338772 
sendmail-base_8.14.4-8+deb8u1_all.deb
 815bc41241b112a2ee55ca9b079400227c3070aac16850bfb9ba54b1f0b63a83 286120 
sendmail-cf_8.14.4-8+deb8u1_all.deb
Files:
 61b30f5c4773fc1851f123737dfde09a 2633 mail extra sendmail_8.14.4-8+deb8u1.dsc
 97c54410f5c7e5e67c1bdfc75efe1616 395708 mail extra 
sendmail_8.14.4-8+deb8u1.debian.tar.xz
 768e3c15d519693553ae75b6e1eee835 860072 doc extra 
sendmail-doc_8.14.4-8+deb8u1_all.deb
 8e8a0602d914980c6ba78ea7e4f6fbaa 217032 mail extra 
sendmail_8.14.4-8+deb8u1_all.deb
 62d3bcaf16d0d45c173572772293c146 338772 mail extra 
sendmail-base_8.14.4-8+deb8u1_all.deb
 ad5243d207aa36cc6ee9504cf11b69d3 286120 mail extra 
sendmail-cf_8.14.4-8+deb8u1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXdWCCAAoJEF+zP5NZ6e0I3ogP/iv/Va0neuYUPnqn1XsOgES1
JglHeBNSA7ZV7eAlr+838Dg+BuD8BDp9olgdP2hmtku3f4Rb1uW9EBCz+4ZuN4+s
AJOgxmMhMlgj3P56biIrqRnRUefWfHW/gUzT4XBo8z7Pu3oCjIX+zcDeqhF48DHb
vPXTkFYhnmduGA1R78ZvBSKRFyXyjnAjJxGBymPdDGB8vSph3F4Z0g85s+TQMLH4
117AIpMaoMg9vkLnrroLkZuIAeU/uYG3p2+zJ8IHXz4YD+77Pfb4EZl9FKxWVnc1
xyhQX02hQdP60hJXl7mwanm4JsxhF/MnZjGArHuWqgMrgdhG6Kn3LyVbvgvB4etb
1O4uw3D+utaDf80ohCe9CunOKCQfB82MyxdWxQqObjdKMZieZsv3UeO+Gt39Fy2V
OjctGSa4DPLrgdZMojQhiHa7Wkf5CbBZbGLiDlQL8j2Ol+lq0d49NYmk230+OgST
6f3wJLogComMZWTbtBJdTjtSkvIU8XGx2ejEoBDBZcXlnVhJZLh9sD55XVaIyvTn
RT+MZ8mq15k/nnf8uDPuKB2A+c5FL11eJx4EKECl67IpOTKbyydIyySepKImKbnF
81/VEr0HF6ciHnJcsFKNZockQlupBUekWUVzjNwaz0a3O0rLzTuj72Zadgd+UmT0
Af0DGbVrdKaYD7d3cAqS
=WuRw
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processed: tagging 811591, tagging 811642, tagging 811659, tagging 811733, tagging 811863, tagging 811868 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 811591 + sid stretch
Bug #811591 [ifhp] FTBFS with GCC 6: statement indented as if it were guarded by
Added tag(s) sid and stretch.
> tags 811642 + sid stretch
Bug #811642 [fracplanet] FTBFS with GCC 6: cannot convert x to y
Added tag(s) stretch and sid.
> tags 811659 + sid stretch
Bug #811659 [wvstreams] FTBFS with GCC 6: cannot convert x to y
Added tag(s) stretch and sid.
> tags 811733 + sid stretch
Bug #811733 [cdrdao] cdrdao: FTBFS with GCC 6: narrowing conversion
Added tag(s) sid and stretch.
> tags 811863 + sid stretch
Bug #811863 [tagcoll2] tagcoll2: FTBFS with GCC 6: no matching function for 
call to
Added tag(s) sid and stretch.
> tags 811868 + sid stretch
Bug #811868 [linuxdcpp] linuxdcpp: FTBFS with GCC 6: no matching function for 
call to
Added tag(s) stretch and sid.
> tags 811894 + sid stretch
Bug #811894 [tvtime] tvtime: FTBFS with GCC 6: inconsistent user-defined 
literal suffixes
Added tag(s) sid and stretch.
> tags 811899 + sid stretch
Bug #811899 [gnuift] gnuift: FTBFS with GCC 6: declared in this scope
Added tag(s) stretch and sid.
> tags 812053 + sid stretch
Bug #812053 [galib] galib: FTBFS with GCC 6
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
811591: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811591
811642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811642
811659: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811659
811733: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811733
811863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811863
811868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811868
811894: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811894
811899: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811899
812053: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812053
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

adplay_1.7-2_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 30 Jun 2016 14:55:20 +0200
Source: adplay
Binary: adplay
Architecture: source
Version: 1.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Matthias Klose 
Description:
 adplay - console-based OPL2 audio player
Closes: 811739
Changes:
 adplay (1.7-2) unstable; urgency=medium
 .
   * QA upload.
   * Fix build failure using GCC 6. Closes: #811739.
Checksums-Sha1:
 c0457dbb7a0db65ef1ef2547b3cd1d086bd503cd 1770 adplay_1.7-2.dsc
 b7121425193ea55eab343dd62d9d8638707ab107 6296 adplay_1.7-2.debian.tar.xz
Checksums-Sha256:
 1a1d7036cbe599d6bf50ba5622165730eb1fe4f7c1552145b07868d2b0b4ff18 1770 
adplay_1.7-2.dsc
 4c234fb94101233f368ed30fe08317c1c4b20f6e17a1ea0f5959f7ddea525075 6296 
adplay_1.7-2.debian.tar.xz
Files:
 d70a06168ee08c3573adfd60387ed051 1770 sound optional adplay_1.7-2.dsc
 83da053f92206bbd2f2fd527abaee066 6296 sound optional adplay_1.7-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXdRplAAoJEL1+qmB3j6b1XPEQAMjkPLyV24wSfmhiYWYY3rjX
SwhzHv9mJY4Apwh9Jd+pwdunQ+Q8QJZt1cuI12VQ7ysuMwy9zi4kjlT8HTYbJ50t
oQo9P9xQ8o0/WM272b65pkTZaqOBNcYm2N+h9intLN7F6MV6xrbF9t/0wlt4HtIQ
hN/ZlpZ+GdWgSEyOXDkHxfxEArQJDXHbjVH8I2mAYZVyLxUy/FCbgi7aaRWzI24/
MsGDV2RTsyfo8zIbjcvZ2dTzvvZs/DemyMXD9qO8qpRsXkjdb55SVUQqWkfMg2YH
tNq4lYE5uHOAR1wfCnsKG5bX3EJT8IkZAkCe8riQGCbccTsx48yOkGU2gZlazWhk
bF5yBVIFdxRWiKMfdRn5Do0PrRnEyeDQu44q2zy8MYtakHKxfKe5w/JvVyf+7scc
jwXoklJR6O8b/bRDIQBlhXvd7/4wbGrLj8D8L4CGK/4G3cppLgTTeEfyl7wWEwaR
FW+B3TSymjNkmPJGsarvFg44PvfxakSWXt7Okg6EgDZPtsyEIz9G2iS8gHDm3f9+
zIYraVVUS7vRBGVvMYrr2jnztD9PgUO9s7usA7Rym2+RDJkTL6/fT3SuMQYcuGIU
Adgg22RBVvpfbX8Vbp4fZIgP0Rjs79mJ+oc98RlpKdU14fEPPS61zqvo/Sn1yGgB
CKxmt3RzpifGSapwoBUA
=Ea5o
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of adplay_1.7-2_source.changes

[Debian FTP Masters]

adplay_1.7-2_source.changes uploaded successfully to localhost
along with the files:
  adplay_1.7-2.dsc
  adplay_1.7-2.debian.tar.xz

Greetings,

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

Bug#811667: Fix in upstream

[Matthias Klose]

could you pick the relevant SVN changes?

Bug#811739: marked as done (adplay: FTBFS with GCC 6: narrowing conversion)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jun 2016 13:18:50 +
with message-id 
and subject line Bug#811739: fixed in adplay 1.7-2
has caused the Debian Bug report #811739,
regarding adplay: FTBFS with GCC 6: narrowing conversion
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.)


-- 
811739: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: adplay
Version: 1.7-1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-narrowing

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> g++ -DHAVE_CONFIG_H -I.  -I/usr/include/libbinio  -I/usr/include/SDL 
> -D_GNU_SOURCE=1 -D_REENTRANT -DADPLUG_DATA_DIR=\"/usr/com/adplug\" 
> -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -fPIE -fstack-protector-strong 
> -Wformat -Werror=format-security -c -o alsa.o alsa.cc
> esound.cc: In member function 'virtual void EsoundPlayer::output(const void*, 
> long unsigned int)':
> esound.cc:46:27: warning: ignoring return value of 'ssize_t write(int, const 
> void*, size_t)', declared with attribute warn_unused_result [-Wunused-result]
>write(socket, buf, size);
>^
> 
> oss.cc: In member function 'virtual void OSSPlayer::output(const void*, long 
> unsigned int)':
> oss.cc:59:29: warning: ignoring return value of 'ssize_t write(int, const 
> void*, size_t)', declared with attribute warn_unused_result [-Wunused-result]
>write(audio_fd, buf, size);
>  ^
> 
> adplay.cc:98:1: error: narrowing conversion of '-1' from 'int' to 'unsigned 
> int' inside { } [-Wnarrowing]
>  };
>  ^
> 
> Makefile:497: recipe for target 'adplay.o' failed
> make[3]: *** [adplay.o] Error 1
> make[3]: *** Waiting for unfinished jobs

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: adplay
Source-Version: 1.7-2

We believe that the bug you reported is fixed in the latest version of
adplay, 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 811...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated adplay 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: SHA256

Format: 1.8
Date: Thu, 30 Jun 2016 14:55:20 +0200
Source: adplay
Binary: adplay
Architecture: source
Version: 1.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Matthias Klose 
Description:
 adplay - console-based OPL2 audio player
Closes: 811739
Changes:
 adplay (1.7-2) unstable; urgency=medium
 .
   * QA upload.
   * Fix build failure using GCC 6. Closes: #811739.
Checksums-Sha1:
 c0457dbb7a0db65ef1ef2547b3cd1d086bd503cd 1770 adplay_1.7-2.dsc
 b7121425193ea55eab343dd62d9d8638707ab107 6296 adplay_1.7-2.debian.tar.xz
Checksums-Sha256:
 1a1d7036cbe599d6bf50ba5622165730eb1fe4f7c1552145b07868d2b0b4ff18 1770 
adplay_1.7-2.dsc
 4c234fb94101233f368ed30fe08317c1c4b20f6e17a1ea0f5959f7ddea525075 6296 
adplay_1.7-2.debian.tar.xz
Files:
 d70a06168ee08c3573adfd60387ed051 1770 sound optional adplay_1.7-2.dsc
 83da053f92206bbd2f2fd527abaee066 6296 sound optional adplay_1.7-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXdRplAAoJEL1+qmB3j6b1XPEQAMjkPLyV24wSfmhiYWYY3rjX
SwhzHv9mJY4Apwh9Jd+pwdunQ+Q8QJZt1cuI12VQ7ysuMwy9zi4kjlT8HTYbJ50t
oQo9P9xQ8o0/WM272b65pkTZaqOBNcYm2N+h9intLN7F6MV6xrbF9t/0wlt4HtIQ
hN/ZlpZ+GdWgSEyOXDkHxfxEArQJDXHbjVH8I2mAYZVyLxUy/FCbgi7aaRWzI24/
MsGDV2RTsyfo8zIbjcvZ2dTzvvZs/DemyMXD9qO8qpRsXkjdb55SVUQqWkfMg2YH
tNq4lYE5uHOAR1wfCnsKG5bX3EJT8IkZAkCe8riQGCbccTsx48yOkGU2gZlazWhk
bF5yBVIFdxRWiKMfdRn5Do0PrRnEyeDQu44q2zy8MYtakHKxfKe5w/JvVyf+7scc
jwXoklJR6O8b/bRDIQBlhXvd7/4wbGrLj8D8L4CGK/4G3

Bug#829027: libstroke: missing/obsolete coypright information

[Vincent Lefevre]

On 2016-06-30 03:22:09 +, Sean Whitton wrote:
> On Wed, Jun 29, 2016 at 10:44:36PM +0200, Vincent Lefevre wrote:
> > The Debian policy manual says:
> > 
> > "In addition, the copyright file must say where the upstream sources
> > (if any) were obtained, and should name the original authors."
> 
> This clause is made up of two requirements:
> 
> 1. "the copyright file must say where the upstream sources ... were obtained"
> 
> 2. "the copyright file ... should name the original authors"
> 
> libstroke does not violate the first requirement: the copyright file
> does say where the upstream sources /were/ obtained, even though they
> can no longer be obtained there.  (I believe that the requirement is for
> FTP-master verification of the copyright status that the copyright file
> claims; since that verification has already taken place, it is not a
> problem that the source is no longer accessible there.)

I thought that it would still be needed as long as the package is
in Debian (so that users could check too) so that the location
should implicitly still be valid.

> I'm not sure whether libstroke violates the second requirement.  The
> original author is, arguably, the company called "ETLA", and one could
> argue that the URL included in the copyright file names them.  You are
> correct that it could be much clearer, and the next upload of libstroke
> ought to correct this.

This is not exactly ETLA. The upstream COPYRIGHT file says:
"Mark F. Willey, ETLA Technical".

> Someone has contributed a patch fixing the autoconf problem.  You are
> encouraged to prepare a QA upload applying it (and also fixing this
> bug): .

I might have some time to look at this next week (otherwise after
July 16).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#800005: fbset gets 'ioctl FBIOPUT_VSCREENINFO: Invalid argument'

[Rick Thomas]

Do I understand correctly that I should put “drm.debug=0xe” as a kernel 
argument at boot time?  Then boot, try running my “fbset” test and send you the 
entire output of dmesg including all boot messages.  Is this correct?

Further, I guess you would prefer to have this on the amd64 machine in question 
rather than the original powerpc machine?

What other info should I send?  If I use the amd64 machine, I guess you’d like 
some hardware configuration info as well?  Please be specific: a verbatim list 
of shell commands you’d like me to run would be most helpful!

Thanks!
Rick

On Jun 29, 2016, at 11:20 PM, Mathieu Malaterre  wrote:

> On Sun, Jun 26, 2016 at 2:59 AM, Rick Thomas  wrote:
>> For what it’s worth, I get the same behavior on amd64 running stretch.  It’s 
>> not just on powerpc.
> 
> Great ! Could you please turn more debugging info. eg: drm.debug=0xe
> and try again.
> 
> ref:
> https://01.org/linuxgraphics/documentation/how-report-bugs
> 
> thanks