On Thu, Aug 18, 2016 at 1:24 AM, Johannes Schauer wrote:
> does anybody plan to use sbuild in Stretch with Debian Squeeze or older
> chroots?
ISTR folks on IRC mentioning they are still supporting clients on
lenny and older.
--
bye,
pabs
https://wiki.debian.org/PaulWise
On Wed, Aug 17, 2016 at 10:05:06PM +0200, ni...@thykier.net wrote:
> * If we were to enable -fPIE/-pie by default in GCC-6, should that change
>also apply to this port? [0]
If -fPIE is the default will -fPIC override it?
It will also default to tell the linker to use -pie, but then
don't do
Martin Michlmayr:
> * ni...@thykier.net [2016-08-17 22:05]:
>> 2020), please respond with a signed email containing the following
>> before Friday, the 9th of September:
>
> Can you please specify where to respond to? I don't think dozens of
> emails to -ports and -devel make any sense.
>
Ah,
On Wed, Aug 17, 2016 at 07:24:51PM +0200, Johannes Schauer wrote:
> does anybody plan to use sbuild in Stretch with Debian Squeeze or older
> chroots?
>
> I would like to remove some code from sbuild which is only useful for chroots
> with very old apt inside (specifically apt without support for
* ni...@thykier.net [2016-08-17 22:05]:
> 2020), please respond with a signed email containing the following
> before Friday, the 9th of September:
Can you please specify where to respond to? I don't think dozens of
emails to -ports and -devel make any sense.
Maybe debian-release with CC debian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Like last release, we are doing a roll call for porters of all release
architectures. If you are an active porter behind one of the [release
architectures] for the entire lifetime of Debian Stretch (est. end of
2020), please respond with a sign
Daniel Pocock writes:
> I was only talking about control emails (e.g. the -done address and
> control@). The requirements for opening bugs or submitting comments
> (without pseudo-headers) could remain as they are.
I don't believe the spammer intended to close the bug. The bug
had already been
On Wed, 17 Aug 2016, Daniel Pocock wrote:
> I received a notification that a bug was closed.
>
> The email that closed the bug was a spam email sent to the address
> (bug-number)-d...@bugs.debian.org
>
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737921
>
> Maybe time to start requir
Hi,
does anybody plan to use sbuild in Stretch with Debian Squeeze or older
chroots?
I would like to remove some code from sbuild which is only useful for chroots
with very old apt inside (specifically apt without support for [trusted=yes] in
the sources.list). Maintaining this piece of code take
On 17/08/16 18:34, Stéphane Blondon wrote:
> Hello,
>
> Le 17/08/2016 à 18:14, Daniel Pocock a écrit :
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737921
>>
>> Maybe time to start requiring PGP signatures on control emails to
>> the BTS?
>
> Requiring signature will increase the level
On 17/08/16 18:29, gustavo panizzo wrote:
> On Wed, Aug 17, 2016 at 06:14:38PM +0200, Daniel Pocock wrote:
>>
>>
>> I received a notification that a bug was closed.
>>
>> The email that closed the bug was a spam email sent to the
>> address (bug-number)-d...@bugs.debian.org
>>
>>
>> https:/
Hello,
Le 17/08/2016 à 18:14, Daniel Pocock a écrit :
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737921
>
> Maybe time to start requiring PGP signatures on control emails to the BTS?
Requiring signature will increase the level to send bugs to the BTS for
external people. And spammers co
On Wed, Aug 17, 2016 at 06:14:38PM +0200, Daniel Pocock wrote:
>
>
> I received a notification that a bug was closed.
>
> The email that closed the bug was a spam email sent to the address
> (bug-number)-d...@bugs.debian.org
>
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737921
It w
I received a notification that a bug was closed.
The email that closed the bug was a spam email sent to the address
(bug-number)-d...@bugs.debian.org
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737921
Maybe time to start requiring PGP signatures on control emails to the BTS?
Package: wnpp
Severity: wishlist
Owner: Debian Med team
* Package name: hisat2
Version : 2.0.4
Upstream Author : HISAT2 team
* URL : https://ccb.jhu.edu/software/hisat2/index.shtml
* License : GPL-3+
Programming Lang: Perl, Python, C++
Description : gr
Package: wnpp
Severity: wishlist
Owner: Debian Med team
* Package name: python3-typed-ast
Version : 0.5.5
Upstream Author : David Fisher
* URL : https://pypi.python.org/pypi/typed-ast
* License : Python, Apache-2.0
Programming Lang: Python, C
Description
Andrey Rahmatullin writes:
> On Tue, Aug 16, 2016 at 02:30:58PM +0200, Ole Streicher wrote:
>> I always use this as one argument when it comes to "Why should be care
>> about Debian? Our users use something else", that packaging includes a
>> careful review and documentation of the copyright.
> Us
Quoting Andreas Tille (2016-08-17 10:55:01)
> On Tue, Aug 16, 2016 at 10:13:30PM +0500, Andrey Rahmatullin wrote:
> > On Tue, Aug 16, 2016 at 02:30:58PM +0200, Ole Streicher wrote:
> > > I always use this as one argument when it comes to "Why should be care
> > > about Debian? Our users use somethi
On Tue, Aug 16, 2016 at 10:13:30PM +0500, Andrey Rahmatullin wrote:
> On Tue, Aug 16, 2016 at 02:30:58PM +0200, Ole Streicher wrote:
> > I always use this as one argument when it comes to "Why should be care
> > about Debian? Our users use something else", that packaging includes a
> > careful revi
On Mon, 1 Aug 2016 12:40:37 +0200, Adam Borowski wrote:
> On Mon, Aug 01, 2016 at 12:31:14PM +0200, Marco d'Itri wrote:
> > We should also think hard about switching to a new default since
> > currently many other major distributions are moving to NetworkManager
> > and/or systemd-networkd (which
20 matches
Mail list logo
