Bug#778194: missing patch

2015-04-03 Thread Adam Borowski
Oif, the patch wasn't actually attached.  Sending it now.
>From 75a5da43aef805be81c08a69bd8986d9dbe60a4a Mon Sep 17 00:00:00 2001
From: Adam Borowski 
Date: Sat, 4 Apr 2015 03:12:34 +0200
Subject: [PATCH] Add x32/efi recipe, as a symlink to amd64/efi.

---
 recipes-x32-efi | 1 +
 1 file changed, 1 insertion(+)
 create mode 12 recipes-x32-efi

diff --git a/recipes-x32-efi b/recipes-x32-efi
new file mode 12
index 000..d383b93
--- /dev/null
+++ b/recipes-x32-efi
@@ -0,0 +1 @@
+recipes-amd64-efi
\ No newline at end of file
-- 
2.1.4



consistency check of sources of udebs

2015-04-03 Thread Cyril Brulebois
Hi people,

there's a handy “consistency check of sources of udebs” link on [1]
which leads to [2].

 1. http://d-i.debian.org/testing-summary.html
 2. https://ftp-master.debian.org/d-i

The contents on the latter seems fishy to me, let's take this example:
| udeb's in unstable that should be in testing too:
|package|   version|  arch  |
| source  
| 
--+--++-
|  beep-udeb| 1.3-3| arm64  | beep
|  beep-udeb| 1.3-3| ppc64el| beep

while we have:
| kibi@arya:~$ rmadison beep-udeb -s testing,unstable
| beep-udeb  | 1.3-3 | testing| arm64, ppc64el
| beep-udeb  | 1.3-3 | unstable   | arm64, ppc64el
| beep-udeb  | 1.3-3+b1  | testing| amd64, armel, armhf, i386, mips, 
mipsel, powerpc, s390x
| beep-udeb  | 1.3-3+b1  | unstable   | amd64, armel, armhf, i386, mips, 
mipsel, powerpc, s390x, sparc

