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.
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/2001121
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.n
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."
> > >
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) st
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
uploade
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
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 y
* 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 upst
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 sendmai
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) stre
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
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)
could you pick the relevant SVN changes?
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
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."
>
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 que
17 matches
Mail list logo
