Bug#805223: base-installer unable to determine kernel
Dnia 15 listopad 2015 o 22:54 Ben Hutchings napisał(a): > On Sun, 2015-11-15 at 22:17 +0100, Łukasz Stelmach wrote: >> During the installation I get a message that the installer was unable to >> find appropriate kernel package for the device. >> >> No installable kernel was found in the defined APT sources. [...] >> >> I have traced the the message and it comes from pick_kernel() in >> /usr/lib//base-installer/library.sh. In /var/log/syslog I find a message >> >> Jan 1 00:52:06 base-installer: info: could not determine kernel flavour >> >> repeated several times and followed by >> >> Jan 1 00:52:06 base-installer: info: Found kernels '' >> >> A very brief investigation suggests that that the problems comes from >> the references to unassigned $FLAVOUR variable. > > Unassigned, or empty? It's hard to tell precisely. FLAVOUR is not assigned any value in library.sh explicitly AND "$FLAVOUR" apparently evaluates to "" at line 352[1]. >> I may only suspect that >> the code containing $FLAVOUR has been moved from some file without >> moving actual assignment (like the one in >> debian/bootstrap-base.postinst) > [...] > > These functions are only ever called by debian/bootstrap-base.postinst. > I think the problem is that arch_get_kernel_flavour is failing. I have never said they are. I only gave the postinst script as an example of a place where FLAVOUR is assigned. Do you know of any other place? > This definitely doesn't seem like a proper fix. Then what is in your opinion KERNEL_FLAVOUR for? It can't but ask why there are two variables with apparently the same value (or at least values from the same set). I will try the fix suggested by Martin Michlmayr and see if it works. [1] https://sources.debian.net/src/base-installer/1.154/library.sh/#L352 -- Miłego dnia, Łukasz Stelmach
Bug#805279: cdebconf-gtk: Autoscroll on field activation
Package: cdebconf-gtk Version: 0.192 Hello, When using big fonts for accessibility, the debian installer questions do not fit on a screen any more. For such case, cdebconf-gtk implements a scrollbar. It however does not scroll automatically when tabbing between text fields, while it would be very helpful to avoid having to resort to the mouse (which some people may have difficulties to use). Samuel -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.4 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Samuel > Allez, soyez sympa ... traduisez-lui "linux" Linux, c'est comme le miel : c'est vachement bon mais ça attire les mouches. En plus, ça colle aux doigts et on a du mal à s'en défaire. -+- TP in: Guide du linuxien pervers - "Barrez vous les mouches !"
Bug#805223: base-installer unable to determine kernel
On Mon, 2015-11-16 at 10:16 +0100, Łukasz Stelmach wrote: > Dnia 15 listopad 2015 o 22:54 Ben Hutchings napisał(a): [...] > > > > > I may only suspect that > > > the code containing $FLAVOUR has been moved from some file without > > > moving actual assignment (like the one in > > > debian/bootstrap-base.postinst) > > [...] > > > > These functions are only ever called by debian/bootstrap-base.postinst. > > I think the problem is that arch_get_kernel_flavour is failing. > > I have never said they are. I only gave the postinst script as an example > of a place where FLAVOUR is assigned. Do you know of any other place? I don't; that's my point. There is one caller and it sets FLAVOUR. > > This definitely doesn't seem like a proper fix. > > Then what is in your opinion KERNEL_FLAVOUR for? It can't but ask why > there are two variables with apparently the same value (or at least > values from the same set). [...] I think it's obsolete, but it used to be used in the i386 kernel selection to decide whether to install a kernel that supports PAE. Ben. -- Ben Hutchings Everything should be made as simple as possible, but not simpler. - Albert Einstein signature.asc Description: This is a digitally signed message part
Bug#805280: debian-installer: Have big cursors available
Package: debian-installer Version: 20151024 Severity: normal User: debian-accessibil...@lists.debian.org Usertags: a11y Hello, We have support for bigger fonts along the dark theme, but the mouse is still quite small and hard to see. We'd need a set of bigger cursors, or get the existing cursor to be bigger (the cursor on my X session on my desktop is already quite big, probably thanks to the DPI setting). Samuel -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.4 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Samuel can you guys see what I type? no, raize How do I set it up so you can see it?
DebianCustomCD
Hi all, The https://wiki.debian.org/DebianCustomCD instructions are quite out-dated. Can someone update this page? I am willing to test it :) Thanks, Tom
Re: Integrate fully partman-reiser4 into d-i
I hacked (literally) a preliminary version of the of GNU Parted 3.2
source with Reiser4 support.
On Thu, Nov 12, 2015 at 8:23 AM, Edward Shishkin
wrote:
>
>
> On 11/12/2015 12:28 PM, Jose R R wrote:
>>
>> On Mon, Sep 21, 2015 at 7:49 AM, Edward Shishkin
>> wrote:
>>>
>>> On 09/21/2015 01:12 PM, Colin Watson wrote:
On Sun, Sep 20, 2015 at 07:40:37AM -0700, Jose R R wrote:
>
> I have realized that although partman-reiser4 udeb enables Reiser4 to
> be listed as an option during the Debian-Installer routine of a
> netboot ISO image, the lack of support for reiser4 in GNU Parted
> (Debian's libparted) prevents installation from the GUI interface.
It should be pretty easy to add that to parted, since nowadays the only
filesystem support it has is probing support. I suggest preparing a
patch against git://git.sv.gnu.org/parted.git master that adds the
ability to detect existing reiser4 partitions and sending it upstream;
it should only be on the order of a hundred lines.
>>>
>>>
>>>
>>> Does anybody care to prepare the patch?
>>
>> I am working on it Ed. I have been ironing out some wrinkles from the
>> last Reiser4 patch proposed several years ago in the GNU Parted
>> mailing lists. It's components and structure were basically cloned by
>> the initial btrfs patch submitted to Debian. autoreconf has been my
>> friend ;-)
>>
>>> I think we just need to a read a sector at REISER4_MAGIC_OFFSET
>>> and check the magic string ("ReIsEr4"), see definition of the struct
>>> reiser4_master_sb.
>>
>> Please enlighten me with reference to its documentation -- online or
>> in the Reiser4 source code?
>
>
> Alas, only source code..
>
> In reiser4 kernel sources look for REISER4_MAGIC_OFFSET
> and REISER4_SUPER_MAGIC_STRING.
>
> In reiser4progs it is called REISER4_MASTER_OFFSET and
> REISER4_MASTER_MAGIC respectively.
>
It can be built with the usual:
apt-get install libdevmapper-dev
./configure [ --prefix=/opt/parted-3.2/usr/local ]
make
make install
The resulting parted binary recognizes Reiser4 partitions when invoked
at your shell:
$ parted
GNU Parted 3.2
Using /dev/xda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
And it will print recognized partitions -- including reiser4, of course.
Although it was developed and tested in a local machine,
I ran PoC build on small Google Compute Engine (GCE) Cloud instance
with a couple of existing Reiser4 partitions:
Snapshot:
https://pbs.twimg.com/media/CT8U78zUwAE-ZTc.png:large
Here is GNU Parted 3.2 bz2-compressed src modified for Reiser4 (in
case I no longer have time to improve it ;-)
Source: 2.6M reiser4-parted-3.2m.tar.bz2 @
http://metztli.it/readOnlyEphemeral/reiser4-parted-3.2m.tar.bz2
SHA256SUM:
http://metztli.it/readOnlyEphemeral/reiser4-parted-3.2m.tar.bz2.SHA256SUM
Best Professional Regards.
--
Jose R R
http://metztli.it
-
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
-
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!
-
Bug#805291: preseed: Offer a way to override initrd-level preseeding with kernel command line preseeding
Source: preseed Version: 1.68 Severity: wishlist User: de...@kali.org Usertags: origin-kali In Kali, we rely on initrd preseeding to set a bunch of Debconf entries because it's the only sane way to ensure that we have those during netboot too. Unfortunately, it makes it very hard for end-users to change some of those entries... editing initrd is not the best interface. It would be very nice if there was a way to override such preseeding with the (kernel) boot command line. Right now env-preseed runs before initrd-preseed: $ ls debian-installer-startup.d/ S30env-preseed S35initrd-preseed S60auto-install I'm not sure what is the rationale for this order but if we don't want to swap the order, then I would suggest that we introduce a new syntax that let us do this operation. I think inverting the order of both script would make a lot of sense. I tried to find reasons not to but there is no intermediary script between S30 and S35 and thus except for the precedence of preseeding, it has no other impact AFAIK. Otherwise if not possible I suggest "mirror/hostname!=http://my.mirror"; as alternative syntax, somewhat mirroring the already existing ?= syntax (with the exclamation mark conveying the notion of "forcing") but I'm happy with any other syntax that you might prefer. Phil & Cyril, please share your opinions/preference as I'll probably try to implement this soonish. I track this wishlist on the Kali side too: https://bugs.kali.org/view.php?id=2143 And it's prompted by the fact that even though we set a mirror in the initrd, it would be nice if users could pick other mirrors via the command line. Example case where someone was bitten by this: https://www.linuxquestions.org/questions/debian-26/kernel-preseed-argument-vs-preseed-cfg-doesn%27t-work-4175534979/ -- System Information: Debian Release: stretch/sid APT prefers squeeze-lts APT policy: (500, 'squeeze-lts'), (500, 'oldoldstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#805291: preseed: Offer a way to override initrd-level preseeding with kernel command line preseeding
Hi, Raphaël Hertzog (2015-11-16): > In Kali, we rely on initrd preseeding to set a bunch of Debconf entries > because it's the only sane way to ensure that we have those during netboot > too. > > Unfortunately, it makes it very hard for end-users to change some of > those entries... editing initrd is not the best interface. It would > be very nice if there was a way to override such preseeding with the > (kernel) boot command line. > > Right now env-preseed runs before initrd-preseed: > $ ls debian-installer-startup.d/ > S30env-preseed S35initrd-preseed S60auto-install > > I'm not sure what is the rationale for this order but if we don't want to > swap the order, then I would suggest that we introduce a new syntax that > let us do this operation. > > I think inverting the order of both script would make a lot of sense. I > tried to find reasons not to but there is no intermediary script between > S30 and S35 and thus except for the precedence of preseeding, it has no > other impact AFAIK. > > Otherwise if not possible I suggest "mirror/hostname!=http://my.mirror"; as > alternative syntax, somewhat mirroring the already existing ?= syntax > (with the exclamation mark conveying the notion of "forcing") but I'm > happy with any other syntax that you might prefer. > > Phil & Cyril, please share your opinions/preference as I'll probably try > to implement this soonish. I'm afraid I don't have time to spend on figuring out all the possible consequences of such a move… Mraw, KiBi. signature.asc Description: Digital signature
Re: Jessie installation
(Adding debian-boot@ back.) Hi, Willie Rea (2015-11-15): > Thank you for you response. I attempted to install Jessie again and > when processing was halted, I entered terminal 4. The following is the > last few lines of the output: > > ... in-target: pdkg: error processing package ca-certificates-java > (--configure): > ... in-target: dependency problems - leaving unconfigured > ... in-target: pdkg: dependency problems prevent configuration of default-jre: > ... in-target: default-jre depends on default-jre-headless (= 2:1.7-52); > however: > ... in-target: Package default-jre-headless is not configured yet. > ... in-target: default-jre depends on openjdk-7-jre (>= 7~u3-2.1.1); however: > ... in-target: Package openjdk-7-jre:amd64 is not configured yeet. > ... in-target: > ... in-target: dpkg: error processing package default-jre (--configure): > ... in-target: dependency problems - leaving unconfigured > ... in-target: Errors were encountered while processing: > ... in-target: openjdk-7-jre-headless:amd64 > ... in-target: openjdk-7-jre:amd64 > ... in-target: default-jre-headless > ... in-target: ca-certificates-java > ... in-target: default-jre > ... kernel: [ 7872.781984] ISO 9660 Extensions: Microsoft Joliet Level 3 > ... kernel: [ 7872.785641] ISO 9660 Extensions: RRIP_1991A > ... kernel: [ 7874.958767] ISO 9660 Extensions: Microsoft Joliet Level 3 > ... kernel: [ 7874.960941] ISO 9660 Extensions: RRIP_1991A > ... main-menu [358]: WARNING ** Configuring 'kpgsel' failed with error code 1 > ... main-menu [358]: WARNING ** Menu item 'pkgsel' failed. We're missing the actual error which is likely going to be a few lines above. You could try reading /var/log/syslog with more if you can't scroll back enough. Possibly an issue with /proc not being mounted? (Which I seem to recall is a rather frequent issue with java-based stuff in chroots/environments where /proc isn't available.) Mraw, KiBi. signature.asc Description: Digital signature
Processing of cdebconf_0.196_i386.changes
cdebconf_0.196_i386.changes uploaded successfully to ftp-master.debian.org along with the files: cdebconf_0.196.dsc cdebconf_0.196.tar.xz cdebconf-gtk-udeb_0.196_i386.udeb cdebconf-gtk_0.196_i386.deb cdebconf-newt-udeb_0.196_i386.udeb cdebconf-priority_0.196_all.udeb cdebconf-text-udeb_0.196_i386.udeb cdebconf-udeb_0.196_i386.udeb cdebconf_0.196_i386.deb libdebconfclient0-dev_0.196_i386.deb libdebconfclient0-udeb_0.196_i386.udeb libdebconfclient0_0.196_i386.deb Greetings, Your Debian queue daemon (running on host coccia.debian.org)
Processing of cdebconf_0.196_i386.changes
cdebconf_0.196_i386.changes uploaded successfully to localhost along with the files: cdebconf_0.196.dsc cdebconf_0.196.tar.xz cdebconf-gtk-udeb_0.196_i386.udeb cdebconf-gtk_0.196_i386.deb cdebconf-newt-udeb_0.196_i386.udeb cdebconf-priority_0.196_all.udeb cdebconf-text-udeb_0.196_i386.udeb cdebconf-udeb_0.196_i386.udeb cdebconf_0.196_i386.deb libdebconfclient0-dev_0.196_i386.deb libdebconfclient0-udeb_0.196_i386.udeb libdebconfclient0_0.196_i386.deb Greetings, Your Debian queue daemon (running on host franck.debian.org)
cdebconf_0.196_i386.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 16 Nov 2015 07:05:20 +0100 Source: cdebconf Binary: cdebconf cdebconf-gtk libdebconfclient0 libdebconfclient0-dev cdebconf-udeb cdebconf-priority libdebconfclient0-udeb cdebconf-text-udeb cdebconf-newt-udeb cdebconf-gtk-udeb Architecture: source i386 all Version: 0.196 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Christian Perrier Description: cdebconf - Debian Configuration Management System (C-implementation) cdebconf-gtk - Gtk+ frontend for Debian Configuration Management System cdebconf-gtk-udeb - Gtk+ frontend for Debian Configuration Management System (udeb) cdebconf-newt-udeb - Newt frontend for Debian Configuration Management System (udeb) cdebconf-priority - Change debconf priority (udeb) cdebconf-text-udeb - Plain text frontend for Debian Configuration Management System (udeb) cdebconf-udeb - Debian Configuration Management System (C-implementation) (udeb) libdebconfclient0 - Debian Configuration Management System (C-implementation library) libdebconfclient0-dev - Development files for cdebconf libdebconfclient0-udeb - Debian Configuration Management System (C-implementation) (udeb) Changes: cdebconf (0.196) unstable; urgency=medium . [ Samuel Thibault ] * Add control-+/- shortcuts to adjust font size. Checksums-Sha1: 893f3cfbce979fa5b8ab4ce24b17b9db1fff462c 2567 cdebconf_0.196.dsc c71e0b56f88a9f55b4e487163b1ea184d9fb5d6b 267228 cdebconf_0.196.tar.xz 6dbc922559f1c97a45eb151e9fae37de7b9b4756 30928 cdebconf-gtk-udeb_0.196_i386.udeb fc27b2f476b375b939d0e437769cbbfff45def39 72576 cdebconf-gtk_0.196_i386.deb 7c18623e5dcbc9306f3d205052d9adc77a31d679 20314 cdebconf-newt-udeb_0.196_i386.udeb b632e9581cd87a9b06357108454830a2f6fa7ad3 3156 cdebconf-priority_0.196_all.udeb 60a8bc077ac844328348fc1e493fcd20f1fc059d 23120 cdebconf-text-udeb_0.196_i386.udeb f64d988dc813a1cdfe7f5eb78e58b03846123cbb 81142 cdebconf-udeb_0.196_i386.udeb 66bbee73ad2ca9959abb8026f5b3ab4c901978dc 177460 cdebconf_0.196_i386.deb 4fbe3458f9224d5e2ab6d4d24c560e7cf3b055d7 50886 libdebconfclient0-dev_0.196_i386.deb 075c1b29344779655dbf908b690a9cbcdeec8f00 3182 libdebconfclient0-udeb_0.196_i386.udeb e3da91aefb1b1db3a203f72cfa3ead5a6b76650c 46346 libdebconfclient0_0.196_i386.deb Checksums-Sha256: a4c0095d739f1677cb66c698a70007fd63e22516e9c4e1aa54edae777017fdcf 2567 cdebconf_0.196.dsc 508cc082a66a238d8bc486151a4074190b86892ddeeb9b90c54beeb51baa2d6b 267228 cdebconf_0.196.tar.xz 081ca1f5d103877daea114eeece9eee9ee0559cebe5b55048f62fbb3c278733a 30928 cdebconf-gtk-udeb_0.196_i386.udeb fb19228e5b75b2841ad0c825f942f37dfc9e2a58e348e21913786135e8c6d1f1 72576 cdebconf-gtk_0.196_i386.deb 09f7e6f2e2bcab52d727e6c504c35bd18cb607a55758b76a45e3d76841670cf5 20314 cdebconf-newt-udeb_0.196_i386.udeb 00c7d6071e84d31be3fdc855f84f09c29b83aa677c3db1b579cc704c172b5c01 3156 cdebconf-priority_0.196_all.udeb d99e459c679ce6fba6d0da2f05e1aa9f7bda9145b524a1e704f402cca2f363a3 23120 cdebconf-text-udeb_0.196_i386.udeb bf984fc4e16aea4c7c9d498973ae7e8b767f63c53ee8413392c350da695f379b 81142 cdebconf-udeb_0.196_i386.udeb 05ced8e7b2a836d8ad11199b7495e10cf6768f2488a460a23fb1c0ac7f456ba5 177460 cdebconf_0.196_i386.deb 70a66e5658fb9a18cce228cc6c46e91a7bd1ad493fb00c5070c2c6ccf0ecc21f 50886 libdebconfclient0-dev_0.196_i386.deb 71d9ad623fa0b54f157c2da5b3e7a23810b64f82787526ce3433d3d44eb76ec2 3182 libdebconfclient0-udeb_0.196_i386.udeb dd9345f9c817bb0f198af1a84b261c92d952625523c416d4269e734a30c14b5b 46346 libdebconfclient0_0.196_i386.deb Files: daa1f7a5b638b269914715e9210c4275 2567 utils optional cdebconf_0.196.dsc 2c2453f95f3d4445fae9f7a6a54eeea0 267228 utils optional cdebconf_0.196.tar.xz ad0774eb833b91ca9fbfe6bdb80ecea7 30928 debian-installer optional cdebconf-gtk-udeb_0.196_i386.udeb 8a19a93d466d48634e4452840f7ca175 72576 admin extra cdebconf-gtk_0.196_i386.deb eea6e7a75b5067734798e7fbfef62087 20314 debian-installer optional cdebconf-newt-udeb_0.196_i386.udeb 6224a659162b5a56777ad215e046cb20 3156 debian-installer standard cdebconf-priority_0.196_all.udeb 76678883b772485e3fd4ed2790350449 23120 debian-installer optional cdebconf-text-udeb_0.196_i386.udeb 030e69fa4cc4b171a946b148700d0a92 81142 debian-installer standard cdebconf-udeb_0.196_i386.udeb 7e21c4eb75f54d58933e618e213d1de2 177460 utils extra cdebconf_0.196_i386.deb 18a17469508a9e7cf824d54b74770fb6 50886 libdevel optional libdebconfclient0-dev_0.196_i386.deb 7bda7a00a61472917ec1df1b0335a666 3182 debian-installer optional libdebconfclient0-udeb_0.196_i386.udeb afc34f300b28f72872932cd2c5cf362c 46346 libs optional libdebconfclient0_0.196_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWShSCAAoJEIcvcCxNbiWoB3IQALPL8doRFxUKOSIIl84i0V2n DkHjYZUqV+ilEYzh4FvUgXw3XRudMfkGkdSboV9U8pjH8viv7krzoCduDK0joQYN dsm8Xj4huCmI4Rl9HGYPxZS1qj442Kg8Hv4QHbiTmO7IGXjFTuGI0k5Vt0oGTnAW +V1h+4zsEOCXByS7sL1qYY3V+vT6Ft
Bug#805305: tasksel: Please consider adding GNOME Flashback as a desktop choice
Source: tasksel
Version: 3.34
Severity: wishlist
Dear tasksel maintainers,
I would like you to consider adding the GNOME Flashback desktop to the list of
supported desktop environments in Debian.
GNOME Flashback is the classic desktop based on the GNOME Panel and the Metacity
window manager — the same components that were powering the default session in
Debian ≤ 6 (Squeeze). It tries to use mainline GNOME components where possible,
all code specific to the GNOME Flashback session (apart from the panel and the
WM) is in the gnome-flashback package.
Some links:
* https://wiki.gnome.org/Projects/GnomeFlashback
* http://mitya57.me/weblog/2015/07/gnome-flashback-316-in-testing.html
According to the commit message in [1], there may be not enough space to add yet
another desktop, however I consider that GNOME Flashback is a better choice for
the top list as compared to i.e. MATE or Cinnamon, as it has a small codebase,
is actively developed, uses modern GNOME technologies and is familiar for users
of previous Debian versions.
[1]:
http://anonscm.debian.org/cgit/tasksel/tasksel.git/commit/?id=952ee6491807d54d
I do not have much tasksel experience, however attached is a potential patch
against the packaging git master. Thanks for considering this.
--
Dmitry ShachnevFrom c381f8c60f698813f95d6ee5ed078b7f7bf2783a Mon Sep 17 00:00:00 2001
From: Dmitry Shachnev
Date: Mon, 2 Nov 2015 00:21:25 +0300
Subject: [PATCH] Add GNOME Flashback as a desktop choice
---
debian/control| 51 ++-
debian/templates | 2 +-
tasks/gnome-flashback-desktop | 7 ++
3 files changed, 58 insertions(+), 2 deletions(-)
create mode 100644 tasks/gnome-flashback-desktop
diff --git a/debian/control b/debian/control
index e754936..208d8d5 100644
--- a/debian/control
+++ b/debian/control
@@ -44,7 +44,7 @@ Recommends:
# The order here is significant when installing this task manually;
# when tasksel installs this task it instead selects one of these based
# on the tasksel/desktop debconf setting.
- task-gnome-desktop | task-xfce-desktop | task-kde-desktop | task-lxde-desktop | task-cinnamon-desktop | task-mate-desktop,
+ task-gnome-desktop | task-gnome-flashback-desktop | task-xfce-desktop | task-kde-desktop | task-lxde-desktop | task-cinnamon-desktop | task-mate-desktop,
# For use by third-party apps.
xdg-utils,
# mdns/zeroconf stuff
@@ -96,6 +96,55 @@ Recommends:
# we need a working network setup at least
network-manager-gnome,
+Package: task-gnome-flashback-desktop
+Architecture: all
+Description: GNOME Flashback
+ This task package is used to install the Debian desktop, featuring
+ the GNOME Flashback desktop environment, and with other packages that
+ Debian users expect to have available on the desktop.
+Depends: ${misc:Depends},
+ task-desktop,
+# the basic components required for the session
+ gnome-session-flashback,
+# the display manager
+ gdm3,
+# the control center
+ gnome-control-center,
+# some core GNOME applications
+ eog,
+ gedit,
+ gnome-calculator,
+ gnome-screenshot,
+ gnome-terminal,
+# network manager applet
+ network-manager-gnome,
+Recommends:
+# accessibility support
+ gnome-orca,
+# web browser
+ iceweasel,
+# mail client
+ evolution,
+# package management
+ gnome-software,
+# some non-core GNOME applications
+ alacarte,
+ gnome-disk-utility,
+ gnome-documents,
+ gnome-tweak-tool,
+ yelp,
+# libreoffice suite
+ libreoffice,
+ libreoffice-gnome,
+ libreoffice-evolution,
+ libreoffice-help-en-us,
+# make thesaurus work
+ mythes-en-us,
+# make spellchecker work
+ hunspell-en-us,
+# make hyphenation work
+ hyphen-en-us,
+
Package: task-kde-desktop
Architecture: all
Description: KDE
diff --git a/debian/templates b/debian/templates
index bccc719..faa4d75 100644
--- a/debian/templates
+++ b/debian/templates
@@ -17,7 +17,7 @@ _Description: Choose software to install:
Template: tasksel/desktop
Type: multiselect
-Choices: gnome, kde, xfce, lxde, cinnamon, mate
+Choices: gnome, gnome-flashback, kde, xfce, lxde, cinnamon, mate
Description: This can be preseeded to override the default desktop.
Template: tasksel/title
diff --git a/tasks/gnome-flashback-desktop b/tasks/gnome-flashback-desktop
new file mode 100644
index 000..5657696
--- /dev/null
+++ b/tasks/gnome-flashback-desktop
@@ -0,0 +1,7 @@
+Task: gnome-flashback-desktop
+Relevance: 7
+Parent: desktop
+Test-default-desktop: 3 gnome-flashback
+Section: user
+Key:
+ task-gnome-flashback-desktop
--
2.6.2
signature.asc
Description: OpenPGP digital signature
Re: cdebconf_0.196_i386.changes ACCEPTED into unstable
Debian FTP Masters (2015-11-16): > cdebconf (0.196) unstable; urgency=medium > . >[ Samuel Thibault ] >* Add control-+/- shortcuts to adjust font size. I'm sorry but the implementation doesn't look reasonable at first glance. We already have gtk-set-font, which handles font name and font size selection, in rootskel-gtk. Couldn't we adjust that instead of implementing a(nother) sed call within cdebconf-gtk? (Keeping in mind we will go to gtk3 at some point, and it would be better if we didn't have to change setting-related stuff in more than a single location.) Also, picking a random non-default language like Chinese or Dzongkha, then increasing the font leads to G_IS_OBJECT assertion failure and localechooser fails with error 1 (going back to the language selection). Mraw, KiBi. signature.asc Description: Digital signature
Re: cdebconf_0.196_i386.changes ACCEPTED into unstable
Hello, Cyril Brulebois, on Mon 16 Nov 2015 22:39:26 +0100, wrote: > Debian FTP Masters (2015-11-16): > > cdebconf (0.196) unstable; urgency=medium > > . > >[ Samuel Thibault ] > >* Add control-+/- shortcuts to adjust font size. > > I'm sorry but the implementation doesn't look reasonable at first > glance. We already have gtk-set-font, which handles font name and font > size selection, in rootskel-gtk. Couldn't we adjust that instead of > implementing a(nother) sed call within cdebconf-gtk? Christian uploaded before I got ideas about doing it in a better way :) I've been thinking about it, and perhaps we can indeed make cdebconf instead increase a value in some /etc/gtk-2 file, which gtk-set-font would add to its default "9" value. We'd then have to make cdebconf_gtk_di_run_dialog run gtk_rc_reparse_all_for_settings(). > Also, picking a random non-default language like Chinese or Dzongkha, > then increasing the font leads to G_IS_OBJECT assertion failure and > localechooser fails with error 1 (going back to the language selection). Ah, I had tested that, but didn't realize it was still posing problem. This seems very odd, and it seems to me like some bug deeper somewhere. I initially just modified gtkrc and called gtk_rc_reparse_all_for_settings(), but the next choice being made would get the kind of assertion failure you are talking about. I added the cdebconf_gtk_set_answer_notok() call to make sure to restart the question with the new size (which is needed anyway to recompute the layout). Samuel
Re: cdebconf_0.196_i386.changes ACCEPTED into unstable
Hi, Samuel Thibault (2015-11-16): > Cyril Brulebois, on Mon 16 Nov 2015 22:39:26 +0100, wrote: > > I'm sorry but the implementation doesn't look reasonable at first > > glance. We already have gtk-set-font, which handles font name and font > > size selection, in rootskel-gtk. Couldn't we adjust that instead of > > implementing a(nother) sed call within cdebconf-gtk? > > Christian uploaded before I got ideas about doing it in a better way > :) That happens. ;) > I've been thinking about it, and perhaps we can indeed make > cdebconf instead increase a value in some /etc/gtk-2 file, which > gtk-set-font would add to its default "9" value. We'd then have to make > cdebconf_gtk_di_run_dialog run gtk_rc_reparse_all_for_settings(). Something along these lines would probably work, yes. > > Also, picking a random non-default language like Chinese or > > Dzongkha, then increasing the font leads to G_IS_OBJECT assertion > > failure and localechooser fails with error 1 (going back to the > > language selection). > > Ah, I had tested that, but didn't realize it was still posing problem. > This seems very odd, and it seems to me like some bug deeper > somewhere. I initially just modified gtkrc and called > gtk_rc_reparse_all_for_settings(), but the next choice being made > would get the kind of assertion failure you are talking about. I > added the cdebconf_gtk_set_answer_notok() call to make sure to restart > the question with the new size (which is needed anyway to recompute > the layout). I must confess I don't have much time to dig into this. Feel free to record that as a bug report for the time being; while we hadn't ctrl-+/- support until this upload, this might break cause regressions depending on user input, and cause some confusion. Mraw, KiBi. signature.asc Description: Digital signature
Re: cdebconf_0.196_i386.changes ACCEPTED into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi everyone, On 16/11/15 22:01, Cyril Brulebois wrote: > Hi, > > Samuel Thibault (2015-11-16): >> Cyril Brulebois, on Mon 16 Nov 2015 22:39:26 +0100, wrote: >>> I'm sorry but the implementation doesn't look reasonable at >>> first glance. We already have gtk-set-font, which handles font >>> name and font size selection, in rootskel-gtk. Couldn't we >>> adjust that instead of implementing a(nother) sed call within >>> cdebconf-gtk? >> >> Christian uploaded before I got ideas about doing it in a better >> way :) > > That happens. ;) > >> I've been thinking about it, and perhaps we can indeed make >> cdebconf instead increase a value in some /etc/gtk-2 file, which >> gtk-set-font would add to its default "9" value. We'd then have >> to make cdebconf_gtk_di_run_dialog run >> gtk_rc_reparse_all_for_settings(). > > Something along these lines would probably work, yes. > >>> Also, picking a random non-default language like Chinese or >>> Dzongkha, then increasing the font leads to G_IS_OBJECT >>> assertion failure and localechooser fails with error 1 (going >>> back to the language selection). >> >> Ah, I had tested that, but didn't realize it was still posing >> problem. This seems very odd, and it seems to me like some bug >> deeper somewhere. I initially just modified gtkrc and called >> gtk_rc_reparse_all_for_settings(), but the next choice being >> made would get the kind of assertion failure you are talking >> about. I added the cdebconf_gtk_set_answer_notok() call to make >> sure to restart the question with the new size (which is needed >> anyway to recompute the layout). > > I must confess I don't have much time to dig into this. Feel free > to record that as a bug report for the time being; while we hadn't > ctrl-+/- support until this upload, this might break cause > regressions depending on user input, and cause some confusion. > > Mraw, KiBi. > Jumping slightly on the cdebconf bandwagon here. Having finally a proper Internet connection, I've pushed a few changes that had been sleeping on my laptop for a while. They include : * Lintian overrides for what is considered misuse of debconf templates. * SeLinux support, which is disabled for d-i builds * Rewording of some long descriptions * The long awaited possibility to show passwords in clear with the GTK and newt plugins. (Sorry Christian, more translations). Overall, the actual changes are relatively limited and local when taking patches individually, so should be fairly safe. If there's anything I could improve, please let me know. Thanks, Regis
More cdebconf improvements
Hi, (Adjusting subject slightly.) Regis Boudin (2015-11-16): > Jumping slightly on the cdebconf bandwagon here. Having finally a > proper Internet connection, I've pushed a few changes that had been > sleeping on my laptop for a while. They include : > > * Lintian overrides for what is considered misuse of debconf templates. > * SeLinux support, which is disabled for d-i builds > * Rewording of some long descriptions > * The long awaited possibility to show passwords in clear with the > GTK and newt plugins. (Sorry Christian, more translations). > > Overall, the actual changes are relatively limited and local when > taking patches individually, so should be fairly safe. > > If there's anything I could improve, please let me know. I thought we discussed stuff involving an ABI bump, but that doesn't seem to be the case. Maybe you managed to avoid this? Or maybe I'm just confused about different patchsets? Anyway, as you said, besides translations, patches look small enough to be easily debugged (or worst case reverted) if needed, so I'm fine with getting the whole lot uploaded whenever someone feels like being responsible for what happens next. ;) Mraw, KiBi. signature.asc Description: Digital signature
Re: More cdebconf improvements
On 16/11/15 23:29, Cyril Brulebois wrote: > Hi, > > (Adjusting subject slightly.) > > Regis Boudin (2015-11-16): >> Jumping slightly on the cdebconf bandwagon here. Having finally a >> proper Internet connection, I've pushed a few changes that had been >> sleeping on my laptop for a while. They include : >> >> * Lintian overrides for what is considered misuse of debconf templates. >> * SeLinux support, which is disabled for d-i builds >> * Rewording of some long descriptions >> * The long awaited possibility to show passwords in clear with the >> GTK and newt plugins. (Sorry Christian, more translations). >> >> Overall, the actual changes are relatively limited and local when >> taking patches individually, so should be fairly safe. >> >> If there's anything I could improve, please let me know. > > I thought we discussed stuff involving an ABI bump, but that doesn't > seem to be the case. Maybe you managed to avoid this? Or maybe I'm just > confused about different patchsets? That's a different patch indeed, which I won't push without a minimum of coordination as it changes the API/ABI of the plugin inteface. Also the patch is more intrusive, and I would probably need to review it again before pushing it. > Anyway, as you said, besides translations, patches look small enough to > be easily debugged (or worst case reverted) if needed, so I'm fine with > getting the whole lot uploaded whenever someone feels like being > responsible for what happens next. ;) Well, I can't upload at the moment, so I'll pass on the offer. Also, we might want to wait a couple of days to get the new text translated in a few languages ? Thanks, Regis
Bug#805321: debian-installer: builds unreproducible netboot images
Package: debian-installer Version: 20150422 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertag: timestamps fileordering infrastructure X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org X-Debbugs-Cc: debian-...@lists.debian.org Hi! The debian-installer package build produces netboot.tar.gz and the mini.iso netboot install media. It doesn't do this in an easily reproducible way: * the d-i initrd/mfsroot is a filesystem image, having variable mtime/ctime/atime timestamps from package build time; * likewise in the generated mini.iso; * netboot.tar.gz also has varying timestamps; the order of files may also vary depending on the filesystem; * likewise in the cd info tarball; * likewise in the debian-installer-images tarball; * all gzipped outfile files have a timestamp in the header. I have a patch aimed at jessie-kfreebsd that should fix all of the above. It should be possible to do the same in sid with much less code, due to new GNU tar features and other reproducible builds work. I've 'clamped' timestamps to be no later than the most recent debian/changelog entry date. That way, the non-useful timestamps from during the build are adjusted to a constant value. Older timestamps, actually indicating how old a file is, are untouched. The BUILD_DATE, actually the package version number, is unchanged. Specifically on kfreebsd, the generated mfsroot is a ffs filesystem having file atimes, and another timestamp in the filesystem superblock. I intend to patch makefs so that it can clamp timestamps to a given SOURCE_DATE_EPOCH. Besides a file ordering issue in makefs, all output files including netboot.tar.gz and mini.iso then seem to be reproducible for jessie-kfreebsd, at least. :) Regards, -- Steven Chamberlain ste...@pyro.eu.org signature.asc Description: Digital signature
Processing of partman-zfs_45+kbsd8u2_source.changes
partman-zfs_45+kbsd8u2_source.changes uploaded successfully to ftp-master.debian.org along with the files: partman-zfs_45+kbsd8u2.dsc partman-zfs_45+kbsd8u2.tar.xz Greetings, Your Debian queue daemon (running on host coccia.debian.org)
Re: More cdebconf improvements
Regis Boudin (2015-11-16): > That's a different patch indeed, which I won't push without a minimum of > coordination as it changes the API/ABI of the plugin inteface. Also the > patch is more intrusive, and I would probably need to review it again > before pushing it. OK, thanks for confirming/clarifying. Feel free to push to a pu/$something branch once you have polished it for review and coordination. > > Anyway, as you said, besides translations, patches look small enough > > to be easily debugged (or worst case reverted) if needed, so I'm > > fine with getting the whole lot uploaded whenever someone feels like > > being responsible for what happens next. ;) > > Well, I can't upload at the moment, so I'll pass on the offer. Also, > we might want to wait a couple of days to get the new text translated > in a few languages ? Indeed, no hurry. Just saying there's no need to coordinate as that's not what I was thinking about (no ABI/API changes). Mraw, KiBi. signature.asc Description: Digital signature
Processing of partman-zfs_45+kbsd8u2_source.changes
partman-zfs_45+kbsd8u2_source.changes uploaded successfully to localhost along with the files: partman-zfs_45+kbsd8u2.dsc partman-zfs_45+kbsd8u2.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org)
Bug#805321: debian-installer: builds unreproducible netboot images
Attached is my jessie-kfreebsd implementation. As I said, it should be
much cleaner to implement this in sid with newer GNU tar.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/build/Makefile b/build/Makefile
index ec5a084..6261a4d 100644
--- a/build/Makefile
+++ b/build/Makefile
@@ -56,7 +56,7 @@
# Add to PATH so dpkg will always work, and so local programs will be found.
PATH := util:$(PATH):/usr/sbin:/sbin
EATMYDATA = $(shell which eatmydata 2>/dev/null)
-GZIP = $(shell which pigz gzip | head -1)
+GZIP = $(shell which pigz gzip | head -1) -n
# We don't want this to be run each time we re-enter.
ifndef DEB_HOST_ARCH
@@ -149,7 +149,7 @@ MFSROOT_LIMIT := 68m
endif
define mkfs.ufs1
- sh -c 'makefs -t ffs -s $(MFSROOT_LIMIT) -f 3000 -o minfree=0,version=1 $$0 ${TREE}'
+ sh -c 'makefs -t ffs -T $(SOURCE_DATE_EPOCH) -s $(MFSROOT_LIMIT) -f 3000 -o minfree=0,version=1 $$0 ${TREE}'
endef
define e2fsck
@@ -803,7 +803,14 @@ $(TEMP_MINIISO): $(TEMP_BOOT_SCREENS) arch_miniiso
# various kinds of information, for use on debian-cd isos
$(DEBIAN_CD_INFO): $(TEMP_BOOT_SCREENS) $(TEMP_CD_INFO_DIR)
- (cd $(TEMP_CD_INFO_DIR); tar czf - .) > $@
+ # Clamp timestamps to be no newer than last changelog entry, see
+ # https://wiki.debian.org/ReproducibleBuilds/TimestampsInTarball
+ find $(TEMP_CD_INFO_DIR) -newermt "@$(SOURCE_DATE_EPOCH)" -print0 | xargs -0r touch --no-dereference --date="@$(SOURCE_DATE_EPOCH)"
+ # Create tarball with files sorted in a stable order, see
+ # https://wiki.debian.org/ReproducibleBuilds/FileOrderInTarballs
+ # and without timestamp in the gzip header, see
+ # https://wiki.debian.org/ReproducibleBuilds/TimestampsInGzipHeaders
+ ( cd $(TEMP_CD_INFO_DIR) && find . -print0 | LC_ALL=C sort -z | GZIP=-n tar --no-recursion --null -T - -czf -) > $@
update-manifest $@ $(MANIFEST-DEBIAN_CD_INFO)
# a directory full of files for netbooting
@@ -822,7 +829,14 @@ $(NETBOOT_TAR): $(TEMP_NETBOOT_DIR)
# Create an version info file.
echo 'Debian version: $(DEBIAN_VERSION)' > $(TEMP_NETBOOT_DIR)/version.info
echo 'Installer build: $(BUILD_DATE)' >> $(TEMP_NETBOOT_DIR)/version.info
- (cd $(TEMP_NETBOOT_DIR); tar czf - .) > $@
+ # Clamp timestamps to be no newer than last changelog entry, see
+ # https://wiki.debian.org/ReproducibleBuilds/TimestampsInTarball
+ find $(TEMP_NETBOOT_DIR) -newermt "@$(SOURCE_DATE_EPOCH)" -print0 | xargs -0r touch --no-dereference --date="@$(SOURCE_DATE_EPOCH)"
+ # Create tarball with files sorted in a stable order, see
+ # https://wiki.debian.org/ReproducibleBuilds/FileOrderInTarballs
+ # and without timestamp in the gzip header, see
+ # https://wiki.debian.org/ReproducibleBuilds/TimestampsInGzipHeaders
+ ( cd $(TEMP_NETBOOT_DIR) && find . -print0 | LC_ALL=C sort -z | GZIP=-n tar --no-recursion --null -T - -czf -) > $@
update-manifest $@ $(MANIFEST-NETBOOT_TAR) $(UDEB_LISTS)
$(TEMP_BOOT_SCREENS): arch_boot_screens
diff --git a/build/config/x86.cfg b/build/config/x86.cfg
index 3caadd2..b0fc9a2 100644
--- a/build/config/x86.cfg
+++ b/build/config/x86.cfg
@@ -332,6 +332,11 @@ arch_miniiso: x86_syslinux x86_grub_efi
| todos > $(TEMP_CD_TREE)/win32-loader.ini; \
fi
+ # Clamp timestamps to be no newer than last changelog entry, see
+ # https://wiki.debian.org/ReproducibleBuilds/TimestampsInTarball
+ find $(TEMP_CD_TREE) -newermt "$(SOURCE_DATE)" -print0 \
+ | xargs -0r touch --no-dereference --date="$(SOURCE_DATE)"
+
if [ "$(GRUB_EFI)" = y ]; then \
xorriso -as mkisofs -r -J -b isolinux.bin -c boot.cat \
-no-emul-boot -boot-load-size 4 -boot-info-table \
diff --git a/debian/changelog b/debian/changelog
index 42aed37..09c8a02 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,21 @@
+debian-installer (20150422+kbsd8u2) jessie-kfreebsd; urgency=medium
+
+ * Improve reproducibility of debian-installer netboot images:
+(Closes: #805321)
+- clamp timestamps in the d-i ramdisk to be no later than
+ the most recent debian/changelog entry of this package
+ - raise makefs dependency on >= 20100306-5+kbsd8u1
+- clamp timestamps in the mini.iso similarly
+- clamp timestamps in the netboot tarball; store files in a
+ stable order
+- clamp timestamps in the cd info tarball; store files in a
+ stable order
+- clamp timestamps in the output debian-installer-images tarball;
+ store files in a stable order
+- disable timestamps in gzip output (e.g. initrd.gz and tarballs)
+
+ -- Steven Chamberlain Tue, 10 Nov 2015 21:38:46 +
+
debian-installer (20150422+kbsd8u1) jessie-kfreebsd; urgency=medium
* Rebuild using udebs from the jessie-kfreebsd suite, also using
diff --git a/debian/control b/debian/control
index 100ca5a..6f4df5b 100644
--- a/debian/control
+++ b/debian/control
@@ -162,7 +162,7 @@ Build-Depends:
# architectures if SSL_CERTS has been set locally.
win32-loader (>= 0.7.2) [i386 amd64 kfreebsd-i386 kfreebsd-amd64 hurd-i386],
# Alternative boot method
Bug#805321: debian-installer: builds unreproducible netboot images
(Keeping everyone initially x-d-cc'd in the loop.) Hi, Steven Chamberlain (2015-11-16): > Package: debian-installer > Version: 20150422 > Severity: wishlist > Tags: patch Where's the patch? :p > The debian-installer package build produces netboot.tar.gz and > the mini.iso netboot install media. It doesn't do this in an easily > reproducible way: > > * the d-i initrd/mfsroot is a filesystem image, having variable > mtime/ctime/atime timestamps from package build time; > * likewise in the generated mini.iso; > * netboot.tar.gz also has varying timestamps; the order of files > may also vary depending on the filesystem; > * likewise in the cd info tarball; > * likewise in the debian-installer-images tarball; > * all gzipped outfile files have a timestamp in the header. > > I have a patch aimed at jessie-kfreebsd that should fix all of the > above. It should be possible to do the same in sid with much less > code, due to new GNU tar features and other reproducible builds work. Please make sure not to depend on features which are not found in stable (I'm not entirely sure about oldstable at this point), which might hinder our ability to cherry-pick bits and pieces from master to jessie. I know this might sound a bit silly since you're talking about targetting jessie-kfreebsd anyway, but I'd like to point that out anyway, just in case someone wants to rework/“simplify” your work later on. > I've 'clamped' timestamps to be no later than the most recent > debian/changelog entry date. That way, the non-useful timestamps > from during the build are adjusted to a constant value. Older > timestamps, actually indicating how old a file is, are untouched. > The BUILD_DATE, actually the package version number, is unchanged. > > Specifically on kfreebsd, the generated mfsroot is a ffs filesystem > having file atimes, and another timestamp in the filesystem superblock. > I intend to patch makefs so that it can clamp timestamps to a given > SOURCE_DATE_EPOCH. > > Besides a file ordering issue in makefs, all output files including > netboot.tar.gz and mini.iso then seem to be reproducible for > jessie-kfreebsd, at least. :) I don't have much knowledge in this area (or time to investigate right away), so I'll probably let reproducible people comment on this once they see your patch. Mraw, KiBi. signature.asc Description: Digital signature
partman-zfs_45+kbsd8u2_source.changes ACCEPTED into stable-kfreebsd-proposed-updates
Mapping jessie-kfreebsd to stable-kfreebsd. Mapping stable-kfreebsd to stable-kfreebsd-proposed-updates. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Nov 2015 22:02:40 + Source: partman-zfs Binary: partman-zfs Architecture: source Version: 45+kbsd8u2 Distribution: jessie-kfreebsd Urgency: medium Maintainer: Debian Install System Team Changed-By: Steven Chamberlain Description: partman-zfs - Add to partman support for ZFS (udeb) Changes: partman-zfs (45+kbsd8u2) jessie-kfreebsd; urgency=medium . * In a user-provided volume size, ignore any spaces, or "i" as in MiB, GiB, etc. to prevent a syntax error. * Allow more reserved space, to avoid suggesting a volume size too large to actually be created. Checksums-Sha1: 0a5580056efd89ce890d9488301edec9e1240096 1377 partman-zfs_45+kbsd8u2.dsc e1e243e8afee3d2991f4b6c1f1225dc5f3ea786a 260204 partman-zfs_45+kbsd8u2.tar.xz Checksums-Sha256: db972cf907f48ce6b5bf3180a2eeeaf17ba9ba36ecb6f43c33e9ad62f308f2f4 1377 partman-zfs_45+kbsd8u2.dsc e72cb5d4dfde4359f689b7b2b4b3d00cdd6d1a7b7aaa78273288c74dd29dd89c 260204 partman-zfs_45+kbsd8u2.tar.xz Files: 4ad0ed087fbb21170a66637a7ae37e8d 1377 debian-installer standard partman-zfs_45+kbsd8u2.dsc d248cb1b465ab3fbd42e450d355bee75 260204 debian-installer standard partman-zfs_45+kbsd8u2.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJWSmSyAAoJELrpzbaMAu5Tl6kH/AxWjDlHsFO0zZ+OCD1ydxsB 3tZOBD00dHfYC3fBKCNSn7j/gRIvHTG+1UhZEzcnflFNM2j9GVh2IN8ud2eRukuu sEa3E0HG2yucJ8z9bmo9zLGAlEYo5cGPVBUJ8mygYqHk9ghag/A05L7epSdT8knG vTg9mMl19xLKKXjBsmJIzppVhilM/08Z2awwRuPd91GQkGw13xawSBTV3LJSv6QE cnBfZPqs25d8QooOTpW3sV0Xz8Pz/ySsE0boA2S4qJ74bWzgQJEHux5siqWIKQ8N oYuYtG2RaY2CDczixtRGzOhIYIWm2ZcahDUVqM3NGqLZeykymxYHbM7Ee/rYK40= =/O0x -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#805321: debian-installer: builds unreproducible netboot images
Hi,
Steven Chamberlain (2015-11-17):
> Attached is my jessie-kfreebsd implementation. As I said, it should be
> much cleaner to implement this in sid with newer GNU tar.
>
> Regards,
> --
> Steven Chamberlain
> ste...@pyro.eu.org
> diff --git a/build/Makefile b/build/Makefile
> index ec5a084..6261a4d 100644
> --- a/build/Makefile
> +++ b/build/Makefile
> @@ -56,7 +56,7 @@
> # Add to PATH so dpkg will always work, and so local programs will be found.
> PATH := util:$(PATH):/usr/sbin:/sbin
> EATMYDATA = $(shell which eatmydata 2>/dev/null)
> -GZIP = $(shell which pigz gzip | head -1)
> +GZIP = $(shell which pigz gzip | head -1) -n
I think I already added -n to a bunch of calls. Not sure whether adding
it here once and for all would be better than adding it where it's
missing though. Anyway, not my biggest question/comment/concern here.
> # We don't want this to be run each time we re-enter.
> ifndef DEB_HOST_ARCH
> @@ -149,7 +149,7 @@ MFSROOT_LIMIT := 68m
> endif
>
> define mkfs.ufs1
> - sh -c 'makefs -t ffs -s $(MFSROOT_LIMIT) -f 3000 -o minfree=0,version=1
> $$0 ${TREE}'
> + sh -c 'makefs -t ffs -T $(SOURCE_DATE_EPOCH) -s $(MFSROOT_LIMIT) -f 3000
> -o minfree=0,version=1 $$0 ${TREE}'
Straightforward enough.
> define e2fsck
> @@ -803,7 +803,14 @@ $(TEMP_MINIISO): $(TEMP_BOOT_SCREENS) arch_miniiso
>
> # various kinds of information, for use on debian-cd isos
> $(DEBIAN_CD_INFO): $(TEMP_BOOT_SCREENS) $(TEMP_CD_INFO_DIR)
> - (cd $(TEMP_CD_INFO_DIR); tar czf - .) > $@
> + # Clamp timestamps to be no newer than last changelog entry, see
> + # https://wiki.debian.org/ReproducibleBuilds/TimestampsInTarball
> + find $(TEMP_CD_INFO_DIR) -newermt "@$(SOURCE_DATE_EPOCH)" -print0 |
> xargs -0r touch --no-dereference --date="@$(SOURCE_DATE_EPOCH)"
> + # Create tarball with files sorted in a stable order, see
> + # https://wiki.debian.org/ReproducibleBuilds/FileOrderInTarballs
> + # and without timestamp in the gzip header, see
> + # https://wiki.debian.org/ReproducibleBuilds/TimestampsInGzipHeaders
> + ( cd $(TEMP_CD_INFO_DIR) && find . -print0 | LC_ALL=C sort -z | GZIP=-n
> tar --no-recursion --null -T - -czf -) > $@
> update-manifest $@ $(MANIFEST-DEBIAN_CD_INFO)
Once.
> # a directory full of files for netbooting
> @@ -822,7 +829,14 @@ $(NETBOOT_TAR): $(TEMP_NETBOOT_DIR)
> # Create an version info file.
> echo 'Debian version: $(DEBIAN_VERSION)' >
> $(TEMP_NETBOOT_DIR)/version.info
> echo 'Installer build: $(BUILD_DATE)' >>
> $(TEMP_NETBOOT_DIR)/version.info
> - (cd $(TEMP_NETBOOT_DIR); tar czf - .) > $@
> + # Clamp timestamps to be no newer than last changelog entry, see
> + # https://wiki.debian.org/ReproducibleBuilds/TimestampsInTarball
> + find $(TEMP_NETBOOT_DIR) -newermt "@$(SOURCE_DATE_EPOCH)" -print0 |
> xargs -0r touch --no-dereference --date="@$(SOURCE_DATE_EPOCH)"
> + # Create tarball with files sorted in a stable order, see
> + # https://wiki.debian.org/ReproducibleBuilds/FileOrderInTarballs
> + # and without timestamp in the gzip header, see
> + # https://wiki.debian.org/ReproducibleBuilds/TimestampsInGzipHeaders
> + ( cd $(TEMP_NETBOOT_DIR) && find . -print0 | LC_ALL=C sort -z | GZIP=-n
> tar --no-recursion --null -T - -czf -) > $@
Twice.
> update-manifest $@ $(MANIFEST-NETBOOT_TAR) $(UDEB_LISTS)
>
> $(TEMP_BOOT_SCREENS): arch_boot_screens
> diff --git a/build/config/x86.cfg b/build/config/x86.cfg
> index 3caadd2..b0fc9a2 100644
> --- a/build/config/x86.cfg
> +++ b/build/config/x86.cfg
> @@ -332,6 +332,11 @@ arch_miniiso: x86_syslinux x86_grub_efi
> | todos > $(TEMP_CD_TREE)/win32-loader.ini; \
> fi
>
> + # Clamp timestamps to be no newer than last changelog entry, see
> + # https://wiki.debian.org/ReproducibleBuilds/TimestampsInTarball
> + find $(TEMP_CD_TREE) -newermt "$(SOURCE_DATE)" -print0 \
> + | xargs -0r touch --no-dereference --date="$(SOURCE_DATE)"
> +
Refraining from writing “almost thrice”. [XXX]
> if [ "$(GRUB_EFI)" = y ]; then \
> xorriso -as mkisofs -r -J -b isolinux.bin -c boot.cat \
> -no-emul-boot -boot-load-size 4 -boot-info-table \
> diff --git a/debian/changelog b/debian/changelog
> index 42aed37..09c8a02 100644
> --- a/debian/changelog
> +++ b/debian/changelog
> @@ -1,3 +1,21 @@
> +debian-installer (20150422+kbsd8u2) jessie-kfreebsd; urgency=medium
> +
> + * Improve reproducibility of debian-installer netboot images:
> +(Closes: #805321)
> +- clamp timestamps in the d-i ramdisk to be no later than
> + the most recent debian/changelog entry of this package
> + - raise makefs dependency on >= 20100306-5+kbsd8u1
> +- clamp timestamps in the mini.iso similarly
> +- clamp timestamps in the netboot tarball; store files in a
> + stable order
> +- clamp timestamps in the cd info tarball; store files in a
> + stable o
Bug#805321: debian-installer: builds unreproducible netboot images
Hi KiBi, Many thanks for reviewing this. Cyril Brulebois wrote: > Please make sure not to depend on features which are not found in stable > (I'm not entirely sure about oldstable at this point), which might hinder > our ability to cherry-pick bits and pieces from master to jessie. I think I could make that easier by splitting into smaller commits: * parts only needed for kfreebsd * parts more appropriate for stable, oldstable, etc. * parts only appropriate for sid (or just not use new GNU tar features yet) > > --- a/build/Makefile > > +++ b/build/Makefile > > @@ -56,7 +56,7 @@ > > # Add to PATH so dpkg will always work, and so local programs will be > > found. > > PATH := util:$(PATH):/usr/sbin:/sbin > > EATMYDATA = $(shell which eatmydata 2>/dev/null) > > -GZIP = $(shell which pigz gzip | head -1) > > +GZIP = $(shell which pigz gzip | head -1) -n > > I think I already added -n to a bunch of calls. Not sure whether adding > it here once and for all would be better than adding it where it's > missing though. Anyway, not my biggest question/comment/concern here. Seems reasonable to factor out and put it here. If we don't, someone may add a new $GZIP call later, forget -n and make it unreproducible again. Although it is a macro here, GZIP is also the name of an environment variable used by gzip (but not pigz?), which is likely confusing. And the later tar invocations call gzip (not pigz) in quite a few places regardless of the GZIP macro contents; those do look at the GZIP environment variable though. > I think those 3(.5) occurrences really should be factorized, especially > given the logic is the same: replacing "cd foo && tar bar ." with more > code. Somewhere under build/util would probably be suitable. I agree. It is a very common pattern in other Debian packages too, and it often needs patching for reproducibility. > > --- a/build/config/x86.cfg > > +++ b/build/config/x86.cfg > > @@ -332,6 +332,11 @@ arch_miniiso: x86_syslinux x86_grub_efi > > | todos > $(TEMP_CD_TREE)/win32-loader.ini; \ > > fi > > > > + # Clamp timestamps to be no newer than last changelog entry, see > > + # https://wiki.debian.org/ReproducibleBuilds/TimestampsInTarball > > + find $(TEMP_CD_TREE) -newermt "$(SOURCE_DATE)" -print0 \ > > +| xargs -0r touch --no-dereference --date="$(SOURCE_DATE)" > > + > [...] above is using SOURCE_DATE, which is undefined as > far as I can tell since SOURCE_DATE_EPOCH is what's getting defined. > Maybe it should call the same new util (with different parameters since > we only need touch here, and no tar call)? That's a typo, and was buggy - it would touch all timestamps, not just the ones necessary. I may drop this part as I don't think it's needed any more with the newer makefs, which will clamp the timestamps itself. > Finally, not everything is built using debian/rules targets (with or > without dpkg-buildpackage). One should still be able to just run e.g.: > “make -C build build_netboot-gtk USE_UDEBS_FROM=sid” > > See BUILD_DATE handling, for example. We end up with a default setting > through: > |build/config/common:BUILD_DATE ?= $(shell date -u '+%Y%m%d-%H:%M') That would not be reproducible, then! (it is embedded in the tarballs) > [ Please note that calling $(shell dpkg-parsechangelog -SDate) to set > SOURCE_DATE_EPOCH there would only work when building from the toplevel > directory, and not from the build/ subdirectory for example. ] If it's anyway not going to be reproducible, we could similarly fall back to a SOURCE_DATE_EPOCH ?= now; or the caller could choose to provide them. Regards, -- Steven Chamberlain ste...@pyro.eu.org signature.asc Description: Digital signature
Bug#805321: debian-installer: builds unreproducible netboot images
(Trimming a lot because running out of time.) Steven Chamberlain (2015-11-17): > Seems reasonable to factor out and put it here. If we don't, someone > may add a new $GZIP call later, forget -n and make it unreproducible > again. > > Although it is a macro here, GZIP is also the name of an environment > variable used by gzip (but not pigz?), which is likely confusing. And > the later tar invocations call gzip (not pigz) in quite a few places > regardless of the GZIP macro contents; those do look at the GZIP > environment variable though. Feel free to rename stuff as needed. > > Finally, not everything is built using debian/rules targets (with or > > without dpkg-buildpackage). One should still be able to just run e.g.: > > “make -C build build_netboot-gtk USE_UDEBS_FROM=sid” > > > > See BUILD_DATE handling, for example. We end up with a default setting > > through: > > |build/config/common:BUILD_DATE ?= $(shell date -u '+%Y%m%d-%H:%M') > > That would not be reproducible, then! (it is embedded in the tarballs) Sure. I just meant to point out that even if BUILD_DATE is set through debian/rules, a default value is set for users not building through debian/rules, meaning BUILD_DATE gets set in the end, instead of just being empty. > > [ Please note that calling $(shell dpkg-parsechangelog -SDate) to set > > SOURCE_DATE_EPOCH there would only work when building from the toplevel > > directory, and not from the build/ subdirectory for example. ] > > If it's anyway not going to be reproducible, we could similarly fall > back to a SOURCE_DATE_EPOCH ?= now; or the caller could choose to > provide them. Mraw, KiBi. signature.asc Description: Digital signature
Bug#805342: Stretch Alpha 4 Installation Report (failed)
Package: installation-reports Boot method: USB Stick Image version: http://cdimage.debian.org/cdimage/stretch_di_alpha4/amd64/iso-dvd/debian-stretch-DI-alpha4-amd64-DVD-1.iso Date: 11/16/2015 Machine: Dell XPS 13 (late 2015) with WiFi/Bluetooth card change from stock to an Intel 7265. Processor: Core i5-6200U (Skylake) Memory:8 gigs Partitions: irrelevant Irrelevant Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[E] Configure network: [E] Detect CD: [E] I didn't get any further than this as this part of the installer has a catastrophic failure. Comments/Problems: FWIW, the Jessie installer does okay but the Stretch Installer has problems. Starting off, the install halts when it gets to the network hardware. I have installed an Intel 7265. The Stretch installer says that the firmware is missing (this was not a problem with Ubuntu which instantly saw the network hardware and completed the installation without a hitch, never asking for me to provide drivers for anything). The installer says: "Some of your hardware needs non-free firmware files to operate. The firmware can be loaded from removable media, such as a USB stick or floppy. The missing firmware files are: iwlwifi-7265D-15.ucode, iwlwifi-7265D-14.ucode, iwlwifi-7265D-13.ucode, iwlwifi-7265D-12.ucode, iwlwifi-7265D-11.ucode, iwlwifi-7265D-10.ucode." The first problem is that it does not see the USB stick when you insert it. You have to press control-function-alt-F2 (which is indicated nowhere) to get to a command prompt and then mount the usb stick to cdrom (again this information is presented nowhere). Once manually mounted you have to press control-function-alt-F5 to get back to the installer at which point it still doesn't doesn't see the firmware. Part of the problem is that 7265D-11.ucode never has existed anywhere, in any package, ever Also, this is the wrong firmware. The correct firmware is iwlwifi-7265-8.ucode and iwlwifi-7265-9.ucode (note the lack of a 'D' after 7265). If after failing to install the network hardware, you put the install USB stick back in, and tell the installed "NO", I do not want to load the drivers at this time and you hit return, the installer fails (gets caught in an indefinite hang. The only way to get out of it is to cold power cycle the machine.
Re: More cdebconf improvements
Quoting Regis Boudin (re...@boudin.name):
> > Anyway, as you said, besides translations, patches look small enough to
> > be easily debugged (or worst case reverted) if needed, so I'm fine with
> > getting the whole lot uploaded whenever someone feels like being
> > responsible for what happens next. ;)
>
> Well, I can't upload at the moment, so I'll pass on the offer. Also, we
> might want to wait a couple of days to get the new text translated in a
> few languages ?
Translations will naturally flow in as sonn as the changes are
committed to git, whether the package is uploaded or not.
Anyway, once the changes are there, and assuming the package is
uplaoded quickly (which I think is the best), other uploads will
happen from time to time when "enough" translation updates have piled
up ("enough" is a number that depends on my state of mind, mostly).
So, in short, don't worry about l10n, there is plenty of time for
updates.
signature.asc
Description: PGP signature
