Bug#836157: jessie-pu: gnome-sudoku/1:3.14.1-1+deb8u1

[Jeremy Bicha]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: jessie
Severity: normal

gnome-sudoku had a bug where it would generate the same sequence of
puzzles every time the app was run. I'm applying the patch included
upstream in 3.18.3.

Thanks,
Jeremy Bicha
=== modified file 'debian/changelog'
--- debian/changelog2016-08-31 01:41:59 +
+++ debian/changelog2016-08-31 01:44:04 +
@@ -1,3 +1,12 @@
+gnome-sudoku (1:3.14.1-1+deb8u1) stable; urgency=medium
+
+  * Team upload
+  * debian/patches/generate_new_puzzles.patch:
+- Don't generate the same puzzle sequence every time.
+  Closes: #828106
+ 
+ -- Jeremy Bicha   Tue, 30 Aug 2016 15:23:30 -0400
+
 gnome-sudoku (1:3.14.1-1) unstable; urgency=medium
 
   [ Jackson Doak ]

=== added directory 'debian/patches'
=== added file 'debian/patches/generate_new_puzzles.patch'
--- debian/patches/generate_new_puzzles.patch   1970-01-01 00:00:00 +
+++ debian/patches/generate_new_puzzles.patch   2016-08-31 01:42:05 +
@@ -0,0 +1,38 @@
+From 95b99df63e1704cca55b13ba27f140bf4961fabb Mon Sep 17 00:00:00 2001
+From: Michael Catanzaro 
+Date: Mon, 11 Jul 2016 23:15:13 -0500
+Subject: qqwing-wrapper: Seed RNG
+
+This is ugly. On the master branch, we will use std::once_flag, but for
+gnome-3-20 let's avoid adding a dependency on C++ 11.
+
+https://bugzilla.gnome.org/show_bug.cgi?id=768345
+
+Bug-Debian: https://bugs.debian.org/828106
+---
+ lib/qqwing-wrapper.cpp | 11 +++
+ 1 file changed, 11 insertions(+)
+
+diff --git a/lib/qqwing-wrapper.cpp b/lib/qqwing-wrapper.cpp
+index 99c4562..dfd0ac4 100644
+--- a/lib/qqwing-wrapper.cpp
 b/lib/qqwing-wrapper.cpp
+@@ -41,6 +41,17 @@ int* qqwing_generate_puzzle(int difficulty)
+ const int BOARD_SIZE = 81;
+ SudokuBoard board;
+ 
++// Seed RNG exactly once.
++static GMutex mutex;
++static bool seeded = false;
++g_mutex_lock();
++if (!seeded)
++{
++srand(time(NULL));
++seeded = true;
++}
++g_mutex_unlock();
++
+ board.setRecordHistory(true);
+ board.setLogHistory(false);
+ board.setPrintStyle(SudokuBoard::ONE_LINE);
+

=== added file 'debian/patches/series'
--- debian/patches/series   1970-01-01 00:00:00 +
+++ debian/patches/series   2016-08-31 01:42:05 +
@@ -0,0 +1,1 @@
+generate_new_puzzles.patch

Bug#832336: jessie-pu: package systemd/215-17+deb8u5

[Michael Biebl]

Am 18.08.2016 um 23:41 schrieb Michael Biebl:
> Am 04.08.2016 um 22:13 schrieb Michael Biebl:
>> Am 03.08.2016 um 22:41 schrieb Julien Cristau:
>>> On Wed, Aug  3, 2016 at 22:32:16 +0200, Michael Biebl wrote:
>>>
 Am 29.07.2016 um 23:00 schrieb Michael Biebl:
> Am 29.07.2016 um 14:00 schrieb Julien Cristau:
>> This looks fine in general, I'm just wondering if the effect of bumping
>> the util-linux dependency on upgrades from wheezy was considered/tested?
>
> It was not specifically tested since I didn't expect any breakage
> because of it. But I did it now for a basic wheezy system the upgrade to
> jessie (with the updated systemd packages) worked fine. The tightened
> dep on u-l seems to not cause any issues.
>
> I've attached the typescript from the wheezy → jessie dist-upgrade.

 Is that sufficient or do you still have concerns?

