Re: Bug#1068197: debian-installer: accesses the internet during build

On Mon, Apr 01, 2024 at 07:39:18PM +0200, Jonathan Carter wrote: > As far as I know, this doesn't happen until after d-i asked the question "Do > you want to use a network mirror?" and the user answered "Yes", in which > case I think that would count as informed consent. During build, not during

Re: What to do with d-i on armel?

[ Remove -arm and -release } Hi On Sun, Mar 03, 2024 at 09:01:06PM +0100, Cyril Brulebois wrote: > Maybe have it marked Not-For-Us on armel, also requesting the binary to > be dropped there? And maybe poke the ftp team to have installer-armel/ > cleaned up? (The “disabling daily builds” part

Re: What to do with d-i on armel?

On Fri, Jan 19, 2024 at 05:33:23PM +0100, Arnd Bergmann wrote: > Right, though changing the kernel package to support this > sounds easier than changing the installer to use a > foreign architecture kernel package. Well. It is a "dpkg --add-architecture" in the right spot of

What to do with d-i on armel?

Hi With Linux 6.6 we dropped the Marvell specific kernel image, as it was not known to work on any of the available devices. We still have another armel kernel left, the one of the Raspberry Pi 0 and 1, which uses an ARMv6 CPU. This also removed all the udebs from armel, which makes many d-i

Re: Immediate fallouts from the big linux changes, and actions

On Sun, Dec 24, 2023 at 08:38:57AM +0100, Cyril Brulebois wrote: > - kernel-image-* packages are now shipping /boot/vmlinuz-* (or > /boot/vmlinux-* depending on the arch), instead of just /boot/vmlinuz > (respectively /boot/vmlinux). This was even dependent on architecture. A lot of

Re: Bug#1040901: Upcoming changes to Debian Linux kernel packages

On Fri, Oct 27, 2023 at 08:43:46AM +0200, Julian Andres Klode wrote: > > > ## Image packages contains more version info > > > > > > Example: linux-image-6.5.3-cloud-arm64 > > > > > It will not longer be possible to reliably derive the package name from > > > kernel release (see above), as both

Re: Upcoming changes to Debian Linux kernel packages

On Thu, Oct 05, 2023 at 07:59:54AM -0600, Sam Hartman wrote: > I think that's what you mean by the first-level error. > If not, I'm still confused. > In the second level error case you are talking about is: No, the first level is always: but the new kernel does not work. The second is: I need to

Re: Bug#1040901: Upcoming changes to Debian Linux kernel packages

Moin On Sun, Sep 24, 2023 at 03:01:51PM +0200, Bastian Blank wrote: > ## Kernel modules will be signed with an ephemeral key This is now https://salsa.debian.org/kernel-team/linux/-/merge_requests/607. > ## Image packages contains more version info > > Example: linux-image-6.5.3

Re: Bug#1040901: Upcoming changes to Debian Linux kernel packages

Hi On Sun, Sep 24, 2023 at 06:05:09PM +0200, Ben Hutchings wrote: > > Multiple uploads of the same upstream version will have > > the same package name, but those rarely happens. > Those happen fairly often for urgent security updates. We could encode that in the upstream version. Aka to have

Re: Upcoming changes to Debian Linux kernel packages

On Tue, Oct 03, 2023 at 03:00:53PM -0500, Robert Nelson wrote: > On Tue, Oct 3, 2023 at 2:54 PM Adrian Bunk wrote: > > How will the user get the headers matching this previously-used kernel > > that are required until we provide a kernel with the regression fixed? The same as now: nowhere,

Re: Upcoming changes to Debian Linux kernel packages

Hi Andreas On Tue, Oct 03, 2023 at 11:58:29PM +0200, Andreas Beckmann wrote: > That should solve the problem where several source packages need to be > updated together. The problem does not come from multiple source packages that need to be updated together. Instead it comes from the way

Re: Upcoming changes to Debian Linux kernel packages

Hi Sam On Tue, Oct 03, 2023 at 08:31:57AM -0600, Sam Hartman wrote: > I still think it would help if you would work more on articulating what > problem you are trying to solve with the linux-headers versioning > change. I have read multiple versions of this proposal, and your > follow-ups, and I

Re: Upcoming changes to Debian Linux kernel packages

On Mon, Sep 25, 2023 at 04:35:08AM +0200, Andreas Beckmann wrote: > On 25/09/2023 00.50, Bastian Blank wrote: > > Already built modules remain until someone deletes it. So you can also > > switch back to the still installed older kernel version and it will have > > the

Re: Bug#1040901: Upcoming changes to Debian Linux kernel packages

Hi Ben On Sun, Sep 24, 2023 at 06:05:09PM +0200, Ben Hutchings wrote: > On Sun, 2023-09-24 at 15:01 +0200, Bastian Blank wrote: > > The same upstream version in testing and backports will have the same > > package name. > This is not OK, because they will be incompatibl

Re: Upcoming changes to Debian Linux kernel packages

Hi Andreas On Sun, Sep 24, 2023 at 11:10:36PM +0200, Andreas Beckmann wrote: > On 24/09/2023 15.01, Bastian Blank wrote: > > ## Kernel modules will be signed with an ephemeral key > > > > The modules will not longer be signed using the Secure Boot CA like the > &

Upcoming changes to Debian Linux kernel packages

Hi folks Debian currently does Secure Boot signing using a shim chained to the Microsoft key. This use requires that we follow certain rules. And one of the recent changes to those rules state that our method of signing kernel modules also with the same key will not be allowed anymore. Some

Re: Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize

Hi On Thu, Feb 09, 2023 at 03:16:15PM -0500, Theodore Ts'o wrote: > Right, but if the conflict in e2fsprogs-udeb prevents the installer > from pulling in an overly new version of e2fsprogs-udeb, that woul be > sufficient, no? No, it does not. Conflicts have undefined behaviour for udebs.

Re: Total removal of floppy support?

Hi Cyril On Wed, Jan 18, 2023 at 03:28:25PM +0100, Cyril Brulebois wrote: > While working on extending firmware support, I've stumbled upon floppy > support in various components. Even if the maintenance costs are low, I > suppose this could go away nowadays? It can completely go in the

Bug#987503: swap partition only 1 GB instead of at least 1 x RAM size

On Thu, Dec 08, 2022 at 11:35:43AM +0100, Jan Kowalsky wrote: > So: please set a default again which is reasonable for laptops and > workstations. We always recommend debian for desktops to our customers. > But if many things are not really suitable for Desktops people will > avoid debian. The

Bug#1018740: debootstrap: better initialisisation of /etc/machine-id

On Mon, Aug 29, 2022 at 10:52:07PM +0200, Holger Levsen wrote: > So probably it would be better to either remove the file or write > "uninitialized" > into it... or support both via commandline flags :) Actually debootstrap must write it as _empty_, to avoid running into first boot setup.[1]

