Re: Porter roll call for Debian Stretch

[Roger Shimizu]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On Wed, 17 Aug 2016 22:05:06 +0200
ni...@thykier.net wrote:

> 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 signed email containing the following
> before Friday, the 9th of September:
> 

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 armel, I
 - submit device-tree patch to upstream (linux kernel), and backport to debian 
kernel to get more devices supported
 - support new device for d-i and flash-kernel package
 - test most packages on this architecture
 - run Debian stable / testing / unstable system on port that I use regularly
 - triage arch-specific bugs
 - fix arch-related bugs
 - triage d-i bugs
 - test d-i regularly
 - fix d-i bugs/issues

I am a DM.

Altough I enabled -fPIE/-pie for most of my maintaining packages, I'm not sure 
/ I don't have enough knowledge whether it's able to be applied to all packages.
Since all other ARM porters seem agree on this, I believe it definitely 
deserves a try to enable this hardening on stretch.

Cheers,
- -- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJXzEFiAAoJEKR4aw2nAzSoAekP/j4eNf0jKvmArPlPbhA7XkBk
/5u9Un4qOHBNcSMAU5YVLHkpnT1CX/C08W+/ctGbB9AnnRwyn8X0uailjedZ13jK
oZYW/kUSwWiPmOkRTeNgFepzuKL+TNsAGgjHOY4ZbzYKC+h9C0UNWwyA77L3GUep
3HA9eTrtxMAAvJPNN4AhOjMeCI3qXIZ+wLKjhT+u/OUETWly8MolBw8PUjjwW6yy
Va7ciRMQf8KL149+Pa/tYFaENoAOV6//3M2QkJyaGbfxJp3xiFFcrlw+kw6J4RyH
vNIewz78nZwN88Y7JWa2EdBVcJr0897REXpDPXK/OpzlWw0R0xqB86jtmHfc+rQJ
IiNGt5Uc4Y3mD04O6AEDDJFJnEQ/QLi8OR8/TuxHiBJ6JTv0m67KsJVgdFqeRnlz
wJqcIQAzTF1iixVXjreVqW6P/+pGNHDbh9APfUz+UV97sZ4tD2BV1K1Rgk7cPDCn
zcpVhkQRy5PzLmK315vb8h9juFDDS/18yzmXwGMnmIhv4+8GBJIQLm5gvk9NuEbw
V/hBC42+fqX6RzGCoV3M8V+A6aLSpG/BcIAQOx8ewVfzMHIFSJmYParCHKXdiX+z
WB8UBt2xCHuzg98jxU80UwR492X9WvKeb6xA8dKqOW22XzsLxaQTe+SLSaGQ7er2
cpuhCpYFDKj/TL6UE2f9
=Vckg
-END PGP SIGNATURE-

Processed: Bug#836529 marked as pending

[Debian Bug Tracking System]

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

> tag 836529 pending
Bug #836529 [hurd] hurd: won't boot if /etc/hurd/runsystem is runsystem.gnu, 
because runsystem.hurd does not exist
Ignoring request to alter tags of bug #836529 to the same tags previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
836529: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#836529: hurd: won't boot if /etc/hurd/runsystem is runsystem.gnu, because runsystem.hurd does not exist

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #836529 [hurd] hurd: won't boot if /etc/hurd/runsystem is runsystem.gnu, 
because runsystem.hurd does not exist
Added tag(s) pending.

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

Bug#836529: hurd: won't boot if /etc/hurd/runsystem is runsystem.gnu, because runsystem.hurd does not exist

[Samuel Thibault]

Control: tags -1 + pending

Hello,

Kalle Olavi Niemitalo, on Sat 03 Sep 2016 22:13:20 +0300, wrote:
> /etc/hurd/runsystem.hurd, which does not exist.

Actually, there were not even upstream rules to install it... This is
now fixed.

Samuel

Re: Bug#836016: netcfg: Drop unnecessary loopback config in /etc/network/interfaces

[Cyril Brulebois]

Hi Martin,

Martin Pitt  (2016-08-30):
> Package: netcfg
> Version: 1.139
> 
> Hello,
> 
> netcfg still configures a "lo" (loopback) device in
> /etc/network/interfaces, although this hasn't been necessary since
> ifupdown 0.7.41 in 2013:
> 
>   
> https://anonscm.debian.org/cgit/collab-maint/ifupdown.git/commit/?id=2127aa19d9416

Thanks. Your patch looks rather sane at first glance.

I'm not sure what the status is WRT non-Linux ports so I've added bsd
and hurd people in cc.

Also, what about the /etc/networks file? (I've just discovered it while
grepping for "loopback" in the netcfg codebase.)

> Please drop it as this is unnecessary extra parsing work at boot. I
> attach an untested (only build-tested) initial patch. The main thing
> I'm not sure about is whether this actually needs to clear
> /etc/network/interfaces when NetworkManager is installed -- would
> anything write "real" interfaces to /e/n/i in this case?

I can't easily check right now.

> OOI, how can an updated netcfg be tested locally?

debcheckout debian-installer, put generated netcfg udebs below
build/localudebs, and build e.g. a netboot-gtk image (see wiki
for instructions); the resulting mini.iso should be using your
local packages (that doesn't work for all udebs since some are
loaded way later, over the network, but netcfg might be OK).

> In a more general vein, ifupdown creates an appropriate /e/n/i on package
> installation already. It would be nicer if netcfg would not completly
> overwrite this and instead just add files to /etc/network/interfaces.d/

I don't think I'm going to look into this part since I've little time at the
moment.



KiBi.


signature.asc
Description: Digital signature