>>> I'm definitely concerned about changing dependencies in the base system
>>> in stable, yes.  Is the parallel fsck bug that bad?
>>
>> I would really like to include that fsck fix. Parallel fsck on rotating
>> disks is bad. It degrades the performance and we had reports from
>> concerned users, that their disks made very strange noises when the
>> heads where constantly repositioned.
>> This doesn't affect SSDs, but I guess HDD are still very common on a
>> typical server.
> 
> With the 8.6 release being close and no further response, I assume you
> still object to this change. I would still like to see the other fixes
> land in 8.6, so if you are ok with the other changes, can I proceed with
> the upload if I exclude the 'fsck -l' fix?


Hi, would be great to have a final decisions on this issue so I can
proceed with the upload. I'd hate to see the accumulated fixes for
systemd not to land in 8.6.

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#835397: transition: superlu soname 4 -> 5

[Emilio Pozuelo Monfort]

On 27/08/16 05:53, Drew Parsons wrote:
> binNMU requests filed to complete the petsc/slepc transtion:
> #835556: nmu: aster_11.5.0+dfsg2-4
> #835557: nmu: dolfin_2016.1.0-2

Scheduled.

Emilio

Bug#835557: marked as done (nmu: dolfin_2016.1.0-2)

[Debian Bug Tracking System]

Your message dated Wed, 31 Aug 2016 00:44:44 +0200
with message-id 
and subject line Re: Bug#835557: nmu: dolfin_2016.1.0-2
has caused the Debian Bug report #835557,
regarding nmu: dolfin_2016.1.0-2
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.)


-- 
835557: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835557
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

nmu dolfin_2016.1.0-2 . ANY . unstable . -m "binNMU for petsc 3.7 transition"

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On 27/08/16 05:27, Drew Parsons wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> nmu dolfin_2016.1.0-2 . ANY . unstable . -m "binNMU for petsc 3.7 transition"

Scheduled.

Emilio--- End Message ---

Bug#835556: marked as done (nmu: aster_11.5.0+dfsg2-4)

[Debian Bug Tracking System]

Your message dated Wed, 31 Aug 2016 00:44:25 +0200
with message-id <7cc1a326-fdae-4852-01b3-31a645449...@debian.org>
and subject line Re: Bug#835556: nmu: aster_11.5.0+dfsg2-4
has caused the Debian Bug report #835556,
regarding nmu: aster_11.5.0+dfsg2-4
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.)


-- 
835556: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

nmu aster_11.5.0+dfsg2-4 . ANY . unstable . -m "binNMU for petsc 3.7 transition"

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On 27/08/16 05:21, Drew Parsons wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> nmu aster_11.5.0+dfsg2-4 . ANY . unstable . -m "binNMU for petsc 3.7 
> transition"

Scheduled.

Emilio--- End Message ---

Bug#835170: transition: protobuf

[Emilio Pozuelo Monfort]

On 28/08/16 18:13, Sebastiaan Couwenberg wrote:
> On 08/25/16 19:17, Sebastiaan Couwenberg wrote:
>> On 08/25/16 17:33, Sebastiaan Couwenberg wrote:
>>> Several packages unfortunately fail to build, some due to unrelated
>>> issues to the new protobuf packages. Bugs still need to be filed for
>>> those that weren't sid-ony due to RC bugs already.
>>
>> The bugreports have been filed, and ones specific to protobuf 3.0.0 have
>> been usertagged for easy access:
>>
>> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=protobuf-3.0.0;users=pkg-protobuf-de...@lists.alioth.debian.org
>>
> 
> Release Team, can you schedule binNMUs for the packages that rebuilt OK?

Scheduled.

Emilio

Bug#834545: transition: re2

[Stefano Rivera]

Hi Emilio (2016.08.31_00:35:21_+0200)
> > Would you mind if I held back for the next release, due on the 1st?
> 
> 1st of September?
> 
> That'd be fine.

Yep. Upstream does monthly snapshots, rather than releases. And seem to
be moving rather fast atm.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#834545: transition: re2

[Emilio Pozuelo Monfort]

On 30/08/16 08:04, Stefano Rivera wrote:
> Hi Emilio (2016.08.29_09:58:46_+0200)
>> Go ahead.
> 
> Would you mind if I held back for the next release, due on the 1st?

1st of September?

That'd be fine.

Emilio

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: adblock-plus_2.7.3+dfsg-1~deb8u1_amd64.changes
  ACCEPT
Processing changes file: bogofilter_1.2.4+dfsg1-3+deb8u1_amd64.changes
  ACCEPT
Processing changes file: bogofilter_1.2.4+dfsg1-3+deb8u1_arm64.changes
  ACCEPT
Processing changes file: bogofilter_1.2.4+dfsg1-3+deb8u1_armel.changes
  ACCEPT