Re: s390-dasd: sbuild fails, when building on amd64 machine

On Sun, Aug 28, 2022 at 08:21:15PM +0200, Holger Wansing wrote: > +STRIPTOOL=/usr/bin/s390x-linux-gnu-strip This should use DEB_HOST_GNU_TYPE at least. And not absolue path. Bastian -- Conquest is easy. Control is not. -- Kirk, "Mirror, Mirror", stardate unknown

Re: debian-installer missing Standards-Version

On Wed, Mar 23, 2022 at 10:46:08AM +0100, John Paul Adrian Glaubitz wrote: > Does anyone know whether this is by design or is this an oversight? This is by design. udeb don't follow policy. So listing a policy version is somewhat distracting. Bastian -- ... The prejudices people feel about

Bug#1000239: Rescue system won't find root partition, but insists on /usr

Control: severity -1 normal On Fri, Dec 03, 2021 at 04:08:24PM -0500, Nicholas D Steeves wrote: > Steps I used to try to reproduce: > > 1. Downloaded debian-testing-amd64-netinst.iso2021-12-03 16:21 408M > 2. Installed to EFI-enabled qemu eg: >kvm -bios /usr/share/ovmf/bios.bin -m 2G

Re: Naming convention for udebs: -udeb/-installer suffix

On Wed, Jan 13, 2021 at 03:49:40PM -0500, John Scott wrote: > It's going to take a while for me to figure out how to incorporate it into > the > installer for Bookworm, but just because it's otherwise ready I'm thinking of > doing an upload of firmware-ath9k-htc adding a udeb. We don't ship

Re: Bug#959037: lintian: FPOS? for executable-in-usr-lib

On Thu, Apr 30, 2020 at 11:41:44AM +0200, Bastian Blank wrote: > The _other_ d-i parts are only looking in the specified directories in > /usr/lib. Okay, let's expand on this. The following directories are part of the API of several d-i components: - /usr/lib/post-base-installer.d/ - /u

Re: Bug#959037: lintian: FPOS? for executable-in-usr-lib

