Re: [PATCH 0/3] Add sparc64 support to base-installer

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/05/2016 09:29 PM, Cyril Brulebois wrote: >> Ping ;-). > > Sorry, but I'm pretty sure pinging people after a whooping 3-day > delay is not going to get your patches reviewed quicker. No problem. It would just be nice to have working sparc64

Processed: found 802702 in 1:1.17.1-8

Processing commands for cont...@bugs.debian.org: > found 802702 1:1.17.1-8 Bug #802702 [busybox] CVE-2011-5325: busybox: Directory traversal via crafted tar file which contains a symlink pointing outside of the current directory Marked as found in versions busybox/1:1.17.1-8. > thanks Stopping

Going ahead with non-free-firmware

Hi, I think there was consensus to introduce the non-free-firmware section and move the non-free firmware blobs there. I'm wondering what we need to do next? Besides the ftp team setting the new section up, I expect the installer would need changes to enable it instead of non-free when non-free

Re: Going ahead with non-free-firmware

On Sat, Jan 9, 2016 at 6:51 PM, Ansgar Burchardt wrote: > I think there was consensus to introduce the non-free-firmware section > and move the non-free firmware blobs there. I'm wondering what we need > to do next? I have a question about the implementation; will non-free firmware be in

Re: Going ahead with non-free-firmware

Ansgar Burchardt (2016-01-09): > I think there was consensus to introduce the non-free-firmware section > and move the non-free firmware blobs there. I'm wondering what we need > to do next? > > Besides the ftp team setting the new section up, I expect the installer > would

Processed (with 1 error): merge

Processing commands for cont...@bugs.debian.org: > severity 809932 important Bug #809932 [installation-reports] installation-reports: Successful install of Debian Stretch on Sheevaplug Severity set to 'important' from 'normal' > merge 770032 809932 Bug #770032 [partman-auto] home recipe

Processed: merge

Processing commands for cont...@bugs.debian.org: > reassign 809932 partman-auto Bug #809932 [installation-reports] installation-reports: Successful install of Debian Stretch on Sheevaplug Bug reassigned from package 'installation-reports' to 'partman-auto'. Ignoring request to alter found

Re: Going ahead with non-free-firmware

And btw: Even if Debian doesn't want to do the non-open thing now or perhaps generally doesn't want to allow people to opt-out of closed source software while keeping other non-free software, then the name non-free-firmware seems to break the current naming, doesn't it? main contrib non-free

Processing of preseed_1.69_amd64.changes

preseed_1.69.dsc has incorrect md5 checksum; deleting it Greetings, Your Debian queue daemon (running on host franck.debian.org)

Processing of preseed_1.69_amd64.changes

preseed_1.69_amd64.changes uploaded successfully to localhost along with the files: preseed_1.69.dsc preseed_1.69.tar.xz env-preseed_1.69_all.udeb file-preseed_1.69_all.udeb initrd-preseed_1.69_all.udeb network-preseed_1.69_all.udeb preseed-common_1.69_all.udeb Greetings,

Going ahead with non-free-firmware

Ansgar Burchardt wrote: > I think there was consensus to introduce the non-free-firmware > section > and move the non-free firmware blobs there. I'm wondering what we > need > to do next? While it's good that at least something happens it's really sad and kinda disturbing to see that a more

Processed: Re: Bug#810301: technical reason for "merged /usr support" in debootstrap

Processing control commands: > tag -1 -moreinfo Bug #810301 [debootstrap] merged /usr support for debootstrap Removed tag(s) moreinfo. -- 810301: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810301 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#810301: technical reason for "merged /usr support" in debootstrap

Control: tag -1 -moreinfo On Jan 09, Geert Stappers wrote: > * It is not clear what problem is being fixed. It allows to support new use cases like OS snapshots, real read only OS filesystems, real shared (maybe networked) OS filesystems and stateless computers. For a

Bug#810538: console-setup: Wide character ... in pattern match (m//) at /usr/bin/ckbcomp ...

Package: console-setup Version: 1.134 Severity: normal I'm seeing this: update-initramfs: Generating /boot/initrd.img-4.3.0-1-amd64 Wide character (U+111) in pattern match (m//) at /usr/bin/ckbcomp line 3847. Wide character (U+126) in pattern match (m//) at /usr/bin/ckbcomp line 3847. Wide

Bug#571136: please remove useless devices from devices.tar.gz

Marco d'Itri writes: > On Jan 08, Marco d'Itri wrote: > >> If there are some doubts that devices.tar.gz could still be needed in >> the future then I would start with a smaller patch which keeps all the >> old code around. > Here it is. > If somebody will report

Bug#810301: technical reason for "merged /usr support" in debootstrap