Processing changes file: bogofilter_1.2.4+dfsg1-3+deb8u1_armhf.changes
  ACCEPT
Processing changes file: bogofilter_1.2.4+dfsg1-3+deb8u1_i386.changes
  ACCEPT
Processing changes file: bogofilter_1.2.4+dfsg1-3+deb8u1_mips.changes
  ACCEPT
Processing changes file: bogofilter_1.2.4+dfsg1-3+deb8u1_mipsel.changes
  ACCEPT
Processing changes file: bogofilter_1.2.4+dfsg1-3+deb8u1_powerpc.changes
  ACCEPT
Processing changes file: bogofilter_1.2.4+dfsg1-3+deb8u1_ppc64el.changes
  ACCEPT
Processing changes file: bogofilter_1.2.4+dfsg1-3+deb8u1_s390x.changes
  ACCEPT
Processing changes file: firegestures_1.10.9-1~deb8u1_amd64.changes
  ACCEPT
Processing changes file: greasemonkey_3.8-1~deb8u1_amd64.changes
  ACCEPT
Processing changes file: intel-microcode_3.20160714.1~deb8u1_multi.changes
  ACCEPT
Processing changes file: mozilla-noscript_2.9.0.11-1~deb8u1_amd64.changes
  ACCEPT
Processing changes file: ovirt-guest-agent_1.0.10.2.dfsg-2+deb8u1_amd64.changes
  ACCEPT
Processing changes file: sqlite3_3.8.7.1-1+deb8u2_amd64.changes
  ACCEPT
Processing changes file: tabmixplus_0.5.0.0-1~deb8u1_amd64.changes
  ACCEPT

Re: Porter roll call for Debian Stretch

[Lucas Nussbaum]

On 22/08/16 at 19:12 +0200, Bálint Réczey wrote:
> Hi Guillem,
> 
> 2016-08-21 14:02 GMT+02:00 Guillem Jover <guil...@debian.org>:
> > Hi!
> >
> > On Sun, 2016-08-21 at 10:24:42 +0200, Bálint Réczey wrote:
> >> I'm testing a set of patches [2] for gcc and dpkg which enable bindnow for 
> >> all
> >> arches and PIE for amd64, ppc64el and s390x in sync with Ubuntu.
> >>
> >> My assumption was that this set of architectures need the least amount of
> >> additional work since they are tested already in Ubuntu, but I would be 
> >> happy
> >> if more ports would opt in for PIE.
> >>
> >> I plan filing wishlist bugs against dpkg and gcc with the patches
> >> after I rebuilt a
> >> few packages with the defaults.
> >
> > TBH I think PIE should in fact be safer to enable globally than
> > bindnow, because the latter changes the run-time behavior and things
> > might break (perhaps even silently) when failing to load plugins
> > or similar.
> 
> Yes, in that sense enabling PIE is safer indeed. Regarding bindnow
> I don't expect too many surprises either, since other distributions
> already tested enabling bindnow and probably they found
> most issues.
> 
> >
> > From dpkg PoV enabling both, would at least require a full-archive
> > rebuild, for bindnow ideally also a full autopkgtest run (as the
> > updated dpkg FAQ states now, after Lucas Nussbaum approached me some
> > weeks ago mentioning he was willing to do such archive-wide rebuild).
> 
> The patches at [2] seem to work well and since you expressed that you would
> prefer changing both toolchain and dpkg, too, I would like to suggest running
> the rebuild with those patches.
> 
> I think Matthias would be OK with the patch since it is very small and brings
> Debian's gcc closer to Ubuntu's.
> 
> Lucas, could you please run the rebuild with the three patches?

Hi,

Results are available at
https://people.debian.org/~lucas/logs/2016/08/30/pie-bindnow-20160830/

I did a full rebuild with bindnow and PIE enabled, then rebuilt all
failed packages with a pristine unstable chroot.

You can take a look at
https://people.debian.org/~lucas/logs/2016/08/30/pie-bindnow-20160830/diff.txt
and grep for "OK Failed" (failed with PIE+bindnow, built fine in
unstable). (There are 1188 packages failing to build)

Logs for both builds are available in the respective subdirectories.

Lucas

Processed: Re: Bug#835444: jessie-pu: package ovirt-guest-agent/1.0.10.2.dfsg-2+deb8u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #835444 [release.debian.org] jessie-pu: package 
ovirt-guest-agent/1.0.10.2.dfsg-2+deb8u1
Added tag(s) pending.

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