There's a bunch of arm64/ppc64el pairs, which would make it look like
there might be something around the addition of those archs. But there's
also the case of libxdmcp6-udeb which is mentioned for more or less all
archs (some bit of sorting wouldn't hurt BTW ;)).

Can you please check what's happening there?

Mraw,
KiBi.


signature.asc
Description: Digital signature


Re: Bug#746967: buildd.debian.org: d-i daily builds happen with unsigned code from alioth

2015-04-03 Thread Cyril Brulebois
(Catching up with a number of mails on debian-boot@…)

Aurelien Jarno  (2015-03-18):
> With the help of Hector Oron, we have been able to setup this on the
> porterbox of 4 architectures: arm64, armel, armhf and mips. This has
> been done by allowing the d-i role account on the porterboxes. As a
> nice side effect, this mean that d-i people can now do/fix the setup
> themselves without having to go through the buildd team. The code used
> is available in the porterbox branch of the di-autobuild git.

Thank you so much for that!

There wasn't a need for fixing the setup yet, but that's a very thing to
have.

> Note that the chroots on the porterbox are created in a very similar
> way than on the newer buildds (it's even done by the same script
> IIRC), so the problems should be similar. For example both were
> affected by bug#775136.

Having build environments as close as possible to the ones actually used
on buildds is great: this should ensure the amount of last minute
surprises is kept at a minimum.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Processed: tagging 780545

2015-04-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> # no need for a d-i tag for os-prober; and no need for dist tags either given 
> the version tracking feature of the bts
> tags 780545 - d-i jessie sid
Bug #780545 [os-prober] os-prober looping with formated partitions without OS
Removed tag(s) sid, d-i, and jessie.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/handler.s.c.1428099759782.transcr...@bugs.debian.org



Re: missing syslinux labels/targets in help/text screen?

2015-04-03 Thread Václav Ovsík
On Fri, Apr 03, 2015 at 09:55:55PM +0200, Cyril Brulebois wrote:
> Václav Ovsík  (2015-03-18):
> > I have a PXE booting configured with Debian installer for testing/jessie
> > too. I noticed, that on help screen is only available label "menu".
> > Labels "install" and "expert" are missing. I need also the text-only
> > startup screen, because of DRAC SOL installations.
> > 
> > I think this change is source of the problem:
> > https://anonscm.debian.org/cgit/d-i/debian-installer.git/commit/build/boot/x86/prompt.cfg?id=1e9968331c7938461a52d8d8ed7bd6f4431fb40b
> 
> Hi,
> 
> I can't look into it right now, but please open a bug report against the
> debian-installer package (version 20141002 would be a good guess if said
> commit is indeed responsible), so that it can be tracked properly.

OK, I did it
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781853
Cheers
-- 
Zito


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150403215435.GA5494@bobek.localdomain



Re: Bug#774358: libxml2: CVE-2014-3660 patch makes installation-guide FTBFS

2015-04-03 Thread Cyril Brulebois
Hi people,

(adding debian-boot@ for reference.)

Samuel Thibault  (2015-03-26):
> Samuel Thibault, le Thu 26 Mar 2015 02:17:01 +0100, a écrit :
> > Control: found -1 2.8.0+dfsg1-7+wheezy3
> > 
> > This is still an issue in stable, the proposed patch was not applied
> > there, and thus installation-guide still FTBFS on wheezy, notably on our
> > dillon.debian.org machine, thus making http://d-i.debian.org/manual/
> > completely out of date. Could this be proposed for stable update?
> > 
> > I have attached the proposed patch again.
> 
> Just to insist: while the symptoms of my report (#774358) may look like
> #768089, the *actual* bug is *not* the same. Please read my bug report
> and the proposed patch again: the issue is that the security fix for
> CVE-2014-3660 from a newer version of libxml2 (2.9.x) was backported
> into the libxml2 of wheezy (2.8.x) without noticing the subtle source
> code difference which does matter a lot.

As one of the guys receiving a notification of the FTBFS every time
the crontab entry is triggered, and who would like to make sure the
installation guide is actually buildable *and* up-to-date, I really
would like to get a fix for this regression ASAP. It's been more than
3 months since this bug report about ***stable being broken*** has
been opened.

Thanks already.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Re: Status of D-I translations...

2015-04-03 Thread Cyril Brulebois
Hi,

Christian PERRIER  (2015-03-05):
> No, no call for translations.
> 
> I actually rely on translators who want D-I to be fully translated
> to follow its status through the status pages
> (http://d-i.debian.org/l10n-stats/)
> 
> It means that we're indeed left with about only 10 languages that
> happen to be complete -> those where translators act on their own
> and know what to do to get a fully translated D-I.
> 
> For others, most of the time, the registered person with commit
> access either vanished or doesn't care anymore for D-I to be fully
> translated.
> 
> The main "problem" here is that, each time such call for translation
> is posted for D-I, I end up with dozens of mails basically all
> requesting "what should I do for my XXX language to be complete?". I
> then explain all things that are explained in D-I l10n
> documentation, hold the hands of the prospective person, get the
> updates and then.the person vanishes until the next update.
> 
> That's a bit tiring and demotivating when one has much less time for
> all these activities than I had in the past (other activities and
> passions have taken over the Debian work as many know).

Christian, I cannot emphasize enough how much your work and your
commitment around i18n and l10n has been inspirational to me. After
all, as a number of other DDs, I started contributing to Debian
through translation updates. Thanks so much for your work in this
area over this incredible amount of years!


(Wording shamelessly stolen from debian-vote@ and wannabe DPLs) It
seems to me that the problem is two-fold: (1) Finding new
translators and holding their hands for a while; and (2) issuing
calls for translations to make sure those are aware of needed work.

At first glance, it looks to me trying to find new blood on local
user lists (debian-user-* and debian-l10n-* where they exist) might
be an interesting way to spend a few minutes on the topic. It would
be great if we could find someone wanting to give it a shot, and who
might be ready to orientate towards the relevant doc/people since
that's probably going to be needed. Since we're currently in a kind
of slowed down phase, having people catch up would be nice; we can
then switch to trying and keeping the translations updated when
needed, looking into how to issue call for translations in the best
way to keep people willing to stay at 100%. ;)


Who wants to be known as the new d-i translation coordinator? Who
wants to be thanked in each and every of my talks? :)

Mraw,
KiBi.


signature.asc
Description: Digital signature


Bug#781853: debian-installer: not available options install & menu from help screen

2015-04-03 Thread Vaclav Ovsik
Package: debian-installer
Version: 20141002
Severity: normal
Tags: d-i

Dear Maintainer,
I have a PXE booting configured with Debian installer for testing/jessie
too. I noticed, that on help screen is only available label "menu".
Labels "install" and "expert" are missing. I need also the text-only
startup screen, because of DRAC SOL installations.

I think this change is source of the problem:
https://anonscm.debian.org/cgit/d-i/debian-installer.git/commit/build/boot/x86/prompt.cfg?id=1e9968331c7938461a52d8d8ed7bd6f4431fb40b

Reverting this change (inclusion of menu.cfg) brings install and expert back.
Cheers
-- 
Zito

-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armel

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150403203512.11356.82107.reportbug@bobek.localdomain



Bug#779922: marked as done (debian-installer: Installation freezes with "The attempt to mount a files system with type ext4 in SCSI1 (0, 0, 0), partition #1 (sda) at / failed.")

2015-04-03 Thread Debian Bug Tracking System
Your message dated Fri, 3 Apr 2015 22:07:46 +0200
with message-id <20150403200746.gw13...@mraw.org>
and subject line Re: Bug#779922: Quickfix for USB-stick?
has caused the Debian Bug report #779922,
regarding debian-installer: Installation freezes with "The attempt to mount a 
files system with type ext4 in SCSI1 (0, 0, 0), partition #1 (sda) at / failed."
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
779922: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779922
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Severity: critical
Tags: d-i
Justification: breaks the whole system

Dear Maintainer,

I take debian testing weekly build from
http://cdimage.debian.org/cdimage/weekly-builds/i386/jigdo-dvd/debian-testing-i386-DVD-1.jigdo,
add preseed to it and install in qemu.
Preseed contains this:

d-i partman-auto/method string regular
d-i partman-auto/choose_recipe select atomic
d-i partman-partitioning/confirm_write_new_label boolean true
d-i partman/confirm_nooverwrite boolean true
d-i partman/choose_partition select finish
d-i partman/confirm boolean true

Qemu image is created as:

qemu-img create -f qcow2 newcd-qemu.qcow2 10G

Previous debian testing builds caused no problem with the same setup (I test 
each week).

Problem arised with latest debian testing build (from 02.03.2015).

Installation freezes with the following error ("Partition disks" stage):

The attempt to mount a files system with type ext4 in SCSI1 (0,0,0), partition 
#1 (sda) at / failed.

You may resume partitioning from the partitioning menu.
Do you want to resume partitioning?
- No
- Yes

Relevant parts of installer log from qemu follow:


main-menu INFO: Menu item 'disk-detect' selected
kernel: sda: unknown partition table
main-menu: INFO: Menu item 'partman-base' selected
anna-install: Installing partman-auto-lvm
anna: DEBUG: retrieving crc-modules-3.16.0-4-586-di 3.16.7-ckt7-1
anna: DEBUG: retrieving lvm2-udeb 2.02.111-2
anna: DEBUG: retrieving partman-auto-lvm 56
anna: DEBUG: retrieving partman-lvm 105
anna-install: Installing partman-auto-crypto
anna: DEBUG: retrieving partman-auto-crypto 22
anna: DEBUG: retrieving partman-crypto 78
kernel: ext4: Unknown symbol pagecache_get_page_fixed (err 0)
kernel: raid6: mmxx158 MB/s
kernel: raid6: mmxx276 MB/s
kernel: raid6: sse1x1   70 MB/s
kernel: raid6: sse1x2   78 MB/s
kernel: raid6: sse2x1   157 MB/s
kernel: raid6: sse2x2   123 MB/s
kernel: raid6: using algorithm sse2x1 (157 MB/s)
kernel: raid6: using intx1 recovery algorithm
kernel: xor: measuring software checksum speed
kernel: pIII_sse : 430.000 MB/sec
kernel: prefetch64-sse: 429.000 MB/sec
kernel: xor: using function: pIII_sse (430.000 MB/sec)
kernel: btrfs: Unknown symbol pagecache_get_page_fixed (err 0)
kernel: ext4: Unknown symbol pagecache_get_page_fixed (err 0)
kernel: ext4: Unknown symbol pagecache_get_page_fixed (err 0)
kernel: jfs: Unknown symbol pagecache_get_page_fixed (err 0)
kernel: SGI XFS with ACLs, security attributes, realtime, large block/inode 
numbers, no debug enabled
md-devices: mdadm: No arrays found in config file or automatically
kernel: device-mapper: uevent: version 1.0.3
kernel: device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: 
dm-de...@redhat.com
partman: No matching physical volumes found
partman: Reading all physical volumes. This may take a while...
partman: No volume groups found
partman-lvm: No volume groups found
kernel: sda: unknown partition table
kernel: sda: unknown partition table
kernel: sda: unknown partition table
kernel: sda: sda1 sda2 < sda5 >
kernel: Adding 477189k swap on /dev/sda5. Priority:-1 extents:1 across:477189k 
FS
partman: mke2fs 1.42.12 (29-Aug-2014)
kernel: ext4: Unknown symbol pagecache_get_page_fixed (err 0)

-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 20150324

Pavlos Parissis  (2015-03-16):
> I just ran into this issue as well using latest
> debian-testing-amd64-DVD-1.iso.
> 
> Does anyone know how I can follow Hans's workaround using USB-stick
> installation?

Hello everybody,

the D-I Jessie RC2 release (based on the 20150324 release of the
debian-installer package) makes this issue moot, so closing this bug
report; also letting downstream bug report & Vag

Bug#780545: os-prober looping with formated partitions without OS

2015-04-03 Thread Cyril Brulebois
Hi,

Joao Eriberto Mota Filho  (2015-03-15):
> Package: os-prober
> Version: 1.65
> Severity: important
> Tags: d-i
> 
> Dear Maintainer,
> 
> When installing the Jessie (netinst, amd64, 20150315) or updating GRUB in my
> Dell Vostro 5470, the os-prober is looping if there are formated partitions
> without an installed operational system.
> 
> I have two extra empty partitions with ReiserFS and vfat:
> 
> --- /dev/sda3
> Block device, size 596 MiB (624951296 bytes)
> ReiserFS file system (new 3.6 format, standard journal, starts at 64 KiB)
>   UUID 1D55E629-8E1D-452C-AFA2-23D45AF1DA04 (DCE, v4)
>   Volume size 596 MiB (624951296 bytes, 152576 blocks of 4 KiB)
> 
> --- /dev/sda4
> Block device, size 461 MiB (483393536 bytes)
> FAT32 file system (hints score 5 of 5)
>   Volume size 460.1 MiB (482430976 bytes, 117781 clusters of 4 KiB)

I should note that at least ReiserFS is no longer supported, see:
| os-prober (1.63) unstable; urgency=low
| 
|   [ Cyril Brulebois ]
|   * Drop reiserfs, it's no longer supported.
| 
|  -- Christian Perrier   Tue, 23 Jul 2013 09:38:17 +0200

so maybe there's something fishy with filesystems whose support has been
dropped. The “tr” call seems indeed strange to my candid eye.

I'll add that to my to do list, but it's unlikely to be addressed for
RC3 / the first jessie release unless somebody steps in and debugs this
further in the upcoming days.

 
Mraw,
KiBi.


signature.asc
Description: Digital signature


Re: missing syslinux labels/targets in help/text screen?

2015-04-03 Thread Cyril Brulebois
Václav Ovsík  (2015-03-18):
> I have a PXE booting configured with Debian installer for testing/jessie
> too. I noticed, that on help screen is only available label "menu".
> Labels "install" and "expert" are missing. I need also the text-only
> startup screen, because of DRAC SOL installations.
> 
> I think this change is source of the problem:
> https://anonscm.debian.org/cgit/d-i/debian-installer.git/commit/build/boot/x86/prompt.cfg?id=1e9968331c7938461a52d8d8ed7bd6f4431fb40b

Hi,

I can't look into it right now, but please open a bug report against the
debian-installer package (version 20141002 would be a good guess if said
commit is indeed responsible), so that it can be tracked properly.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Bug#768188: Annoying bug

2015-04-03 Thread Cyril Brulebois
Control: found -1 1.120

Martin Stigge  (2015-03-16):
> Thanks for already reporting at finding out about the details of this
> bug. I just encountered the bug during an install with d-i rc1. Without
> finding this bug report and knowing how to navigate the ecosystem to
> find and kill the right process, the situation would have been
> impossible to resolve. 
> 
> This really needs to be fixed before release.

Just a quick line:

Well, chasing and poking happened; it's been errata'd for RC2, and the
fix has now reached jessie, so RC3 should have the fix.

Since the bug graph can lead one to believe this affects wheezy as well,
I'm marking it as found in 1.120, which is the first release to contain:
| commit 48f1de7076f8d17a9bf4d11cb05968cb9d8987f7
| Author: Steven Chamberlain 
| Date:   Fri Sep 5 02:35:28 2014 +0100
| 
| Don't kill_dhcp_client without reason (Closes: #757711, #757988)
| 
| Do not kill_dhcp_client after setting the hostname and domain,
| otherwise Linux udhcpc will stop renewing its lease, and on other
| platforms dhclient will de-configure the network interface
| (Closes: #757711, #757988)

Mraw,
KiBi.


signature.asc
Description: Digital signature


Processed: Re: Bug#768188: Annoying bug

2015-04-03 Thread Debian Bug Tracking System
Processing control commands:

> found -1 1.120
Bug #768188 {Done: Philipp Kern } [netcfg] Jessie Installer 
hangs after processing DHCPv6 stateful addressing
Bug #773452 {Done: Philipp Kern } [netcfg] debian-installer: 
«netcfg» hang after the panel «domain», with ipv6 only
Marked as found in versions netcfg/1.120.
Marked as found in versions netcfg/1.120.

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


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/handler.s.b768188.14280901659769.transcr...@bugs.debian.org



Re: Status on and review/translation of the release-notes

2015-04-03 Thread Cyril Brulebois
Mathieu Parent  (2015-04-01):
> Hello,
> 
> > * Chapter 3: done
> 
> The installer section has seen no important changes since wheezy [1]
> and still indicate a migration from ext3 to ext4 for example [2].
> 
> A full rewrite is needed (cc-ing debian-boot).
> 
> Regards
> 
> 
> [1]: 
> https://anonscm.debian.org/viewvc/ddp/manuals/trunk/release-notes/en/installing.dbk?view=log
> [2]: 
> https://anonscm.debian.org/viewvc/ddp/manuals/trunk/release-notes/en/installing.dbk?revision=10511&view=markup#l223

That's the kind of things that should be mentioned in #780573 I guess.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Re: Debian Installer Jessie RC 2 release

2015-04-03 Thread Cyril Brulebois
Hi,

kongo sec  (2015-04-02):
> Thanks all for the help.
> I tried the installer and on a fresh install I tried apt-get install
> build-essentials i get this:
> 
> Thanks for any help.
> 
> 
> *# apt-get -f install build-essential*
> 
> *Reading package lists... Done*
> 
> *Building dependency tree*
> 
> *Reading state information... Done*
> 
> *Some packages could not be installed. This may mean that you have*
> 
> *requested an impossible situation or if you are using the unstable*
> 
> *distribution that some required packages have not yet been created*
> 
> *or been moved out of Incoming.*
> 
> *The following information may help to resolve the situation:*
> 
> 
> *The following packages have unmet dependencies:*
> 
> * build-essential : Depends: libc6-dev but it is not going to be installed
> or*
> 
> *libc-dev*
> 
> *   Depends: g++ (>= 4:4.9.1) but it is not going to be
> installed*

This seems rather strange to me, but I'd avise getting in touch with a user
support list, like debian-user@ (https://lists.debian.org/debian-user/)
since I doubt this has much to do with the installer or the installation
process.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Bug#780151: debian-installer: Buggy Built-Using generation on an arch-dep manner

2015-04-03 Thread Cyril Brulebois
Karsten Merker  (2015-03-30):
> I have run some further tests in the meantime. Those have shown
> that the effect happens on my local armhf build box when I build
> "by hand", but not when I use pbuilder.
> 
> The significant difference between both is that I have arch:all
> packages built by the syslinux source package (isolinux and
> syslinux-common) installed on my system, but not in the chroot
> used by pbuilder.  If I uninstall those arch:all packages, the
> effect does not occur anymore.  This means that building on a
> buildd will probably be safe for now, but if one architecture
> should in the future add a built-using for an arch-specific
> package, whose source also builds some arch:all package that is a
> build-dependency of the installer on another platform, the
> problem would probably crop up on the buildds as well.  With the
> current setup, I think the chance that this will actually happen
> in the forseeable future is rather low, but it would of course be
> better to find a "proper" solution for the issue.

OK, thanks for the extra checks.

Keeping this bug report open at important severity and bumping it to
serious whenever it becomes a practical issue looks like a reasonable
thing to do, so let's do that.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Re: CSS for installation guide ?

2015-04-03 Thread Stéphane Blondon
2015-04-03 21:19 GMT+02:00 Cyril Brulebois :
> Stéphane Blondon  (2015-04-03):
>> 2015-04-03 19:46 GMT+02:00 Karsten Merker :
>> > I have just stumbled over a missing png file on the index page
>> > of the installation guide:
>> >
>> > The heading of the section:
>> >
>> >   "Warning
>> >
>> >This installation guide is based on an earlier manual written
>> >for the old Debian installation system..."
>> >
>> > 
>> > > > alt="[Warning]" src="images/warning.png">
>> > Warning
>> > 
>> >
>> > points to a graphics file images/warning.png which does not exist.
>> >
>> > $ ls images/
>> > caution.png  home.png  important.png  next.png  note.png prev.png  up.png
>>
>> You can add the warning.png attached to this message in the same directory.
>> The provided picture comes from the same source than the other
>> pictures (Tango icon project). So the size and the style is the
>> equivalent to the other picture.
>>
>> Thank you for catching it, I didn't see the need of 'warning.png' file.
>
> Hello,
>
> I don't have the files handy, but caution.png & warning.png might be
> similar enough anyway? (As a non-native speaker I tend to consider both
> roughly equal. ;))


Yes, they are both an exclamation mark.
Like you, english is not my native tongue so I don't feel a difference
between caution and warning.

You can see a quick screenshot of the icons in attachment.


-- 
Stéphane


Re: translations for d-i manual [ Was: Re: Status of D-I translations... ]

2015-04-03 Thread Cyril Brulebois
Hi all,

and sorry for the lag in replying to this thread.

A quick word about Danish, re-enabled in:
 69659  sthibault daDanish

(according to svn blame debian/langlist).

Hendrik Boom  (2015-03-12):
> On Thu, Mar 12, 2015 at 08:48:47PM +0100, Holger Wansing wrote:
> > The situation for the d-i manual is similar: we have some languages,
> > that did not receive no or nearly no translation updates since the 
> > release of Wheezy. 
> > Should those languages be deactivated?
> > These are:  japanese (no update since 17 months)
> > russian (no update since 24 months)
> > swedish (no update since 2 years 7 months)
> > vietnamese (no update since 2 years 7 months)
> > chinese zh_CN (no update since 2 years 3 months)
> > All of them are po-based translations, so the manuals are strictly
> > spoken not outdated (changed paragraphs fall-back to english), but it of
> > no good use for users probably?
> 
> Well, if I had a choice between a manual thta was all in a foreign 
> language and one that was half in a foreign language and half in mine, 
> I'd prefer the one that was half in mine.

Yeah, I guess keeping the translations enabled means we have a chance
of being useful to some people; seeing clearly partial and/or outdated
translations might give some motivation to potential contributors as
well.

I'm no psychologist though…

Mraw,
KiBi.


signature.asc
Description: Digital signature


Re: CSS for installation guide ?

2015-04-03 Thread Cyril Brulebois
Stéphane Blondon  (2015-04-03):
> 2015-04-03 19:46 GMT+02:00 Karsten Merker :
> > I have just stumbled over a missing png file on the index page
> > of the installation guide:
> >
> > The heading of the section:
> >
> >   "Warning
> >
> >This installation guide is based on an earlier manual written
> >for the old Debian installation system..."
> >
> > 
> >  > src="images/warning.png">
> > Warning
> > 
> >
> > points to a graphics file images/warning.png which does not exist.
> >
> > $ ls images/
> > caution.png  home.png  important.png  next.png  note.png prev.png  up.png
> 
> You can add the warning.png attached to this message in the same directory.
> The provided picture comes from the same source than the other
> pictures (Tango icon project). So the size and the style is the
> equivalent to the other picture.
> 
> Thank you for catching it, I didn't see the need of 'warning.png' file.

Hello,

I don't have the files handy, but caution.png & warning.png might be
similar enough anyway? (As a non-native speaker I tend to consider both
roughly equal. ;))

Mraw,
KiBi.


signature.asc
Description: Digital signature


Re: CSS for installation guide ?

2015-04-03 Thread Stéphane Blondon
2015-04-03 19:46 GMT+02:00 Karsten Merker :
> I have just stumbled over a missing png file on the index page
> of the installation guide:
>
> The heading of the section:
>
>   "Warning
>
>This installation guide is based on an earlier manual written
>for the old Debian installation system..."
>
> 
>  src="images/warning.png">
> Warning
> 
>
> points to a graphics file images/warning.png which does not exist.
>
> $ ls images/
> caution.png  home.png  important.png  next.png  note.png prev.png  up.png

You can add the warning.png attached to this message in the same directory.
The provided picture comes from the same source than the other
pictures (Tango icon project). So the size and the style is the
equivalent to the other picture.

Thank you for catching it, I didn't see the need of 'warning.png' file.


-- 
Stéphane


Processing of partman-efi_66_i386.changes

2015-04-03 Thread Debian FTP Masters
partman-efi_66_i386.changes uploaded successfully to localhost
along with the files:
  partman-efi_66.dsc
  partman-efi_66.tar.xz
  partman-efi_66_i386.udeb

Greetings,

Your Debian queue daemon (running on host franck.debian.org)


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/e1ye41o-00053n...@franck.debian.org



partman-efi_66_i386.changes ACCEPTED into unstable

2015-04-03 Thread Debian FTP Masters


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 26 Mar 2015 07:54:39 +0100
Source: partman-efi
Binary: partman-efi
Architecture: source i386
Version: 66
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team 
Changed-By: Christian Perrier 
Description:
 partman-efi - Add to partman support for EFI System Partitions (udeb)
Changes:
 partman-efi (66) unstable; urgency=low
 .
   [ Updated translations ]
   * Romanian (ro.po) by Bradut Boghita
Checksums-Sha1:
 c0ef76db3b19ac3a9a3b9fe01e7f07d7262ed650 1720 partman-efi_66.dsc
 04f8ed8f0ea007cea90d53152ac683af5bfa05bc 64524 partman-efi_66.tar.xz
 42888162e4ff479a60c26125d99445796a29ff67 42230 partman-efi_66_i386.udeb
Checksums-Sha256:
 f23687390c6efc66444f3b3a86d85c5590b5f00b85a96ef9ce6b937e3d45561b 1720 
partman-efi_66.dsc
 529e3b72682a28eec91146ce2bc96fc306e96e8c484bc1b47dbc9eb4b57076de 64524 
partman-efi_66.tar.xz
 e45a3ddec263dc708c9fc67fdbb3d00e015af43531f6e6b4af3ca86cfa73342a 42230 
partman-efi_66_i386.udeb
Files:
 75ba5802e80280cabaa16517bda973cc 1720 debian-installer standard 
partman-efi_66.dsc
 d80ce8bb83119a3abbb16c8268439b2f 64524 debian-installer standard 
partman-efi_66.tar.xz
 03a8754b35dff2976e7ae71dbbc86e8f 42230 debian-installer standard 
partman-efi_66_i386.udeb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJVE69sAAoJEIcvcCxNbiWou5oQALc/aeM/g96oJzCz/KzetTcb
t0MqduPh7CAaqBan8FuhFuemzDCPprMR+PbHX+g/sWByTDDujFhNAlgwQeY3XHJE
Ar+MYzvwKS4Yij1lKZyeWAQxKRMPaiu497uWrHSILVlr40IrtuhzBN3TnOjS7nrc
k969lGTxKwUaJeknUR6RLbqCE4JUKpJLZUV6FDqnBFmF3H4vHK4o+6HdqVhB1iDD
MDlE2OPFEMI8Mg3utNvx81pTRR6CaDFAsWlX4bxGU7//n2ExpxhlHExpnQPlybi0
0LdnbSyigLn3qpj9TbGJR7MpDNw93UcJT4KX5zfgyYTls4M9L60Omzix6Wn0NO1J
i1fVZM9m1styI/0u15/Y36+ARC1VqKvNmANNAdYfuIS0hL2f0wNJjrtEe2AkyDMs
tWq7PnI3balqT8CXoF8KnrFQl0WlLd8G1m91c/ivhpIHbgiUbjGSXJ8EP1gsexyM
awBaF03K9B1Vxm/an65qQ7VR+P0EOWGmK4YWS2TJpJf0NyI/Bc2u2u4SNuqqEywF
s9fxgVDT8K+lNdMkHlEaCMR5o9fs5p854BawbBADHykUPFIeDYsludmfaFgZh/JX
xAoXaO14S+0v/gxBMWCafL+lB84hXajYkB1K3Ik0jFmzg8rEBHBvs3DwdkuWvqkq
jAHWEDUVI/1s3pCFXmhZ
=949+
-END PGP SIGNATURE-


Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/e1ye44c-0005lo...@franck.debian.org



Processing of partman-efi_66_i386.changes

2015-04-03 Thread Debian FTP Masters
partman-efi_66_i386.changes uploaded successfully to ftp-master.debian.org
along with the files:
  partman-efi_66.dsc
  partman-efi_66.tar.xz
  partman-efi_66_i386.udeb

Greetings,

Your Debian queue daemon (running on host coccia.debian.org)


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/e1ye3zm-0006kf...@coccia.debian.org