Hi Mattia On Wed, Apr 29, 2020 at 06:40:07PM +0200, Mattia Rizzolo wrote: > On Tue, Apr 28, 2020 at 11:38:44PM +0100, Steve McIntyre wrote: > > ACK. d-i won't be looking in /usr/libexec. Please leave things where > > they are... > Good, then @lintian-maint: please exclude udebs from this check :)

Bug#949788: s390-dasd FTCBFS: strips with the build architecture strip

Moin On Sat, Jan 25, 2020 at 05:50:40AM +0100, Helmut Grohne wrote: > s390-dasd fails to cross build from source, because it strips using the > build architecture strip during build. Beyond breaking cross > compilation, this also breaks DEB_BUILD_OPTIONS=nostrip as well as > generation of -dbgsym

Bug#940801: missing virtio block Kernel Objects

On Thu, Sep 19, 2019 at 10:56:55PM +0200, Geert Stappers wrote: > The netboot tarball misses virtio block drivers. > This makes it unnessecary tiresome > to install Debian VMs on not-Internet-connected server. This is intentional. netboot is for booting from _network_. On the network you got a

Re: D-I on riscv64 / new "u-boot-menu-installer" udeb

Hi Karsten On Mon, Aug 19, 2019 at 08:36:58AM +0200, Karsten Merker wrote: > - As the udeb only contains shell scripts, in conformance with > normal policy rules Normal policy only applies pretty limited to udebs. > I have marked it as an arch:all package > that

Re: Bug#930856: autopkgtest-build-qemu: captures something from host

On Sat, Jun 29, 2019 at 04:44:32PM +0200, Bastian Blank wrote: > On Sat, Jun 29, 2019 at 02:25:55PM +, Dmitry Bogatov wrote: > > Note that APT tries to use Devuan keyring to validate Debian release and > > fail. How does `debootstrap' decides, which keyring to use? > &q

Re: Bug#930856: autopkgtest-build-qemu: captures something from host

On Sat, Jun 29, 2019 at 02:25:55PM +, Dmitry Bogatov wrote: > Note that APT tries to use Devuan keyring to validate Debian release and > fail. How does `debootstrap' decides, which keyring to use? "dpkg -s debootstrap"? How did that keyring get on the system in the first place? Bastian --

Bug#925545: busybox: please provide runscript file

Hi Dmitry On Sat, Jun 15, 2019 at 06:37:03PM +, Dmitry Bogatov wrote: > But, after all, we all volonteers here. So hereby I inform you, > following advice in Developer reference, section 5.11, that I plan to > do non-maintainer upload in two weeks or so. As we are before a release, NACK.

Bug#923091: That merged-usr is mandatory is RC

Control: severity -1 wishlist Hi Ian On Mon, May 13, 2019 at 11:22:35AM +0100, Ian Jackson wrote: > In #923091, Guillem (with dpkg maintainer hat on) asks for a > base-installer option to allow installing buster without merged-usr. No, he did not mention dpkg. But as always, please provide a

Re: UEFI Secure Boot changes in d-i and live images

On Sun, Jan 20, 2019 at 12:35:16AM +, Ben Hutchings wrote: > Yes, this is expected. Does anyone want to implement the proposal I > made at > or are we just going to have a flag day and hope no-one screws up after > that? The FTP

NEW udeb: libcrypt1-udeb

Moin Please ACK the NEW udeb: libcrypt1-udeb. AFAIK it is supposed to replace the libcrypt integrated in glibc in the future. Regards, Bastian -- Where there's no emotion, there's no motive for violence. -- Spock, "Dagger of the Mind", stardate 2715.1

Bug#911241: grub-installer - Remove grub-legacy support

Package: grub-installer Version: 1.157 Please remove grub-legacy support. I intend to request removal pretty soon as it does not longer work. Bastian -- Behind every great man, there is a woman -- urging him on. -- Harry Mudd, "I, Mudd", stardate 4513.3

Bug#907704: choose-mirror: default to deb.debian.org