Processed: Re: Bug#835443: jessie-pu: package sqlite3/3.8.7.1-1+deb8u2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #835443 [release.debian.org] jessie-pu: package sqlite3/3.8.7.1-1+deb8u2
Added tag(s) pending.

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

Bug#835444: jessie-pu: package ovirt-guest-agent/1.0.10.2.dfsg-2+deb8u1

[Adam D. Barratt]

Control: tags -1 + pending

On Sun, 2016-08-28 at 15:07 +0100, Adam D. Barratt wrote:
> Control; tags -1 + confirmed
> 
> On Thu, 2016-08-25 at 20:45 +0200, Laszlo Boszormenyi (GCS) wrote:
> > There are two stupid bugs in ovirt-guest-agent which affects Jessie.
> > Both fixed in Sid + Stretch.
> > 
> > First is that its daemon is not started with the initscript[1]. Reason
> > is: it checks for executable bit on the daemon, but it's installed
> > without that. chmod a+x added to d/rules.
> > 
> > Second is that the logging is not working if daemon is started with
> > systemd as its log directory is not owned by the ovirtagent user[2].
> > To be extra safe, the chown was added to postinst.
> 
> Please go ahead.

Uploaded and flagged for acceptance.

Regards,

Adam

Processed: Re: Bug#834479: xul-ext-* (Was: Bug#834480: jessie-pu: package mozilla-noscript/2.9.0.11-1~deb8u1)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #834482 [release.debian.org] jessie-pu: package 
adblock-plus/2.7.3+dfsg-1~deb8u1
Added tag(s) pending.

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

Processed: Re: Bug#834261: jessie-pu: package intel-microcode/3.20160714.1~deb8u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #834261 [release.debian.org] jessie-pu: package 
intel-microcode/3.20160714.1~deb8u1
Added tag(s) pending.

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

Processed: Re: Bug#834479: xul-ext-* (Was: Bug#834480: jessie-pu: package mozilla-noscript/2.9.0.11-1~deb8u1)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #834479 [release.debian.org] jessie-pu: package greasemonkey/3.8-1~deb8u1
Added tag(s) pending.

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

Bug#835443: jessie-pu: package sqlite3/3.8.7.1-1+deb8u2

[Adam D. Barratt]

Control: tags -1 + pending

On Sun, 2016-08-28 at 15:05 +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Thu, 2016-08-25 at 20:45 +0200, Laszlo Boszormenyi (GCS) wrote:
> > There's a vulnerability in SQLite3 [1] which was fixed in Sid and
> > Stretch, but not yet in Jessie. Security Team decided it's a minor
> > issue and doesn't warrant a DSA.
> > 
> > An other issue, a segfault is fixed as well on heavy 'SAVEPOINT'
> > usage[2][3], which affects Django.
> 
> Please go ahead.

Uploaded and flagged for acceptance.

Regards,

Adam

Processed: Re: Bug#834479: xul-ext-* (Was: Bug#834480: jessie-pu: package mozilla-noscript/2.9.0.11-1~deb8u1)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #834484 [release.debian.org] jessie-pu: package firegestures/1.10.9-1~deb8u1
Added tag(s) pending.

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

Bug#834261: jessie-pu: package intel-microcode/3.20160714.1~deb8u1

[Adam D. Barratt]

Control: tags -1 + pending

On Sun, 2016-08-28 at 11:49 -0300, Henrique de Moraes Holschuh wrote:
> On Sun, 28 Aug 2016, Adam D. Barratt wrote:
> > On Sat, 2016-08-13 at 18:27 -0300, Henrique de Moraes Holschuh wrote:
> > > I would like to update the intel-microcode packages in stable to address
> > > several critical errata in newer Intel processors, as well as to
> > > properly support the Linux kernel 4.4 and later.
> > > 
> > > The updated packages being proposed in this bug report are identical to
> > > the ones in unstable/testing and jessie-backports, other than
> > > debian/changelog and version numbering.
> > > 
> > > These changes have been tested in unstable since 2016-07-22 and in
> > > testing and jessie-backports since 2016-07-28, without any issues being
> > > reported.
> > > 
> > > This microcode update is very important to get Debian to run in a more
> > > stable way on the newer processors that have TSX enabled, but as usual,
> > > it also fixes other unspecified errata, so it is important even for
> > > processors without TSX.
> > 
> > Please go ahead.
> 
> Thank you!
> 
> Uploaded.

Flagged for acceptance into p-u.

Regards,

Adam