Control: tag -1 moreinfo On Fri, Jan 08, 2016 at 06:40:31AM +0100, Christian PERRIER wrote: > > To other D-I developers: I'm very tempted to give full confidence in > Marco's proposals (this one and the one related to devices creation), > apply these patches, upload and wait for input. > Any

Processed: technical reason for "merged /usr support" in debootstrap

Processing control commands: > tag -1 moreinfo Bug #810301 [debootstrap] merged /usr support for debootstrap Added tag(s) moreinfo. -- 810301: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810301 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Re: Going ahead with non-free-firmware

On Sat, Jan 09, 2016 at 10:36:53PM +0100, Philippe Cerfon wrote: > And btw: > Even if Debian doesn't want to do the non-open thing now or perhaps > generally doesn't want to allow people to opt-out of closed source > software while keeping other non-free software, then the name > non-free-firmware

Re: [PATCH 0/3] Add sparc64 support to base-installer

John Paul Adrian Glaubitz (2016-01-10): > On 01/10/2016 01:11 AM, Cyril Brulebois wrote: > > I don't see how pushing your changes to d-i git speeds things up > > for anyone. It's not like we're releasing images for this platform. > > If anyone is doing that outside

Bug#805291: marked as done (preseed: Offer a way to override initrd-level preseeding with kernel command line preseeding)

Your message dated Sat, 09 Jan 2016 22:49:19 + with message-id and subject line Bug#805291: fixed in preseed 1.69 has caused the Debian Bug report #805291, regarding preseed: Offer a way to override initrd-level preseeding with kernel command line

Bug#571136: Fwd: Re: Bug#571136: please remove useless devices from devices.tar.gz

Hi ports people, I'm not exactly sure what happened with debian-ports@ (I think there were some planned changes but I don't remember the outcome), so I'm explicitly sending this to bsd/hurd lists since I suspect the linux ports are less likely to be affected by this. We have a bug report with a

Re: [PATCH 0/3] Add sparc64 support to base-installer

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/10/2016 01:11 AM, Cyril Brulebois wrote: > John Paul Adrian Glaubitz > (2016-01-09): >> No problem. It would just be nice to have working sparc64 support >> in d-i rather soon because Wheezy is going to be EOL

preseed_1.69_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 08 Jan 2016 19:49:20 +0100 Source: preseed Binary: preseed-common network-preseed file-preseed initrd-preseed env-preseed Architecture: source all Version: 1.69 Distribution: unstable Urgency: medium Maintainer:

Re: [PATCH 0/3] Add sparc64 support to base-installer

John Paul Adrian Glaubitz (2016-01-09): > No problem. It would just be nice to have working sparc64 support in d-i > rather soon because Wheezy is going to be EOL soon and many people would > like to reinstall their sparc64 machines with a Debian release that is >

Bug#571136: Fwd: Re: Bug#571136: please remove useless devices from devices.tar.gz

On Jan 10, Cyril Brulebois wrote: > We have a bug report with a patch by Marco against debootstrap (see > attachment), which changes how devices are generated; I can't really > tell how much this might affect all of you (especially with debootstrap It is not supposed to, since

Re: What's the deal with discover*? (was: Processed: pending since 2013?)

Hi, And thanks for the details. Petter Reinholdtsen (2016-01-09): > Not quite sure what the question is, but I'll try to provide some > background information on discover in the hope that it might answer at > least part of the question. It seems a "VCS" word was missing in my

Bug#810582: [partman-base] hangs when reformatting existing fs

Package: partman-base Version: 188 Severity: important --- Please enter the report below this line. --- I just installed a new stretch system using the alpha 4 netinst image, manual install. The root partition that I chose already had a filesystem. When parted wanted to create the filesystem,

Bug#810582: [partman-base] hangs when reformatting existing fs

Hi, and thanks for your report. g...@leonde.de (2016-01-10): > Package: partman-base > Version: 188 > Severity: important > > --- Please enter the report below this line. --- > I just installed a new stretch system using the alpha 4 netinst image, manual > install. The root

Re: [PATCH 0/3] Add sparc64 support to base-installer

* John Paul Adrian Glaubitz [2016-01-02 21:10]: > Here's a small set of changes which adds support for the > sparc64 architecture. It basically clones the scripts > and tests from the sparc architecture which was using the > same 64-bit kernel that sparc64 is using.

Bug#810301: technical reason for "merged /usr support" in debootstrap

Quoting Geert Stappers (stapp...@stappers.nl): > * No pointers to the discussion in the opening of this B.R. There's a lengthy discussion in -devel and this issue about merged /usr is something I see floting around for years. Random picks in the said discussion seem to show a quite good

Re: What's the deal with discover*? (was: Processed: pending since 2013?)

Not quite sure what the question is, but I'll try to provide some background information on discover in the hope that it might answer at least part of the question. The task today of the discover package in the installation phrase is to ensure hardware specific packages are installed. It ensure