Hi Philipp On Tue, Sep 04, 2018 at 09:02:42AM +0200, Philipp Kern wrote: > I pulled out my RT account to check for mirror-related problems (they > seem to be in a different queue I can't see) and found [0], so it looks > like there's now a third unannounced provider that is not in the > rotation

Bug#723966: installation-reports: /root directory deleted when re-installing

On Sat, Aug 18, 2018 at 06:52:26PM -0700, Paul Hardy wrote: > Would it be possible to copy /root someplace temporarily during > installation, for example to /home/root if /home is an available file > system or even a RAM-based temporary file system (which won't help > during a kernel panic)? Then

Bug#905165: debootstrap - fails in docker environment

Package: debootstrap Version: 1.0.106 Severity: grave debootstrap fails in docker environment completely by: - symlinking $TARGET/proc to /proc - running chroot $TARGET mount -t proc none /proc The later obviously failing with a recursive symlink: | mount: mount proc on /proc failed: Too many

Re: Archiving the attic folders from d-i for ports

On Sat, May 05, 2018 at 01:29:03PM +0200, John Paul Adrian Glaubitz wrote: > (Please CC me, I'm not subscribed to debian-boot@ at the moment). Mail-Followup-To exists and is both set and respected by decent MUA. > On 04/27/2018 08:14 AM, Bastian Blank wrote: > > On Fri, Apr 27, 2

Re: Salsa

On Fri, May 04, 2018 at 02:08:40PM +0100, Steve McIntyre wrote: > On Fri, May 04, 2018 at 10:44:00AM +0200, Bastian Blank wrote: > >Does that mean you export all the old cruft from > >/trunk/{build,kernel,tools,utils} to this new git repo? > So far, yes. As I said, "For

Re: Salsa

On Thu, May 03, 2018 at 10:10:28PM +0100, Steve McIntyre wrote: > match /trunk/ > repository d-i.git > branch master > end match Does that mean you export all the old cruft from /trunk/{build,kernel,tools,utils} to this new git repo? Bastian -- Each kiss is as the first. --

Re: Archiving the attic folders from d-i for ports

On Fri, Apr 27, 2018 at 05:37:25AM +0200, John Paul Adrian Glaubitz wrote: > Since there are still some repositories that we need for debian-ports > in the attic, I was wondering whether we should take care of the > attic stuff and move it over to salsa or github. Could you show a list? Just

Re: Salsa

On Mon, Jan 22, 2018 at 06:52:01PM +0100, Christian PERRIER wrote: > Quoting Cyril Brulebois (k...@debian.org): > > If you have time/motivation to explore salsa.debian.org for d-i things, > > that's more than welcome! > > > Does anyone have any objection if I create a d-i/boot team on Salsa? > >

Re: Salsa

On Sat, Jan 27, 2018 at 11:46:30AM +, Chris Boot wrote: > I have added the following people to the project as members: > { Alioth Role / Position } => { GitLab Role } > Admin => Owner > Senior Developer => Master > Developer => Developer > > I haven't added "Junior Developers" yet because I'm

Re: Salsa

On Thu, Jan 25, 2018 at 08:43:57PM +0100, Philip Hands wrote: > 'installer-team' would be my top choice too (given that the -team bit > seems to be necessary to accommodate the fact that gitlab uses the same > namespace for teams and users). It is possible to get different names, esp for teams

Re: Salsa

On Mon, Jan 22, 2018 at 05:28:43PM +0100, Cyril Brulebois wrote: > Chris Boot (2018-01-22): > > I think it would be helpful to start using Salsa for some of our repos. > > > > I would like to move my personal busybox work-in-progress repo to Salsa; > > I know nothing prevents

Re: Avoiding use of symlinks in d-i archive tar

Moin On Sat, Aug 05, 2017 at 03:15:51PM +0200, Bastian Blank wrote: > On Sun, Jul 30, 2017 at 04:45:38PM +0200, Cyril Brulebois wrote: > > Yeah. Feel free to propose patches for that then. > Pushed as branch "waldi/dedup-links" to debian-installer.git. Any more thou

Bug#872867: is ISO-3166 really the optimal list for our users?

On Tue, Aug 22, 2017 at 12:28:18AM +0200, Daniel Pocock wrote: > According to this section in the Debian Installer i18n guide[1], the > list of countries is based on ISO3166. Kosovo is listed in ISO3166 as RS-KM, see https://www.iso.org/obp/ui/#iso:code:3166:RS However we don't list

Re: Avoiding use of symlinks in d-i archive tar

On Sun, Jul 30, 2017 at 04:45:38PM +0200, Cyril Brulebois wrote: > Yeah. Feel free to propose patches for that then. Pushed as branch "waldi/dedup-links" to debian-installer.git. > > This symlink is handled by the archive anyway. > OK; I would have thought so but I've never looked at

Re: Avoiding use of symlinks in d-i archive tar

On Sun, Jul 30, 2017 at 03:54:59PM +0200, Cyril Brulebois wrote: > Bastian Blank <wa...@debian.org> (2017-07-30): > > Now there is exactly one other part in the archive that makes > > excessive use of symlinks: the installer. > > > > I would like to get rid of

Avoiding use of symlinks in d-i archive tar

Moin I recently did some changes to the Debian archive so that most ressources that actually change are just symlinks. This much more suits the way rsync does it's work regarding symlinks and hardlinks. In the next step I want to change our mirror script to ignore symlinks in the first sync

Bug#856210: libdebian-installer: please parse SHA256 field and add it to di_* structs

On Wed, Mar 01, 2017 at 02:25:12PM +0100, Julien Cristau wrote: > Changing semantics of an existing struct member is classic ABI breakage. > This does very much need a SONAME bump. Technically yes. But this one is noe used uncontrolled outside. So it works without. Bastian -- Warp 7 -- It's

Bug#856210: libdebian-installer: please parse SHA256 field and add it to di_* structs

On Tue, Feb 28, 2017 at 10:00:01PM +, Steven Chamberlain wrote: > That differs from the latest version of my patch, and from what I sent > earlier today to the release team when asking about a potential unblock: > https://lists.debian.org/debian-release/2017/02/msg01033.html This happens if

Bug#856210: libdebian-installer: please parse SHA256 field and add it to di_* structs

On Sun, Feb 26, 2017 at 06:30:31PM +, Steven Chamberlain wrote: > I've attached only the most minimal patch to allow reverse-depends do > implement SHA256. They must adapt to the new names of struct members > *and* remember that the hash length is now different. (The hash data is > stored in

Bug#856210: libdebian-installer: please parse SHA256 field and add it to di_* structs

On Tue, Feb 28, 2017 at 04:11:50AM +0100, Cyril Brulebois wrote: > > (If we really wanted, we could maybe avoid the ABI bump: no library > > functions are being added/removed, only the name and meaning of a struct > > member (a pointer, which remains the same length). The > > dynamically-sized

Bug#856210: libdebian-installer: please parse SHA256 field and add it to di_* structs

Hi Steven On Sun, Feb 26, 2017 at 06:30:31PM +, Steven Chamberlain wrote: > I've attached only the most minimal patch to allow reverse-depends do > implement SHA256. They must adapt to the new names of struct members > *and* remember that the hash length is now different. (The hash data is

ABI bump libdebian-installer

Hi folks We finally need to do an ABI bump for libdebian-installer. It currently have hardcoded only support for md5 and I hacked in support for sha1 some years back. This needs to be fixed finally, but will change so core structures of the packages support. Please speak up if there are

Re: own cloud task in tasksel?

On Wed, Mar 09, 2016 at 11:51:58PM +0900, Charles Plessy wrote: > This reminds me #696154 ("Please install 'less' by default on official Debian > AMIs."). Basically, there is a tension between: Also 'less' is already important, so it is supposed to be installed somehow. > Maybe this problem can

Re: s390-zfcp: Not sure I want to send translators on this bunch of cryptic strings to translate

On Tue, Feb 09, 2016 at 07:22:19AM +0100, Christian PERRIER wrote: > As a consequence, I'm highly tempted to mark all these strings as "non > translatable". Indeed they are. Just do it. Bastian -- Fascinating, a totally parochial attitude. -- Spock, "Metamorphosis", stardate

Bug#772657: ttf-cjk-compact: build-depends on ruby1.8

On Tue, Dec 09, 2014 at 09:16:50PM +0100, Ralf Treinen wrote: In fact, the jessie Sources file contains both 1.20 and 1.23. Which means there is indeed no bug against ttf-cjk-compact. It is marked with | Extra-Source-Only: yes So it is only there to fullfil source requirements with a

Re: Bug#757985: kfreebsd: hang with ENOSPC after a few components are loaded

On Wed, Aug 20, 2014 at 01:19:52AM +0100, Steven Chamberlain wrote: On 14/08/14 18:15, Cyril Brulebois wrote: [...] If a single extra udeb (or udeb size increase, which happens from time to time) is going to break kfreebsd-*, it seems to me that their status is far too brittle. The

Bug#753442: debootstrap: host's /run/shm gets unmounted after debootstrap run

On Wed, Jul 02, 2014 at 12:10:15AM +0200, Daniel Reichelt wrote: I tried debootstrap on clean and current wheezy and jessie installations, only wheezy was affected. This is due to systemd breakage. Bastian -- Without followers, evil cannot spread. -- Spock, And The Children

Bug#728706: Debian-installer crashes on IA64 in HPVM (Integrity Virtual Machines)

Control: severity -1 important Control: reassign -1 src:linux 3.2.46-1 On Mon, Nov 04, 2013 at 02:41:43PM +0100, Lennert Van Alboom wrote: Severity: grave Not really, it is not broken for many people. Booting debian 7.x installer isos in an Integrity VM (virtualization on top of HP-UX/IA64)

Bug#721869: install appropriate linux-headers

On Wed, Sep 04, 2013 at 05:03:46PM -0400, Joey Hess wrote: The CD images include linux-headers packages, but d-i does not install these by default. Which distro does? A normal user does not need to build its own modules. We also don't install a toolchain, aka build-essential. Bastian -- No

Re: Plan of action for Secure Boot support

On Wed, Aug 14, 2013 at 12:30:55AM +0200, Ben Hutchings wrote: Editing of binary packages is icky, so that's not part of the plan. Instead, after dak signs an executable, the package maintainer downloads and copies those into a separate 'source' package, which has a trivial debian/rules. (And

Re: Using out of tree modules in d-i?

On Wed, May 22, 2013 at 05:16:39PM +0200, Turbo Fredriksson wrote: On May 22, 2013, at 3:52 PM, Ben Hutchings wrote: Also, there are questions as to whether it would be legal. Legal as in CDDL clashes with GPL you mean? Binaries of ZFS linked against the Linux kernel would be licensed under

Bug#703146: Better debootstrap InRelease handling fix

On Wed, Mar 27, 2013 at 12:53:44AM +0100, Bernhard R. Link wrote: Sorry, but this is not enough to properly extract the contents of a inline signed message. You still need to do possible unescaping between those lines. Is the unescaping part necessary for InRelease files? What are the rules

Bug#703979: Available person to review/pull my fix for #703979?

On Tue, Mar 26, 2013 at 06:46:12PM -0300, Ben Armstrong wrote: git clone http://syn.theti.ca/git/debian-installer-launcher.git gitweb: http://syn.theti.ca/gitweb/?p=debian-installer-launcher.git This does one change to restrict rm to one filesyste. The second, replace umount -f with umount -l,

Bug#686502: pxz produces archives broken for busybox's unxz

On Sat, Dec 22, 2012 at 12:03:31AM +0100, Abou Al Montacir wrote: --- busybox-1.20.0/debian/patches/fix-unxz-with-multiple-streams.patch 1970-01-01 01:00:00.0 +0100 +++ busybox-1.20.0/debian/patches/fix-unxz-with-multiple-streams.patch 2012-12-21 19:23:12.0

Bug#686502: pxz produces archives broken for busybox's unxz

On Sun, Jan 06, 2013 at 09:40:00PM +0100, Bastian Blank wrote: This was the wrong mail. Bastian -- Oblivion together does not frighten me, beloved. -- Thalassa (in Anne Mulhall's body), Return to Tomorrow, stardate 4770.3. -- To UNSUBSCRIBE, email

Bug#686502: pxz produces archives broken for busybox's unxz

On Thu, Dec 27, 2012 at 10:08:07PM +0100, Abou Al Montacir wrote: + if (r == XZ_STREAM_END) { + /* Eat padding. Stream never starts with zeros, and padding is 32 aligned */ + while ((iobuf.in_pos iobuf.in_size) (iobuf.in[iobuf.in_pos] ==

Bug#686502: pxz produces archives broken for busybox's unxz

On Fri, Dec 21, 2012 at 02:06:31PM +0100, Abou Al Montacir wrote: On Thu, 2012-12-20 at 23:08 +0100, Bastian Blank wrote: On Thu, Dec 20, 2012 at 10:42:41PM +0100, Abou Al Montacir wrote: Can you please test the attached patch How does it implement stream padding? As it is implemented

Bug#686502: pxz produces archives broken for busybox's unxz

On Thu, Dec 20, 2012 at 12:22:12PM +0400, Michael Tokarev wrote: This is a grave bug in busybox. Grave because it causes silent data loss - valid (according to the format specs) input is decompressed only partially. The documentation say: SHOULD support files that have more than one Stream or

Bug#686502: pxz produces archives broken for busybox's unxz

On Thu, Dec 20, 2012 at 10:42:41PM +0100, Abou Al Montacir wrote: Can you please test the attached patch How does it implement stream padding? Bastian -- What kind of love is that? Not to be loved; never to have shown love. -- Commissioner Nancy Hedford, Metamorphosis,

Re: packages matching running kernel 3.2.0-3-amd64 in archive

On Sat, Nov 10, 2012 at 02:11:31PM +0100, Geert Stappers wrote: How to fix the version mismatch in the Debian archive? Don't use the netboot image. A D-I update is necessary to fix this. Bastian -- No one wants war. -- Kirk, Errand of Mercy, stardate 3201.7 -- To

Re: [PATCH 3/3] install-files: Include modules.{builtin,order} in Linux kernel-image udebs

On Tue, Sep 25, 2012 at 02:07:16AM +0100, Ben Hutchings wrote: libkmod expects these files to be present. However they are not being installed in the s390 tape image packages, so this probably should be made conditional. That might be a bug in the linux package though. Bastian? This is

Re: IPv6 support in d-i

On Sat, Sep 08, 2012 at 11:05:55AM +0200, Michelle Konzack wrote: Am 2012-09-08 00:19:54, hacktest Du folgendes herunter: Hey, I have since some weeks my own GE access in Kehl/Germany and am not able to get any additional IPv4 adresses from RIPE. I Have to use my assigned IPv6 block! This

Re: IPv6 support in d-i

On Sat, Sep 08, 2012 at 04:54:54PM +0200, Bjørn Mork wrote: where 2001:db8::/96 is the prefix you've allocated for your NAT64 service. Using a /96 is recommended as it makes things very simple when the IPv4 addresses just fits at the end. You may want to use the well-known prefix 64:ff9b::/96.

Re: EFI approach and patches

On Mon, Aug 13, 2012 at 01:10:31AM +0100, Steve McIntyre wrote: 1. Add a new subarch of efi for i386 and amd64 in libdebian-installer, worked out (as usual for EFI) from whether /sys/firmware/efi is accessible. This filters through readily to archdetect, used all over the place

Re: Byte queue limits in Linux for wheezy / linux kernel ABI bumps

On Sun, Aug 05, 2012 at 07:43:50PM +0200, Bastian Blank wrote: On Sat, Aug 04, 2012 at 10:06:48PM +0100, Ben Hutchings wrote: A possible solution would be something like: 1. Keep multiple versions of udebs in the same suite (currently possible for arch:all, but maybe not supported for arch

Re: [SCM] d-i libdebian-installer repository branch, master, updated. 0.79-8-g4ac8107

On Mon, Aug 06, 2012 at 02:04:08PM +0100, Ian Campbell wrote: Yes, I normally would, don't know how I missed it this time. I'll go fix it up now. dch should do this by itself in the meantime. Otherwise add DEBCHANGE_RELEASE_HEURISTIC=changelog to ~/.devscripts. Bastian -- Each kiss is as the

Re: Byte queue limits in Linux for wheezy / linux kernel ABI bumps

On Sat, Aug 04, 2012 at 10:06:48PM +0100, Ben Hutchings wrote: A possible solution would be something like: 1. Keep multiple versions of udebs in the same suite (currently possible for arch:all, but maybe not supported for arch-dependent packages) Breaks the expectations within d-i. This is

Re: Thank you so much for breaking d-i!

On Sun, Jul 15, 2012 at 03:05:17PM +0200, Marco d'Itri wrote: WTF are you talking about? We switched from module-init-tools to kmod months ago, and the last time I discussed d-i and modules with debian-boot people my understanding was that modules are now loaded by busybox. Can you provide

Re: Bug#680900: flash-kernel: support for local overrides of db settings

On Mon, Jul 09, 2012 at 01:47:18AM +0100, Ian Campbell wrote: As discussed in #667681 it would be very useful to be able to override certain per-machine settings locally. For example Boot-Device defaults to /dev/sda1 on Dreamplug but can also be sdb1 depending on local configuration. Use

Bug#482092: partman-crypto: xts support

On Sat, Jun 23, 2012 at 03:11:00PM +0200, Bastian Blank wrote: We only want to support plain64 for Wheezy. There is. You need at least 256 bit (128 for encryption, 128 for XTS). I commited support for xts-plain64 to partman-crypto. It will just double the key size used for xts, so no additional

Re: CD sizes again (and BoF reminder!)

On Fri, Jul 06, 2012 at 10:10:04PM +0100, Steve McIntyre wrote: http://cdimage.debian.org/cdimage/tmp/new-tasks/gnome-cd.list.gz Why does this contain debug packages? Bastian -- I've already got a female to worry about. Her name is the Enterprise. -- Kirk, The Corbomite

Re: CD sizes again (and BoF reminder!)

On Sat, Jul 07, 2012 at 02:34:44PM +0100, Steve McIntyre wrote: The list posted there is the full sorted list of *all* packages, as applied to the full set of CDs. The last one on CD#1 is gnome-packagekit-data, as I said, and I don't see any debug packages above that in the list. Ups, I did

Bug#482092: partman-crypto: xts support

On Sat, Jun 23, 2012 at 12:15:36PM +0200, Philipp Kern wrote: So there's nothing special about key sizes with xts as stated basically at the top of the bug report? There is. You need at least 256 bit (128 for encryption, 128 for XTS). Also I guess one should support xts-plain64 too? Is there

Re: tasksel upload

On Thu, Jun 14, 2012 at 02:48:14PM -0400, Joey Hess wrote: Bastian Blank wrote: Is there anything that speaks against an upload of tasksel? It works fine in my tests. This heuristic is just asking for trouble. # Exclude packages starting with lib

tasksel upload

Hi Is there anything that speaks against an upload of tasksel? It works fine in my tests. Okay, #676777 in debhelper needs to be fixed also. Bastian -- No one wants war. -- Kirk, Errand of Mercy, stardate 3201.7 -- To UNSUBSCRIBE, email to

tasksel todo

Hi This is some sort of tasksel todo. Remove tasksel-data === tasksel-data was introduced to help derivates change it. However most of the information is now installed as packages and more should come. Also tasksel and tasksel-data currently have a recursive dependency. So this

Bug#674060: Doesn't support reading InRelease files

On Fri, May 25, 2012 at 11:01:57AM +0200, Mehdi Dogguy wrote: index 67aa412..0b0f802 100644 --- a/src/parser_rfc822.c +++ b/src/parser_rfc822.c @@ -60,6 +60,7 @@ int di_parser_rfc822_read (char *begin, size_t size, di_parser_info *info, di_pa di_rstring field_modifier_string;

Re: installer location on mirrors

On Sat, May 19, 2012 at 10:24:17PM +0200, Joerg Jaspert wrote: I also take it we don't need/want the main/contrib/non-free in installer/, as our d-i will always be main/ only. What about firmware stuff? Bastian -- One does not thank logic. -- Sarek, Journey to Babel, stardate

Bug#670993: busybox: Please use dpkg-buildflags for hardening support

On Mon, Apr 30, 2012 at 11:00:38PM -0700, Steve Langasek wrote: On Tue, May 01, 2012 at 09:53:14AM +0400, Michael Tokarev wrote: Why do you filter this -W option? Well, it causes a build failure if you don't. ;) I inherited this from the previous Ubuntu changes, so I haven't fully reviewed

Bug#666399: s390-dasd fails to work with 20 devices visible (mostly in LPAR mode)

On Fri, Mar 30, 2012 at 02:52:58PM +0200, Philipp Kern wrote: I'm not sure about the rationale for this. s390 system can have hundreds or thousands of DASD devices. With the text frontend it is simply impossible to display such a long list, with slang it is just not pretty. So this code should

Re: libstdc++6-udeb package (Re: RFC: auto-load of D-I drivers in GNU/kFreeBSD)

On Sun, Mar 11, 2012 at 08:07:46PM +0100, Robert Millan wrote: El 5 de març de 2012 21:51, Robert Millan r...@debian.org ha escrit: 1- Add libstdc++6-udeb package (needed by devd). Oh, I wasn't aware that libstdc++ udeb had already been proposed, and it seems to be a controversial topic...

Re: libstdc++6-udeb package (Re: RFC: auto-load of D-I drivers in GNU/kFreeBSD)

On Sun, Mar 11, 2012 at 05:37:35PM -0300, Otavio Salvador wrote: On Sun, Mar 11, 2012 at 17:27, Bastian Blank wa...@debian.org wrote: Reducing libstdc++ with mklibs is tricky, so only the unreduced lib can be included into the boot image. C++ is controversial, because the output is usually

Re: #657560: apt: ...i18n_Translation-en Encountered a section with no Package: header

On Thu, Mar 01, 2012 at 03:35:51PM +0100, Didier 'OdyX' Raboud wrote: a) gracefully fallback on short translations when it fails to uncompress/parse the Translation packages; Do we need the full translations anyway? Bastian -- You! What PLANET is this! -- McCoy, The City on

Re: #657560: apt: ...i18n_Translation-en Encountered a section with no Package: header

On Thu, Mar 01, 2012 at 08:24:10PM +0100, Didier Raboud wrote: Bastian Blank wrote: Do we need the full translations anyway? Good point. Is it possible to instruct `apt-get update` to avoid downloading the Translation-en.bz2 long descriptions file (from my understanding of `man apt.conf

  1   2   3   4   5   6   7   >