Processed: Re: Bug#834479: xul-ext-* (Was: Bug#834480: jessie-pu: package mozilla-noscript/2.9.0.11-1~deb8u1)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #834480 [release.debian.org] jessie-pu: package 
mozilla-noscript/2.9.0.11-1~deb8u1
Added tag(s) pending.

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

Processed: Re: Bug#834479: xul-ext-* (Was: Bug#834480: jessie-pu: package mozilla-noscript/2.9.0.11-1~deb8u1)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #834483 [release.debian.org] jessie-pu: package tabmixplus/0.5.0.0-1~deb8u1
Added tag(s) pending.

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

Bug#834479: xul-ext-* (Was: Bug#834480: jessie-pu: package mozilla-noscript/2.9.0.11-1~deb8u1)

[Adam D. Barratt]

Control: tags -1 + pending

On Sun, 2016-08-28 at 07:50 -1000, David Prévot wrote:
> Hi,
> 
> Le 28/08/2016 à 04:09, Adam D. Barratt a écrit :
> > Control; tags -1 + confirmed
> […]
> > Oh, how I've missed Firefox plugin updates. :-|
> 
> Same here :/
> 
> > Please go ahead.
> 
> Thanks, all uploaded.

Flagged for acceptance, thanks.

Regards,

Adam

Re: Porter roll call for Debian Stretch

[Fernando Seiti Furusato]

Hi,

I am an active porter for the following architectures and I intend
to continue this for the lifetime of the Stretch release (est. end
of 2020):

For ppc64el, I
- test most packages on this architecture
- run a Debian testing or unstable system on port that I use regularly
- triage arch-specific bugs
- fix arch-related bugs
- test d-i with some regularity
- am currently woking on providing ppc64el hardware so to include the
arch to ci.d.n

I am not a DD/DM.

I believe the port is ready to have -fPIE/-pie enabled by default.

Fernando Seiti Furusato




signature.asc
Description: OpenPGP digital signature

Re: Porter roll call for Debian Stretch

[Yunqiang Su]

Sorry for the previous post without signature.

  Hi,

  I am an active porter for the following architectures and I intend
  to continue this for the lifetime of the Stretch release (est. end
  of 2020):

  For mips, mipsel and mips64el, I
  - test most packages on this architecture
  - run a Debian testing or unstable system on port that I use regularly
  - fix toolchain issues
  - triage arch-specific bugs
  - fix arch-related bugs
  - triage d-i bugs
  - test d-i regularly
  - fix d-i bugs/issues
  - maintain buildds
  - maintain/provide hardware for (or assist with) automated tests on ci.d.n,
jenkins.d.n (etc.)
  - run other automated tests outside the Debian QA services
 Run daily build test
 Run autopkgtest
  - ...

  I am a DD

  I believe the ports *are* ready to have -fPIE/-pie enabled by default.

  YunQiang Su

> 在 2016年8月31日，00:04，YunQiang Su  写道：
> 
>  Hi,
> 
>  I am an active porter for the following architectures and I intend
>  to continue this for the lifetime of the Stretch release (est. end
>  of 2020):
> 
>  For mips, mipsel and mips64el, I
>  - test most packages on this architecture
>  - run a Debian testing or unstable system on port that I use regularly
>  - fix toolchain issues
>  - triage arch-specific bugs
>  - fix arch-related bugs
>  - triage d-i bugs
>  - test d-i regularly
>  - fix d-i bugs/issues
>  - maintain buildds
>  - maintain/provide hardware for (or assist with) automated tests on ci.d.n,
>jenkins.d.n (etc.)
>  - run other automated tests outside the Debian QA services
> Run daily build test
> Run autopkgtest
>  - ...
> 
>  I am a DD
> 
>  I believe the ports *are* ready to have -fPIE/-pie enabled by default.
> 
>  YunQiang Su
> 
> On Sun, Aug 28, 2016 at 11:53 PM, Aurelien Jarno  wrote:
>> On 2016-08-17 22:05, ni...@thykier.net wrote:
>>> 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
>> 
>> Does it really concerns *all* release architectures? Traditionally amd64
>> and i386 have been granted waivers as "the toolchain maintainers are
>> happy to support" these architectures "as-is". That said the toolchain
>> maintainers do not fix ports specific bugs outside of the toolchain.
>> 
>> While I fully agree that we can have a waiver for amd64 due to being the
>> de facto standard architecture, it seems that a few leaf packages do
>> not build on i386 and that we have no porters to fix them. That is
>> probably still fine, but I wonder how fast the number of such packages
>> will increase in the future.
>> 
>>> architectures] for the entire lifetime of Debian Stretch (est. end of
>>> 2020), please respond with a signed email containing the following
>> 
>> What is the relation between the end of support of Stretch...
>> 
>>> before Friday, the 9th of September:
>> 
>>> * Which architectures are you committing to be an active porter for?
>>> * Please describe recent relevant porter contributions.
>>> * Are you running/using Debian testing or sid on said port(s)?
>>> * Are you testing/patching d-i for the port(s)?
>>> * If we were to enable -fPIE/-pie by default in GCC-6, should that change
>>>   also apply to this port? [0]
>> 
>> ... and the above questions?
>> 
>> I fully agree that running testing/sid, fixing bugs or working on d-i up
>> to the release of Stretch will improve its quality. But after the
>> release it will improve the quality of Buster and later Bullseye. On the
>> other hand running testing/sid after the release of Stretch will not
>> help to catch bugs that can be fixed through a point release.
>> 
>> Aurelien
>> 
>> --
>> Aurelien Jarno  GPG: 4096R/1DDD8C9B
>> aurel...@aurel32.net http://www.aurel32.net
> 
> 
> 
> --
> YunQiang Su



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Porter roll call for Debian Stretch

[YunQiang Su]

  Hi,

  I am an active porter for the following architectures and I intend
  to continue this for the lifetime of the Stretch release (est. end
  of 2020):

  For mips, mipsel and mips64el, I
  - test most packages on this architecture
  - run a Debian testing or unstable system on port that I use regularly
  - fix toolchain issues
  - triage arch-specific bugs
  - fix arch-related bugs
  - triage d-i bugs
  - test d-i regularly
  - fix d-i bugs/issues
  - maintain buildds
  - maintain/provide hardware for (or assist with) automated tests on ci.d.n,
jenkins.d.n (etc.)
  - run other automated tests outside the Debian QA services
 Run daily build test
 Run autopkgtest
  - ...

  I am a DD

  I believe the ports *are* ready to have -fPIE/-pie enabled by default.

  YunQiang Su

On Sun, Aug 28, 2016 at 11:53 PM, Aurelien Jarno  wrote:
> On 2016-08-17 22:05, ni...@thykier.net wrote:
>> 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
>
> Does it really concerns *all* release architectures? Traditionally amd64
> and i386 have been granted waivers as "the toolchain maintainers are
> happy to support" these architectures "as-is". That said the toolchain
> maintainers do not fix ports specific bugs outside of the toolchain.
>
> While I fully agree that we can have a waiver for amd64 due to being the
> de facto standard architecture, it seems that a few leaf packages do
> not build on i386 and that we have no porters to fix them. That is
> probably still fine, but I wonder how fast the number of such packages
> will increase in the future.
>
>> architectures] for the entire lifetime of Debian Stretch (est. end of
>> 2020), please respond with a signed email containing the following
>
> What is the relation between the end of support of Stretch...
>
>> before Friday, the 9th of September:
>
>>  * Which architectures are you committing to be an active porter for?
>>  * Please describe recent relevant porter contributions.
>>  * Are you running/using Debian testing or sid on said port(s)?
>>  * Are you testing/patching d-i for the port(s)?
>>  * If we were to enable -fPIE/-pie by default in GCC-6, should that change
>>also apply to this port? [0]
>
> ... and the above questions?
>
> I fully agree that running testing/sid, fixing bugs or working on d-i up
> to the release of Stretch will improve its quality. But after the
> release it will improve the quality of Buster and later Bullseye. On the
> other hand running testing/sid after the release of Stretch will not
> help to catch bugs that can be fixed through a point release.
>
> Aurelien
>
> --
> Aurelien Jarno  GPG: 4096R/1DDD8C9B
> aurel...@aurel32.net http://www.aurel32.net



-- 
YunQiang Su

Re: Porter roll call for Debian Stretch

[Aron Xu]

Hi,

I am an active porter for the following architectures and I intend to continue
this for the lifetime of Streth release (est. end of 2020):

For mips, mipsel and mips64el, I
- run several Debian testing/unstable system on real mipsel/mips64el hardware
- maintain 3 mipsel/mips64el machines at data center for porting purpose
- triage arch-specific bugs
- fix arch-related bugs

I am a DD.


Regards,
Aron


signature.asc
Description: Digital signature

Bug#834545: transition: re2

[Stefano Rivera]

Hi Emilio (2016.08.29_09:58:46_+0200)
> Go ahead.

Would you mind if I held back for the next release, due on the 1st?

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272