dose4udebs is back

2024-03-11 Thread Cyril Brulebois
[ bdrung and vorlon cc'd for information; DSA bcc'd for <3 ]

Hi,

dose4udebs was uncronned a while back, even if git doesn't show a specific
reason for it (lots of live changes hadn't been committed when bubulle
removed himself):
  
https://salsa.debian.org/installer-team/d-i/-/commit/3d25abea44bb9122ee404394f6e84d67aa874b31

The last update happened: Mon Sep 3 01:52:02 UTC 2018. Until that point we
had access to a full Debian mirror on dillon (behind d-i.d.o), which meant
we could access all indices directly.

I requested a while back whether those indices could be made available
again to avoid having to maintain a partial sync myself (as the d-i user),
and DSA agreed to make it happen (thanks!).

This means /srv/mirrors/debian is still a broken symlink (to
/auto.dsa/debian) but we have access to /srv/mirrors/ftp.debian.org/ftp/
instead now.

This means dose4udebs is back:
  
https://salsa.debian.org/installer-team/d-i/-/commit/44263866b787f349fe88710f550387dc1f6c3de4

and it seems to be quite needed nowadays…

Also, thanks to Samuel for the heads-up while filing #1064974 against
alsa-lib, the comment about other packages being possibly affected was
spot on.

Those following debian-boot@ might have noticed other bug reports:
 - #1066069 for libpng1.6 (udeb only)
 - #1066071 for mtdev (udeb only)
 - #1066073 for wireless-tools (udeb only, QA-maintained, fixed)
 - #1066074 for ntfs-3g (deb and udeb)


Graphs are available at the usual place, and I'm notified about changes
between runs:
  https://d-i.debian.org/dose/

That should help us stay on top of changes affecting udeb installability,
shortening the feedback loop for people doing the actual work of patching
many packages. (Some packages were uploaded 10+ days ago.)


Cheers,
-- 
Cyril Brulebois (k...@debian.org)<https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature


mips64el daily builds (hopefully) back

2024-03-03 Thread Cyril Brulebois
Hi,

For some reason, PATH wasn't set in the d-i user's crontab, missing
/usr/local/bin for dd-schroot-cmd. (Dates back all the way to December
when the eller → eberlin switch happened…)


Cheers,
-- 
Cyril Brulebois (k...@debian.org)<https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature


Bug#891009: debootstrap: wrongly falls back to https://deb.debian.org when try to create Ubuntu chroot

2024-02-14 Thread Ken Sharp

This should be fixed in the next release.
https://salsa.debian.org/installer-team/debootstrap/-/commit/7e5923030e331f466ec1b56d875b023a274e9220


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1031643: bring hostname variable back

2023-04-08 Thread Andreas B. Mundt
Hi,

perhaps something like the following in [1] could be a fix:

diff --git a/env2debconf b/env2debconf
index 3032235..80394a4 100755
--- a/env2debconf
+++ b/env2debconf
@@ -3,6 +3,12 @@
 set -e
 export DEBIAN_FRONTEND=none
 . /usr/share/debconf/confmodule
+
+if [ "$(hostname)" != '(none)' ]; then
+   # the hostname has been set as boot param, bring it back here
+   hostname="$(hostname)"
+fi
+

I am not familiar with the code, but from checking the installer
console right at the beginning of the installation, this could
work.

Best regards,

  Andi


[1] https://salsa.debian.org/installer-team/preseed/-/blob/master/env2debconf



Bug#1032831: broken loginscreen when switching virtual console forth and back to tty7 out of an active kde session

2023-03-12 Thread digitalwop
Package: installation-reports


(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

Boot method: USB
Image version: 
https://cdimage.debian.org/cdimage/bookworm_di_alpha2/amd64/iso-cd/
debian-bookworm-DI-alpha2-amd64-netinst.iso
Date: <06.03.2023>

Machine: its an acer travel mate 7750G laptop but i have this problem also on a 
getac s410
laptop
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[E]

Comments/Problems:

I did two new installations of debian 12 on two different laptops(listed 
above), this
problem i have on both on them.
If i start my machine i get the normal login screen of sddm on tty7.
Then i can login and the kde loading screen start and after that i have a 
normal kde
session.
But if i then change witch strg alt f2(for example) the virtual console and 
back to tty7 i am
logged out of my active kde session and get a sddm login screen with a 
"pre-typed greyed"
password.Its the same image just before the KDE loading screen appears after 
you type
your pw and hit enter like on a normal login.

I can only move my mouse around and pressing any key does nothing,no 
interaction with
the login screen is possible, but i can still switch tty back to like tty2.




Found a back door

2022-05-31 Thread CONFIDENTIAL
There are wireless back doors in computers in America that are inactive so
they are stealth. It works on ip address 0.0.0.0, on port 0

You need to make it ease to edit firewall rules in the kernel.


Re: Bug#968091: Switching to another tty then back to tty1 in 20200808-3 netinst snapshot fails install

2021-03-28 Thread Holger Wansing
Hi,

Job Bautista  wrote (Sat, 08 Aug 2020 13:08:11 
+):
> Okay, I was still able to install the image successfully.
> 
> Job Bautista

so closing this bug


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Bug#968091: Switching to another tty then back to tty1 in 20200808-3 netinst snapshot fails install

2020-08-08 Thread Job Bautista
py services are supported (int 13h)
dmidecode:  3.5"/720 kB floppy services are supported (int 13h)
dmidecode:  3.5"/2.88 MB floppy services are supported (int 13h)
dmidecode:  Print screen service is supported (int 5h)
dmidecode:  8042 keyboard services are supported (int 9h)
dmidecode:  Serial services are supported (int 14h)
dmidecode:  Printer services are supported (int 17h)
dmidecode:  ACPI is supported
dmidecode:  USB legacy is supported
dmidecode:  Smart battery is supported
dmidecode:  BIOS boot specification is supported
dmidecode:  Targeted content distribution is supported
dmidecode:  UEFI is supported
dmidecode:  BIOS Revision: 5.11
dmidecode: 

dmidecode: Handle 0x0001, DMI type 1, 27 bytes
dmidecode: System Information
dmidecode:  Manufacturer: ASUSTeK COMPUTER INC.
dmidecode:  Product Name: X441UA
dmidecode:  Version: 1.0   

dmidecode:  Serial Number: H2N0WU064884075 

dmidecode:  UUID: 77a02d1c-0fef-2246-88d9-7746d153f281
dmidecode:  Wake-up Type: Power Switch
dmidecode:  SKU Number: ASUS-NotebookSKU
dmidecode:  Family: X
dmidecode: 

dmidecode: Handle 0x0002, DMI type 2, 15 bytes
dmidecode: Base Board Information
dmidecode:  Manufacturer: ASUSTeK COMPUTER INC.
dmidecode:  Product Name: X441UA
dmidecode:  Version: 1.0   

dmidecode:  Serial Number: BSN12345678901234567
dmidecode:  Asset Tag: ATN12345678901234567
dmidecode:  Features:
dmidecode:  Board is a hosting board
dmidecode:  Board is replaceable
dmidecode:  Location In Chassis: MIDDLE  

dmidecode:  Chassis Handle: 0x0003
dmidecode:  Type: Motherboard
dmidecode:  Contained Object Handles: 0
dmidecode: 

dmidecode: Handle 0x0003, DMI type 3, 22 bytes
dmidecode: Chassis Information
dmidecode:  Manufacturer: ASUSTeK COMPUTER INC.
dmidecode:  Type: Notebook
dmidecode:  Lock: Not Present
dmidecode:  Version: 1.0   

dmidecode:  Serial Number: H2N0WU064884075 

dmidecode:  Asset Tag: ATN12345678901234567
dmidecode:  Boot-up State: Safe
dmidecode:  Power Supply State: Safe
dmidecode:  Thermal State: Safe
dmidecode:  Security Status: None
dmidecode:  OEM Information: 0x
dmidecode:  Height: Unspecified
dmidecode:  Number Of Power Cords: 1
dmidecode:  Contained Elements: 0
dmidecode:  SKU Number: Default string
dmidecode: 

dmidecode: Handle 0x0004, DMI type 10, 26 bytes
dmidecode: On Board Device 1 Information
dmidecode:  Type: Video
dmidecode:  Status: Enabled
dmidecode:  Description:  VGA
dmidecode: On Board Device 2 Information
dmidecode:  Type: Ethernet
dmidecode:  Status: Enabled
dmidecode:  Description:  GLAN
dmidecode: On Board Device 3 Information
dmidecode:  Type: Ethernet
dmidecode:  Status: Enabled
dmidecode:  Description:  WLAN
dmidecode: On Board Device 4 Information
dmidecode:  Type: Sound
dmidecode:  Status: Enabled
dmidecode:  Description:  Audio CODEC 

dmidecode: On Board Device 5 Information
dmidecode:  Type: SATA Controller
dmidecode:  Status: Enabled
dmidecode:  Description:  SATA Controller
dmidecode: On Board Device 6 Information
dmidecode:  Type: Other
dmidecode:  Status: Enabled
dmidecode:  Description:  USB 2.0 Controller
dmidecode: On Board Device 7 Information
dmidecode:  Type: Other
dmidecode:  Status: Enabled
dmidecode:  Description:  USB 3.0 Controller
dmidecode: On Board Device 8 Information
dmidecode:  Type: Other
dmidecode:  Status: Enabled
dmidecode:  Description:  SMBus Controller
dmidecode: On Board Device 9 Information
dmidecode:  Type: Other
dmidecode:  Status: Enabled
dmidecode:  Description:  Card Reader
dmidecode: On Board Device 10 Information
dmidecode:  Type: Other
dmidecode:  Status: Enabled
dmidecode:  Description:  Cmos Camera
dmidecode: On Board Device 11 Information
dmidecode:  Type: Other
dmidecode:  Status: Enabled
dmidecode:  Description:  Bluetooth
dmidecode: 

dmidecode: Handle 0x0005, DMI type 11, 5 bytes
dmidecode: OEM Strings
dmidecode:  String 1:  

dmidecode:  String 2:  

dmidecode:  String 3:  

dmidecode:  String 4: 90NB0C92-M02540
dmidecode:  String 5:  

dmidecode:  String 6:  

dmidecode:  String 7:  

dmidecode:  String 8:  

dmidecode:  String 9:  

dmidecode:  String 10:  

dmidecode: 

dmidecode: Handle 0x000C, DMI type 32, 20 bytes
dmidecode: System Boot Information
dmidecode:  Status: No errors detected
dmidecode: 

dmidecode: Handle 0x000D, DMI type 7, 19 bytes
dmidecode: Cache Information
dmidecode:  Socket Designation: L1 Cache
dmidecode:  Configuration: Enabled, Not Socketed, Level 1
dmidecod

Bug#849508: marked as done (add GO BACK choice to save logs question)

2020-08-07 Thread Debian Bug Tracking System
Your message dated Fri, 7 Aug 2020 23:44:04 +0200
with message-id <20200807234404.35e377ed8bc47c218bcf5...@mailbox.org>
and subject line Re: Mass-closing old installation-report bugs  ---  round 4
has caused the Debian Bug report #849508,
regarding add GO BACK choice to save logs question
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.)


-- 
849508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports

Using
DISTRIB_RELEASE="9 (stretch) - installer build 20161212-00:04"
when getting to the question about saving logs,
the user is prompted with /mnt .

At this point the user wants to GO BACK to choose "open a shell" to
inspect what places are in fact mounted.

However at this point there is no GO BACK choice, only Continue!

In fact you might check for other questions that lack GO BACK to see if
they sould have it added or not.
--- End Message ---
--- Begin Message ---
Hi,

Holger Wansing  wrote:
> 
> I'm closing the reports below.
> 
> That's installation-reports for Debian 7 with
> - undefined errors
> - problems which are likely to have been fixed in the meantime
> - successful installation
> 
> Because of the age, there is no chance to analyse them further and therefore
> they are no longer relevant or of any use for current releases:

round 4 (for Debian 7 / 8):

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809618
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809654
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813378
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815491
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815831
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817259
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817946
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819007
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822940
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823845
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824496
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824731
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825835
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826018
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827257
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827610
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827828
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829613
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831513
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831842
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834601
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834806
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834930
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835567
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836345
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837509
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837625
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838319
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839042
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839672
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839803
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840585
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841062
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841747
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842382
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843348
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844519
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846946
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847038
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848075
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848147
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848383
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848929
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849508
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850747
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851947
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852660
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853268
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855349
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857453
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857605
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857646
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859396
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859449
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859970
https:

Bug#945772: marked as done (kernel-wedge: autopkgtest failure: +dpkg-architecture: warning: cannot determine CC system type, falling back to default (native compilation))

2019-11-29 Thread Debian Bug Tracking System
Your message dated Fri, 29 Nov 2019 18:34:47 +
with message-id 
and subject line Bug#945772: fixed in kernel-wedge 2.101
has caused the Debian Bug report #945772,
regarding kernel-wedge: autopkgtest failure: +dpkg-architecture: warning: 
cannot determine CC system type, falling back to default (native compilation)
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.)


-- 
945772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945772
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kernel-wedge
Version: 2.100
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of kernel-wedge you introduced an autopkgtest in
your package. However the test fails. I copied some of the output at the
bottom of this report. Are you missing a test dependency?

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=kernel-wedge

https://ci.debian.net/data/autopkgtest/testing/amd64/k/kernel-wedge/3378125/log.gz

autopkgtest [04:27:25]: test preprocess: [---
I: Testing preprocess case builtin
Files /dev/null and
/tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/builtin.err differ
--- /dev/null   2019-11-10 04:27:02.357733355 +
+++ /tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/builtin.err
2019-11-10 04:27:26.013635941 +
@@ -0,0 +1 @@
+dpkg-architecture: warning: cannot determine CC system type, falling
back to default (native compilation)
E: rc=0
I: Testing preprocess case excludemissing
Files /dev/null and
/tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/excludemissing.err
differ
--- /dev/null   2019-11-10 04:27:02.357733355 +
+++
/tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/excludemissing.err
2019-11-10 04:27:26.057635759 +
@@ -0,0 +1 @@
+dpkg-architecture: warning: cannot determine CC system type, falling
back to default (native compilation)
E: rc=0
I: Testing preprocess case hyphen
Files /dev/null and
/tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/hyphen.err differ
--- /dev/null   2019-11-10 04:27:02.357733355 +
+++ /tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/hyphen.err
2019-11-10 04:27:26.101635578 +
@@ -0,0 +1 @@
+dpkg-architecture: warning: cannot determine CC system type, falling
back to default (native compilation)
E: rc=0
I: Testing preprocess case include
Files /dev/null and
/tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/include.err differ
--- /dev/null   2019-11-10 04:27:02.357733355 +
+++ /tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/include.err
2019-11-10 04:27:26.145635397 +
@@ -0,0 +1 @@
+dpkg-architecture: warning: cannot determine CC system type, falling
back to default (native compilation)
E: rc=0
I: Testing preprocess case missing
Files debian/tests/preprocess-data/missing.err and
/tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/missing.err differ
--- debian/tests/preprocess-data/missing.err2019-02-12
19:30:33.0 +
+++ /tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/missing.err
2019-11-10 04:27:26.185635232 +
@@ -1,2 +1,3 @@
+dpkg-architecture: warning: cannot determine CC system type, falling
back to default (native compilation)
 missing module does-not-exist
 Died at SOMEWHERE.
E: rc=255
I: Testing preprocess case missingdir
Files debian/tests/preprocess-data/missingdir.err and
/tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/missingdir.err differ
--- debian/tests/preprocess-data/missingdir.err 2019-02-12
19:29:24.0 +
+++ /tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/missingdir.err
2019-11-10 04:27:26.229635051 +
@@ -1 +1,2 @@
+dpkg-architecture: warning: cannot determine CC system type, falling
back to default (native compilation)
 pattern missing/dir/* refers to nonexistent subdirectory at SOMEWHERE,
<$fh> line 1.
E: rc=2
I: Testing preprocess case simple
Files /dev/null and
/tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/simple.err differ
--- /dev/null   2019-11-10 04:27:02.357733355 +
+++ /tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/simple.err
2019-11-10 04:27:26.273634869 +
@@ -0,0 +1 @@
+dpkg-architecture: warning: cannot determine CC system type, falling
back to default (native compilation)
E: rc=0
I: Testing preprocess case underscore

Bug#945772: kernel-wedge: autopkgtest failure: +dpkg-architecture: warning: cannot determine CC system type, falling back to default (native compilation)

2019-11-28 Thread Paul Gevers
Source: kernel-wedge
Version: 2.100
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of kernel-wedge you introduced an autopkgtest in
your package. However the test fails. I copied some of the output at the
bottom of this report. Are you missing a test dependency?

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=kernel-wedge

https://ci.debian.net/data/autopkgtest/testing/amd64/k/kernel-wedge/3378125/log.gz

autopkgtest [04:27:25]: test preprocess: [---
I: Testing preprocess case builtin
Files /dev/null and
/tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/builtin.err differ
--- /dev/null   2019-11-10 04:27:02.357733355 +
+++ /tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/builtin.err
2019-11-10 04:27:26.013635941 +
@@ -0,0 +1 @@
+dpkg-architecture: warning: cannot determine CC system type, falling
back to default (native compilation)
E: rc=0
I: Testing preprocess case excludemissing
Files /dev/null and
/tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/excludemissing.err
differ
--- /dev/null   2019-11-10 04:27:02.357733355 +
+++
/tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/excludemissing.err
2019-11-10 04:27:26.057635759 +
@@ -0,0 +1 @@
+dpkg-architecture: warning: cannot determine CC system type, falling
back to default (native compilation)
E: rc=0
I: Testing preprocess case hyphen
Files /dev/null and
/tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/hyphen.err differ
--- /dev/null   2019-11-10 04:27:02.357733355 +
+++ /tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/hyphen.err
2019-11-10 04:27:26.101635578 +
@@ -0,0 +1 @@
+dpkg-architecture: warning: cannot determine CC system type, falling
back to default (native compilation)
E: rc=0
I: Testing preprocess case include
Files /dev/null and
/tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/include.err differ
--- /dev/null   2019-11-10 04:27:02.357733355 +
+++ /tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/include.err
2019-11-10 04:27:26.145635397 +
@@ -0,0 +1 @@
+dpkg-architecture: warning: cannot determine CC system type, falling
back to default (native compilation)
E: rc=0
I: Testing preprocess case missing
Files debian/tests/preprocess-data/missing.err and
/tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/missing.err differ
--- debian/tests/preprocess-data/missing.err2019-02-12
19:30:33.0 +
+++ /tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/missing.err
2019-11-10 04:27:26.185635232 +
@@ -1,2 +1,3 @@
+dpkg-architecture: warning: cannot determine CC system type, falling
back to default (native compilation)
 missing module does-not-exist
 Died at SOMEWHERE.
E: rc=255
I: Testing preprocess case missingdir
Files debian/tests/preprocess-data/missingdir.err and
/tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/missingdir.err differ
--- debian/tests/preprocess-data/missingdir.err 2019-02-12
19:29:24.0 +
+++ /tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/missingdir.err
2019-11-10 04:27:26.229635051 +
@@ -1 +1,2 @@
+dpkg-architecture: warning: cannot determine CC system type, falling
back to default (native compilation)
 pattern missing/dir/* refers to nonexistent subdirectory at SOMEWHERE,
<$fh> line 1.
E: rc=2
I: Testing preprocess case simple
Files /dev/null and
/tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/simple.err differ
--- /dev/null   2019-11-10 04:27:02.357733355 +
+++ /tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/simple.err
2019-11-10 04:27:26.273634869 +
@@ -0,0 +1 @@
+dpkg-architecture: warning: cannot determine CC system type, falling
back to default (native compilation)
E: rc=0
I: Testing preprocess case underscore
Files /dev/null and
/tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/underscore.err differ
--- /dev/null   2019-11-10 04:27:02.357733355 +
+++ /tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/underscore.err
2019-11-10 04:27:26.313634705 +
@@ -0,0 +1 @@
+dpkg-architecture: warning: cannot determine CC system type, falling
back to default (native compilation)
E: rc=0
I: Testing preprocess case wilddoublestar
Files /dev/null and
/tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/wilddoublestar.err
differ
--- /dev/null   2019-11-10 04:27:02.357733355 +
+++
/tmp/autopkgtest-lxc.r3lmallz/downtmp/autopkgtest_tmp/wilddoublestar.err
2019-11-10 04:27:26.357634524 +
@@ -0,0 +1 @@
+dpkg-architecture: warning: cannot determine CC system type, falling
back to default (native compilation)
E: rc=0
I: Testing preprocess case wildstar
Files /dev/null and
/tmp/autopkgtest-lxc.r3lmallz/d

Bug#924037: marked as done (Please add anacron back to task-desktop and task-laptop)

2019-03-10 Thread Debian Bug Tracking System
Your message dated Sun, 10 Mar 2019 22:34:55 +
with message-id 
and subject line Bug#924037: fixed in tasksel 3.51
has caused the Debian Bug report #924037,
regarding Please add anacron back to task-desktop and task-laptop
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.)


-- 
924037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924037
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: task-desktop
Version: 3.49

The rationale for this change is IMO not correct.

Michael Biebl  wrote:
| all important cron jobs have a corresponding .timer unit

This is not a sufficient condition.  Firstly, it is necessary for all
cron jobs, not just ones considered `important', to have a
corresponding timer unit, for this change to be correct.

Secondly, this change simply breaks systems without systemd.  If
(which I deny) it is a good idea to change this for systemd systems,
measures should be taken to arrange that non-systemd systems still get
anacron.  For example, a dependency on   systemd-sysv | anacron

(Thirdly, and tangentially, for reasons explored further in the
debian-devel thread, systemd timer units are not a suitable
replacement for many applications.)

Also I think that when changes are being made which might break
non-systemd systems, the Debian Ecosystem Init Diversity team
 debian-init-divers...@chiark.greenend.org.uk
should be consulted so that the appropriate fixes can be developed.

Finally, this change is rather late wrt the freeze.

Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
--- End Message ---
--- Begin Message ---
Source: tasksel
Source-Version: 3.51

We believe that the bug you reported is fixed in the latest version of
tasksel, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 924...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Holger Wansing  (supplier of updated tasksel package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 10 Mar 2019 23:12:54 +0100
Source: tasksel
Architecture: source
Version: 3.51
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Closes: 823150 824729 910615 915370 922123 923975 924037
Changes:
 tasksel (3.51) unstable; urgency=medium
 .
   * Team upload.
 .
   * Add firefox-l10n-ne-np to task-nepali-desktop. Closes: #922123
   * Re-add anacron to task-desktop and task-laptop (removed in 3.49).
 Closes: #924037, #915370
   * task-catalan-desktop: replace removed myspell-ca by hunspell-ca.
 Closes: #910615
   * task-greek-desktop: remove no longer existing fonts-mgopen. Closes: #823150
   * Some clean-up: (Closes: #923975)
   * Remove several no longer existing packages.
   * Remove some badly outdated documentation packages.
   * Replace some transitional packages by their Depends.
   * Correct name inconsistency in tasks/uyghur-desktop.
   * Replace transitional package myspell-bg by its Depends hunspell-bg.
 Closes: #824729
   * Replace some more myspell-* transitional packages by their Depends
 (hunspell-*).
 .
   [ Updated debconf translations ]
   * Danish (da.po) by Joe Dalton.
   * Norwegian Bokmål (nb.po) by Petter Reinholdtsen.
Checksums-Sha1:
 65560db910aa6923ca43ecc0302ae049227bec57 17094 tasksel_3.51.dsc
 e451a864831538db78728e3406fefd561e3969fe 289564 tasksel_3.51.tar.xz
 e1b870c7fd45660a5e4a60ea14de8ee2c348fe9d 65022 tasksel_3.51_amd64.buildinfo
Checksums-Sha256:
 40e94a943ce496b42b587bfc4ef5b797d352a6b3b2cdc67b97555ab0cb643cff 17094 
tasksel_3.51.dsc
 b2a99b7b75d64e50899e4ef4234d1f248dc7b0ee79ba6687befa30db1ceb30a0 289564 
tasksel_3.51.tar.xz
 5cf0a6aa1895c8dd2243b83ce57675c52021cf656e9ff000d7cd95968710 65022 
tasksel_3.51_amd64.buildinfo
Files:
 8a6e858c64a62e09942edaff3039c0dd 17094 tasks optional tasksel_3.51.dsc
 42e4d02bea337b3ddd26373d1626aa3a 289564 tasks optional tasksel_3.51.tar.xz
 f5d2ec6bb306ad2387306304ceaee25e 65022 tasks optional 
tasksel_3.51_amd64.buildinfo

-BEGIN PGP SIGNATURE

Processed: Re: Bug#924037: Please add anacron back to task-desktop and task-laptop

2019-03-08 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + pending
Bug #924037 [task-desktop] Please add anacron back to task-desktop and 
task-laptop
Added tag(s) pending.

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



Bug#924037: Please add anacron back to task-desktop and task-laptop

2019-03-08 Thread Holger Wansing
Control: tags -1 + pending


Cyril Brulebois  wrote:
> Hi Holger,
> 
> Holger Wansing  (2019-03-08):
> > Since this is just a revert of a recent change, this can be considered
> > causing no harm.
> > 
> > Any objections?
> > kibi?
> 
> Sure, a revert looks good indeed; thanks!

Just committed.
Tagging this bug as pending



Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Bug#924037: Please add anacron back to task-desktop and task-laptop

2019-03-08 Thread Cyril Brulebois
Hi Holger,

Holger Wansing  (2019-03-08):
> Since this is just a revert of a recent change, this can be considered
> causing no harm.
> 
> Any objections?
> kibi?

Sure, a revert looks good indeed; thanks!


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature


Bug#924037: Please add anacron back to task-desktop and task-laptop

2019-03-08 Thread john doe
On 3/8/2019 7:17 PM, Holger Wansing wrote:
> Hi,
>
> Ian Jackson  wrote:
>> Package: task-desktop
>> Version: 3.49
>>
>> The rationale for this change is IMO not correct.
>>
>> Michael Biebl  wrote:
>> | all important cron jobs have a corresponding .timer unit
>>
>> This is not a sufficient condition.  Firstly, it is necessary for all
>> cron jobs, not just ones considered `important', to have a
>> corresponding timer unit, for this change to be correct.
>>
>> Secondly, this change simply breaks systems without systemd.  If
>> (which I deny) it is a good idea to change this for systemd systems,
>> measures should be taken to arrange that non-systemd systems still get
>> anacron.  For example, a dependency on   systemd-sysv | anacron
>>
>> (Thirdly, and tangentially, for reasons explored further in the
>> debian-devel thread, systemd timer units are not a suitable
>> replacement for many applications.)
>>
>> Also I think that when changes are being made which might break
>> non-systemd systems, the Debian Ecosystem Init Diversity team
>>  debian-init-divers...@chiark.greenend.org.uk
>> should be consulted so that the appropriate fixes can be developed.
>
> I tend to follow this proposal (also looking at the corresponding
> discussion on d-devel).
>
>> Finally, this change is rather late wrt the freeze.
>
> Since this is just a revert of a recent change, this can be considered
> causing no harm.
>
>
> Any objections?
> kibi?
>

I'm probably missing something here, this change have never had the
green light to go ahead in the first place.

--
John Doe



Bug#924037: Please add anacron back to task-desktop and task-laptop

2019-03-08 Thread Holger Wansing
Hi,

Ian Jackson  wrote:
> Package: task-desktop
> Version: 3.49
> 
> The rationale for this change is IMO not correct.
> 
> Michael Biebl  wrote:
> | all important cron jobs have a corresponding .timer unit
> 
> This is not a sufficient condition.  Firstly, it is necessary for all
> cron jobs, not just ones considered `important', to have a
> corresponding timer unit, for this change to be correct.
> 
> Secondly, this change simply breaks systems without systemd.  If
> (which I deny) it is a good idea to change this for systemd systems,
> measures should be taken to arrange that non-systemd systems still get
> anacron.  For example, a dependency on   systemd-sysv | anacron
> 
> (Thirdly, and tangentially, for reasons explored further in the
> debian-devel thread, systemd timer units are not a suitable
> replacement for many applications.)
> 
> Also I think that when changes are being made which might break
> non-systemd systems, the Debian Ecosystem Init Diversity team
>  debian-init-divers...@chiark.greenend.org.uk
> should be consulted so that the appropriate fixes can be developed.

I tend to follow this proposal (also looking at the corresponding
discussion on d-devel).

> Finally, this change is rather late wrt the freeze.

Since this is just a revert of a recent change, this can be considered
causing no harm.


Any objections?
kibi?


Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Bug#924037: Please add anacron back to task-desktop and task-laptop

2019-03-08 Thread Ian Jackson
Package: task-desktop
Version: 3.49

The rationale for this change is IMO not correct.

Michael Biebl  wrote:
| all important cron jobs have a corresponding .timer unit

This is not a sufficient condition.  Firstly, it is necessary for all
cron jobs, not just ones considered `important', to have a
corresponding timer unit, for this change to be correct.

Secondly, this change simply breaks systems without systemd.  If
(which I deny) it is a good idea to change this for systemd systems,
measures should be taken to arrange that non-systemd systems still get
anacron.  For example, a dependency on   systemd-sysv | anacron

(Thirdly, and tangentially, for reasons explored further in the
debian-devel thread, systemd timer units are not a suitable
replacement for many applications.)

Also I think that when changes are being made which might break
non-systemd systems, the Debian Ecosystem Init Diversity team
 debian-init-divers...@chiark.greenend.org.uk
should be consulted so that the appropriate fixes can be developed.

Finally, this change is rather late wrt the freeze.

Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.



Bug#914605: marked as done (task-japanese-gnome-desktop: Icedove is now back to Thunderbird)

2018-12-25 Thread Debian Bug Tracking System
Your message dated Tue, 25 Dec 2018 20:41:21 +
with message-id 
and subject line Bug#914605: fixed in tasksel 3.49
has caused the Debian Bug report #914605,
regarding task-japanese-gnome-desktop: Icedove is now back to Thunderbird
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.)


-- 
914605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914605
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: task-japanese-gnome-desktop
Version: 3.48
Severity: normal

Dear Maintainer,

Icedove is now back to Thunderbird.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), 
LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages task-japanese-gnome-desktop depends on:
ii  tasksel  3.48

Versions of packages task-japanese-gnome-desktop recommends:
pn  icedove  
pn  icedove-l10n-ja  

task-japanese-gnome-desktop suggests no packages.

-- no debconf information
diff --git a/debian/control b/debian/control
index 65290fbe..f22b8ef1 100644
--- a/debian/control
+++ b/debian/control
@@ -1438,9 +1438,9 @@ Depends: ${misc:Depends},
 Recommends:
 # evolution has a problem for Japanese, for example it uses always UTF-8
 # subject instead of iso-2022-jp used Japanese de-facto. I recommend
-# icedove as default mailer for Japanese desktop users.
-   icedove,
-   icedove-l10n-ja
+# thunderbird as default mailer for Japanese desktop users.
+   thunderbird,
+   thunderbird-l10n-ja
 
 Package: task-japanese-kde-desktop
 Architecture: all
--- End Message ---
--- Begin Message ---
Source: tasksel
Source-Version: 3.49

We believe that the bug you reported is fixed in the latest version of
tasksel, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 914...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Holger Wansing  (supplier of updated tasksel package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 25 Dec 2018 20:55:39 +0100
Source: tasksel
Binary: tasksel tasksel-data task-desktop task-gnome-desktop task-kde-desktop 
task-lxde-desktop task-lxqt-desktop task-xfce-desktop task-cinnamon-desktop 
task-mate-desktop task-laptop task-web-server task-print-server task-ssh-server 
task-albanian-desktop task-amharic task-amharic-desktop 
task-amharic-kde-desktop task-arabic task-arabic-desktop 
task-arabic-kde-desktop task-asturian task-asturian-desktop task-basque 
task-basque-desktop task-basque-kde-desktop task-belarusian 
task-belarusian-desktop task-belarusian-kde-desktop task-bengali 
task-bengali-desktop task-bengali-kde-desktop task-bosnian task-bosnian-desktop 
task-bosnian-kde-desktop task-brazilian-portuguese 
task-brazilian-portuguese-desktop task-brazilian-portuguese-kde-desktop 
task-british-desktop task-british-kde-desktop task-bulgarian 
task-bulgarian-desktop task-bulgarian-kde-desktop task-catalan 
task-catalan-desktop task-catalan-kde-desktop task-chinese-s 
task-chinese-s-desktop task-chinese-s-kde-desktop
 task-chinese-t task-chinese-t-desktop task-chinese-t-kde-desktop task-croatian 
task-croatian-desktop task-croatian-kde-desktop task-czech task-czech-desktop 
task-czech-kde-desktop task-danish task-danish-desktop task-danish-kde-desktop 
task-dutch task-dutch-desktop task-dutch-kde-desktop task-dzongkha-desktop 
task-dzongkha-kde-desktop task-english task-esperanto task-esperanto-desktop 
task-esperanto-kde-desktop task-estonian task-estonian-desktop 
task-estonian-kde-desktop task-finnish task-finnish-desktop 
task-finnish-kde-desktop task-french task-french-desktop 
task-french-kde-desktop task-galician task-galician-desktop 
task-galician-kde-desktop task-georgian-desktop task-german task-german-desktop 
task-german-kde-desktop task-greek task-greek-desktop task-greek-kde-desktop 
task-gujarati task-gujarati-desktop task-gujarati-kde-desktop

Processed: Re: Bug#914605: task-japanese-gnome-desktop: Icedove is now back to Thunderbird

2018-11-25 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + pending
Bug #914605 [task-japanese-gnome-desktop] task-japanese-gnome-desktop: Icedove 
is now back to Thunderbird
Added tag(s) pending.

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



Bug#914605: task-japanese-gnome-desktop: Icedove is now back to Thunderbird

2018-11-25 Thread Holger Wansing
Control: tags -1 + pending

Tetsutaro KAWADA  wrote:
> Package: task-japanese-gnome-desktop
> Version: 3.48
> Severity: normal
> 
> Dear Maintainer,
> 
> Icedove is now back to Thunderbird.

Committed to GIT. Thanks for the patch.

Tagging this bug as pending


-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Bug#914605: task-japanese-gnome-desktop: Icedove is now back to Thunderbird

2018-11-25 Thread Tetsutaro KAWADA
Package: task-japanese-gnome-desktop
Version: 3.48
Severity: normal

Dear Maintainer,

Icedove is now back to Thunderbird.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), 
LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages task-japanese-gnome-desktop depends on:
ii  tasksel  3.48

Versions of packages task-japanese-gnome-desktop recommends:
pn  icedove  
pn  icedove-l10n-ja  

task-japanese-gnome-desktop suggests no packages.

-- no debconf information
diff --git a/debian/control b/debian/control
index 65290fbe..f22b8ef1 100644
--- a/debian/control
+++ b/debian/control
@@ -1438,9 +1438,9 @@ Depends: ${misc:Depends},
 Recommends:
 # evolution has a problem for Japanese, for example it uses always UTF-8
 # subject instead of iso-2022-jp used Japanese de-facto. I recommend
-# icedove as default mailer for Japanese desktop users.
-   icedove,
-   icedove-l10n-ja
+# thunderbird as default mailer for Japanese desktop users.
+   thunderbird,
+   thunderbird-l10n-ja
 
 Package: task-japanese-kde-desktop
 Architecture: all


Bug#911750: marked as done (Race condition in d-i leading to kernel from security.debian.org to be kept back)

2018-11-04 Thread Debian Bug Tracking System
Your message dated Sun, 04 Nov 2018 20:40:34 +
with message-id 
and subject line Bug#908711: fixed in pkgsel 0.45+deb9u2
has caused the Debian Bug report #908711,
regarding Race condition in d-i leading to kernel from security.debian.org to 
be kept back
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.)


-- 
908711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Version: 20170615+deb9u4

Hi,

I just noticed a race condition in d-i, which may lead to a mild
security risk.

When the kernel metapackage (linux-image-) is initially installed,
APT doesn't install recommended packages, and security.debian.org
repository is not configured yet, so the installer naturally fetches the
latest kernel from the core suite. After APT configuration, and other
repositories and suites are available, debian-installer runs an upgrade;
but if a newer version of linux-image- is found in one of those
newly available repositories (security.debian.org in this case), it's
not installed because APT refuses to install the recommended packages
(firware-linux-free, irqbalance) to satisfy dependencies, so the kernel
metapackage is kept back.

It won't be installed until the admin runs an upgrade manually, once the
system is booted. This may put it at risk during a certain period of
time between the first boot, and the first upgrade (and reboot).

Regards,

-- 
Raphaël Halimi



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pkgsel
Source-Version: 0.45+deb9u2

We believe that the bug you reported is fixed in the latest version of
pkgsel, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 908...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated pkgsel package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 27 Oct 2018 23:58:05 +0100
Source: pkgsel
Binary: pkgsel
Architecture: source
Version: 0.45+deb9u2
Distribution: stretch
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Ben Hutchings 
Description:
 pkgsel - Select and install packages (udeb)
Closes: 908711
Changes:
 pkgsel (0.45+deb9u2) stretch; urgency=medium
 .
   * Fix target suite
 .
 pkgsel (0.45+deb9u1) unstable; urgency=medium
 .
   * Install new dependencies when safe-upgrade (default) is selected
 (Closes: #908711)
Checksums-Sha1:
 65e0f3423481971b663ccf93cf0a6522ae720c4b 1614 pkgsel_0.45+deb9u2.dsc
 345a1c15e1adba79676ed6a603cf5db835f19b74 31576 pkgsel_0.45+deb9u2.tar.xz
 d066b1f7f89f7c50d6ec43eeaffcf59fb134cd4e 5579 
pkgsel_0.45+deb9u2_source.buildinfo
Checksums-Sha256:
 9fdf1219ddc9dd3dcb25499602b29e9197ceabbb04267e35f00a5150e4b90357 1614 
pkgsel_0.45+deb9u2.dsc
 79e1fc9ab9b44c40b9b4f41b3e1a795d5c9638f3107bae42cd06b72d7d9c7fb8 31576 
pkgsel_0.45+deb9u2.tar.xz
 a62bec47b84083146d88632342bd19626769651a004978caa6096e3b0b10d474 5579 
pkgsel_0.45+deb9u2_source.buildinfo
Files:
 0575e304b3f78fb3e30fbbe1c2f2aa47 1614 debian-installer standard 
pkgsel_0.45+deb9u2.dsc
 f2ccdacf5de3c1715d82d07c1a94bd5a 31576 debian-installer standard 
pkgsel_0.45+deb9u2.tar.xz
 9adb5a938042f4f5d2d5c71835a3ec0f 5579 debian-installer standard 
pkgsel_0.45+deb9u2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAlvU7eoACgkQ57/I7JWG
EQkiexAAofBp6xvsGeulQl3n822p94fkBi8wrIDJnJ7IPUGTRnRyqHR0Cp2dyKim
bAU8YOBZ9GC1ji+QMUUUq1K80mm/kzqx2x4BTVkwl/lM6Rmd4S6dofD3fAGGyYUb
KETEdvdDBBGTtHXZcH1DtJ8O78HV+jSMzn4ZMrjRcaWhlUrPJcDA0WOuf8OiSzL0
D0PW0+qJHu98llO+UAypttQ378btirXKl5ad5akgBTOkKPsfYCRLTiPmu7M9/o84
60cTMvNGStPe3FXRnyeGLP8E0RITrsQNy0l+izKrwraxBPcy1OkKR6oco6St3yA0
QW9KSeFVRkUwI3LEwDxLFjMmEGk31SCCP3rLGjyt3cI8kfXt+J/oW4QKLPRkpmjM
M2fu973rW6doSjHjCKVhjS3w2poks960eouobo9g+JHJh6h5KJKImnvIjA5kErrA
cURvwqAU9l9FBxSrFwME9zCyYpLoVQhxJUgBjguFMmErLpqA7kT30n7eE11Jq/Lw
0wGWm4gkMRYmyTiJJ33RnCfbMw86fJZ+Xj+pbRAav6GtcR4Hh4w2tMk1+MKEjCIx
I3s9WbQfX2jaD3patDrfejyi+6dBXbttLHonwjC0KBIcv3enxhyBSKYYkbT971KR
oxNmM5cYZL/RIN7JLDPBNX/cRdD2wvwtDzA8DOSF42i8MYgQ9X4=
=Gh9O
-END PGP SIGNATURE

Bug#911750: marked as done (Race condition in d-i leading to kernel from security.debian.org to be kept back)

2018-10-27 Thread Debian Bug Tracking System
Your message dated Sat, 27 Oct 2018 22:34:16 +
with message-id 
and subject line Bug#908711: fixed in pkgsel 0.61
has caused the Debian Bug report #908711,
regarding Race condition in d-i leading to kernel from security.debian.org to 
be kept back
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.)


-- 
908711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Version: 20170615+deb9u4

Hi,

I just noticed a race condition in d-i, which may lead to a mild
security risk.

When the kernel metapackage (linux-image-) is initially installed,
APT doesn't install recommended packages, and security.debian.org
repository is not configured yet, so the installer naturally fetches the
latest kernel from the core suite. After APT configuration, and other
repositories and suites are available, debian-installer runs an upgrade;
but if a newer version of linux-image- is found in one of those
newly available repositories (security.debian.org in this case), it's
not installed because APT refuses to install the recommended packages
(firware-linux-free, irqbalance) to satisfy dependencies, so the kernel
metapackage is kept back.

It won't be installed until the admin runs an upgrade manually, once the
system is booted. This may put it at risk during a certain period of
time between the first boot, and the first upgrade (and reboot).

Regards,

-- 
Raphaël Halimi



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pkgsel
Source-Version: 0.61

We believe that the bug you reported is fixed in the latest version of
pkgsel, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 908...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated pkgsel package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 27 Oct 2018 23:19:13 +0100
Source: pkgsel
Binary: pkgsel
Architecture: source
Version: 0.61
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Ben Hutchings 
Description:
 pkgsel - Select and install packages (udeb)
Closes: 908711 912073
Changes:
 pkgsel (0.61) unstable; urgency=medium
 .
   * Install new dependencies when safe-upgrade (default) is selected
 (Closes: #908711)
   * Allow update-initramfs to run normally during package upgrade and
 installation (Closes: #912073)
Checksums-Sha1:
 f9a54e694d52ec258c24c13c57d60b408615e79d 1591 pkgsel_0.61.dsc
 9c4e1e0c424f837f81c80c530a215872fb42e126 51908 pkgsel_0.61.tar.xz
 0215d9dfd0637e797fa1002291d2e5392ed6da59 5153 pkgsel_0.61_source.buildinfo
Checksums-Sha256:
 ee9a00276026e44056b6d66e349d904fb8c5120f80cb0b2d120f266b95023191 1591 
pkgsel_0.61.dsc
 44e5afbb45fb8b341e1970d3b373835aa5f6a239c100ffa92dca96becda96190 51908 
pkgsel_0.61.tar.xz
 adaca32ee52cca5f1742f8fab1ab7bb7fdeabb4787b2748d72b3faaafce1a5a3 5153 
pkgsel_0.61_source.buildinfo
Files:
 2f365d94fc83e321d2370beddd47ec21 1591 debian-installer standard pkgsel_0.61.dsc
 50e06b4b69416f3e276558cab5005608 51908 debian-installer standard 
pkgsel_0.61.tar.xz
 357476cee3242b7ce9a7a3e84405256e 5153 debian-installer standard 
pkgsel_0.61_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAlvU5MEACgkQ57/I7JWG
EQmQKg/+K6MQQygZZb9QbdY/JGZPSaUbGIqOv+/Te/xBqx/fWBpuX7IT+uHzAsk0
wKZ63v7ItTDtRoTZ4mxeciMPg8id8GIJvteji77VIknMDsYXVmvjVaU2lh1klQHB
XuLc0gQEjV/0MIj5vm/b0x9UsT1TNjXTz2WEjgMY1NeomO2O9iMKru6cs3G/Kv3B
mCakH/nTRtQz2BenL5yo6yqbJUK+toNnrTapZou8RjWmttjsaZRUSs18YrOiJ7EC
vtuH8qG6kly/rIv3/X4PD/LwzXhIKXeHssNdtr5bkwq4tA2MbNBCRzLvmxFZkMgd
/+0xmWCLHAtAK/DzDbaqmuZ0wBfn7oc3TsB608Yx6yfummkRIJ+t9irGztmzzcJ3
rjTfi0i7Y5V0fqMJd1//LkT3Bd/5aEmz/C9XluIBKYwXe7KNliBQTZRcwL0VvCPt
oAQ6+CqC/wQJP0pZRab2tYLvf3GLn0L8zB6rFEZl/uf8tdyBnX0BK3VzVaSfe3rH
FGCM2luynmrGGVDMxuITXJgEluQs5NScknfu+9URWWzSLqxuR4yFPKL9eK03P9lZ
DEevnyCIq8LgiqwsRG5lL5n90unJvMT8UbzX53YpD+rocjokWYPDbM2srQGp/nrW
eboPibLXxncyoQilbNCNXWU8QvwMGj9gaRDP28R/H/WXVpk1Szs=
=bWJU
-END PGP SIGNATURE End Message ---


Bug#911750: Race condition in d-i leading to kernel from security.debian.org to be kept back

2018-10-24 Thread Ben Hutchings
On Wed, 2018-10-24 at 16:30 +0200, Raphaël Halimi wrote:
> Le 24/10/2018 à 14:15, Ben Hutchings a écrit :
> > > When the kernel metapackage (linux-image-) is initially installed,
> > > APT doesn't install recommended packages, and security.debian.org
> > > repository is not configured yet, so the installer naturally fetches the
> > > latest kernel from the core suite. After APT configuration, and other
> > > repositories and suites are available, debian-installer runs an upgrade;
> > > but if a newer version of linux-image- is found in one of those
> > > newly available repositories (security.debian.org in this case), it's
> > > not installed because APT refuses to install the recommended packages
> > > (firware-linux-free, irqbalance) to satisfy dependencies, so the kernel
> > > metapackage is kept back.
> > 
> > I'm fairly sure it's the ABI bump in the kernel that prevents
> > upgrading, not the recommended packages.  This is tracked as #908711.
> 
> You're right, it seems so obvious now.
> 
> Sorry for the duplicate, I did search the web for "bugs debian-installer
> kernel not upgraded during installation" but the title of this bug was
> too different, and I missed it.
> 
> Do you want me to close this one, or to merge it ?

I'll merge it.

Ben.

-- 
Ben Hutchings
Never put off till tomorrow what you can avoid all together.




signature.asc
Description: This is a digitally signed message part


Bug#911750: Race condition in d-i leading to kernel from security.debian.org to be kept back

2018-10-24 Thread Raphaël Halimi
Le 24/10/2018 à 14:15, Ben Hutchings a écrit :
>> When the kernel metapackage (linux-image-) is initially installed,
>> APT doesn't install recommended packages, and security.debian.org
>> repository is not configured yet, so the installer naturally fetches the
>> latest kernel from the core suite. After APT configuration, and other
>> repositories and suites are available, debian-installer runs an upgrade;
>> but if a newer version of linux-image- is found in one of those
>> newly available repositories (security.debian.org in this case), it's
>> not installed because APT refuses to install the recommended packages
>> (firware-linux-free, irqbalance) to satisfy dependencies, so the kernel
>> metapackage is kept back.
> 
> I'm fairly sure it's the ABI bump in the kernel that prevents
> upgrading, not the recommended packages.  This is tracked as #908711.

You're right, it seems so obvious now.

Sorry for the duplicate, I did search the web for "bugs debian-installer
kernel not upgraded during installation" but the title of this bug was
too different, and I missed it.

Do you want me to close this one, or to merge it ?

Regards,

-- 
Raphaël Halimi



signature.asc
Description: OpenPGP digital signature


Bug#911750: Race condition in d-i leading to kernel from security.debian.org to be kept back

2018-10-24 Thread Ben Hutchings
On Wed, 2018-10-24 at 12:05 +0200, Raphaël Halimi wrote:
> Package: debian-installer
> Version: 20170615+deb9u4
> 
> Hi,
> 
> I just noticed a race condition in d-i, which may lead to a mild
> security risk.
> 
> When the kernel metapackage (linux-image-) is initially installed,
> APT doesn't install recommended packages, and security.debian.org
> repository is not configured yet, so the installer naturally fetches the
> latest kernel from the core suite. After APT configuration, and other
> repositories and suites are available, debian-installer runs an upgrade;
> but if a newer version of linux-image- is found in one of those
> newly available repositories (security.debian.org in this case), it's
> not installed because APT refuses to install the recommended packages
> (firware-linux-free, irqbalance) to satisfy dependencies, so the kernel
> metapackage is kept back.

I'm fairly sure it's the ABI bump in the kernel that prevents
upgrading, not the recommended packages.  This is tracked as #908711.

Ben.

> It won't be installed until the admin runs an upgrade manually, once the
> system is booted. This may put it at risk during a certain period of
> time between the first boot, and the first upgrade (and reboot).
> 
> Regards,
> 
-- 
Ben Hutchings
Never put off till tomorrow what you can avoid all together.



signature.asc
Description: This is a digitally signed message part


Bug#911750: Race condition in d-i leading to kernel from security.debian.org to be kept back

2018-10-24 Thread Raphaël Halimi
Package: debian-installer
Version: 20170615+deb9u4

Hi,

I just noticed a race condition in d-i, which may lead to a mild
security risk.

When the kernel metapackage (linux-image-) is initially installed,
APT doesn't install recommended packages, and security.debian.org
repository is not configured yet, so the installer naturally fetches the
latest kernel from the core suite. After APT configuration, and other
repositories and suites are available, debian-installer runs an upgrade;
but if a newer version of linux-image- is found in one of those
newly available repositories (security.debian.org in this case), it's
not installed because APT refuses to install the recommended packages
(firware-linux-free, irqbalance) to satisfy dependencies, so the kernel
metapackage is kept back.

It won't be installed until the admin runs an upgrade manually, once the
system is booted. This may put it at risk during a certain period of
time between the first boot, and the first upgrade (and reboot).

Regards,

-- 
Raphaël Halimi



signature.asc
Description: OpenPGP digital signature


Bug#891009: debootstrap: wrongly falls back to https://deb.debian.org when try to create Ubuntu chroot

2018-08-03 Thread Hideki Yamane
On Wed, 21 Feb 2018 22:31:02 +0900 Hideki Yamane  wrote:
> And, https assures only secure *connection*, not integrity of *contents*
> as GPG does, so this behavior is not good, IMO. 

 As I said above, what https ensures and gpg does is different, and "if
 there's no reliable keyring then fallback to https connection" behavior
 is not good. I suggest to remove this feature from debootstrap, do you
 have any idea for it? If so, please let me know it and why.


-- 
Hideki Yamane 



Bug#775444: marked as done (Issue warning if falling back to sha1)

2018-04-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Apr 2018 15:21:07 +
with message-id <e1f4pen-0009u2...@fasolo.debian.org>
and subject line Bug#775444: fixed in debootstrap 1.0.96
has caused the Debian Bug report #775444,
regarding Issue warning if falling back to sha1
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.)


-- 
775444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775444
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap
Tags: security patch

Patch attached to output warning if falling back to sha1.
commit 0911f1a8ba757a013e4c97e017634eb0ab746997
Author: jnqnfe <jnq...@gmail.com>
Date:   Thu Jan 15 19:22:17 2015 +

Issue warning if having to fall back to sha1

diff --git a/debootstrap b/debootstrap
index 3d45c9c..c383517 100755
--- a/debootstrap
+++ b/debootstrap
@@ -461,6 +461,7 @@ if [ -z "$SHA_SIZE" ]; then
SHA_SIZE=256
 fi
 if ! in_path "sha${SHA_SIZE}sum" && ! in_path "sha${SHA_SIZE}"; then
+   warning SHA_SIZE "Cannot find binary for checking sha%s checksums, 
falling back to sha1" "${SHA_SIZE}"
SHA_SIZE=1
 fi
 DEBOOTSTRAP_CHECKSUM_FIELD="SHA$SHA_SIZE"
--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.96

We believe that the bug you reported is fixed in the latest version of
debootstrap, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 775...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hideki Yamane <henr...@debian.org> (supplier of updated debootstrap package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 06 Apr 2018 10:02:20 +0900
Source: debootstrap
Binary: debootstrap debootstrap-udeb
Architecture: source all
Version: 1.0.96
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team <debian-boot@lists.debian.org>
Changed-By: Hideki Yamane <henr...@debian.org>
Description:
 debootstrap - Bootstrap a basic Debian system
 debootstrap-udeb - Bootstrap the Debian system (udeb)
Closes: 563647 586158 732628 734324 754318 762431 775444 775474 798564 806780 
833525
Changes:
 debootstrap (1.0.96) unstable; urgency=medium
 .
   * Escape spaces to fix debootstrap on path contains space fails
 Thanks to Tianon Gravi <tia...@debian.org> for the based patch
 (Closes: #586158, #762431)
   * Add warning if file specified via --keyring does not exist
 Thanks to jnqnfe <jnq...@gmail.com> for the patch
 (Closes: #754318, #775474)
   * Avoid unnecessary keyring warning with --second-stage option
 (Closes: #734324)
   * Output warning if falling back to sha1 (Closes: #775444)
 Thanks to jnqnfe <jnq...@gmail.com> for the patch.
   * Prevent unintended removal with --print-debs option (Closes: #833525)
 Thanks to Johannes Schauer <jo...@debian.org> for the patch
   * Add scripts for Kali Linux (Closes: #798564)
   * Improve manpage description for --{unpack,make}-tarball options
 (Closes: #563647)
 .
   * debian/control
 - Add "Suggests: squid-deb-proxy-client"
   * debian/rules
 - Add Kali for ${keyring} pattern
 .
   [ Sjoerd Simons ]
   * Fix multiple components usage for --foreign/--second-stage
 (Closes: #806780)
 .
   [ Michael Vogt ]
   * Try to auto-detect proxy if available (e.g. squid-deb-proxy-client)
 (Closes: #732628)
Checksums-Sha1:
 e283396a67afae3737229a54c142b2f26f6793b6 1991 debootstrap_1.0.96.dsc
 6abf18b0faa0a47a65e6b30aa9611df3d04127ed 69541 debootstrap_1.0.96.tar.gz
 c583d15df4f603d57079d0d3752051dcdf7ed1d4 19632 debootstrap-udeb_1.0.96_all.udeb
 7a01dd6e1d718cc7846832bfafaaeb08d7991e11 67130 debootstrap_1.0.96_all.deb
 9a8356d661e8bd165ab926c00695322483f0f022 5766 
debootstrap_1.0.96_amd64.buildinfo
Checksums-Sha256:
 d2949b1c59c6de220fdb8ca5992ddf7d4ef6680420604b7b0a5c8141f76cbf51 1991 
debootstrap_1.0.96.dsc
 5fe34b69069a8dcb425450f81d7e7c9eda9a6afd90082985d9e8f790868dae86 69541 
debootstrap_1.0.96.tar.gz
 c03783f84073f8bce653042b9a64179f616cc14352f975ab82e843c5d3c2bfce 19632 

Bug#891009: debootstrap: wrongly falls back to https://deb.debian.org when try to create Ubuntu chroot

2018-02-21 Thread Hideki Yamane
Package: debootstrap
Severity: normal
Vesrion: 1.0.56

Hi,

 If you try "debootstrap  ", it automatically falls
 back to pre-defined HTTPS mirror. 

> keyring () {
> if [ -z "$KEYRING" ]; then
> if [ -e "$1" ]; then
> KEYRING="$1"
> elif [ -z "$DISABLE_KEYRING" ]; then
> if [ -n "$DEF_HTTPS_MIRROR" ] && [ -z "$USER_MIRROR" 
> ] && [ -z "$FORCE_KEYRING" ]; then
> info KEYRING "Keyring file not available at 
> %s; switching to https mirror %s" "$1" "$DEF_HTTPS_MIRROR"
> USER_MIRROR="$DEF_HTTPS_MIRROR"
> else

 But defined DEF_HTTPS_MIRROR is https://deb.debian.org, it fails with
 a bit wrong error message. 

> $ sudo debootstrap artful artful
> I: Keyring file not available at 
> /usr/share/keyrings/ubuntu-archive-keyring.gpg; switching to https mirror 
> https://deb.debian.org/debian
> I: Retrieving InRelease 
> I: Retrieving Release 
> E: Failed getting release file 
> https://deb.debian.org/debian/dists/artful/Release

 Expected behavior is
  - fails with just "Keyring file not available" error message
  - or falls back to Ubuntu https mirror.


 And, https assures only secure *connection*, not integrity of *contents*
 as GPG does, so this behavior is not good, IMO. 


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp



Bug#867571: debian-installer: unexpected behaviour when "Back" selected on task selection screen (netinst, expert)

2017-07-07 Thread Jonathan Dowland

Package: debian-installer
Severity: normal

Dear Maintainer,

I'm performing an expert-mode non-graphical install from the stretch d-i
netinst ISO. I've got as far as the task selection screen. I deselected
everything (including standard system utilities) and selected "Back" rather
than "continue" (trying to provoke d-i to bring me back to the list of
options/stages, rather than continuing to install software)

Instead, d-i has now begun to install packages... 1497 of them, including
lots of X-related packages according to the log. so it would appear that,
having not confirmed my deselection of the tasks, the default selection of
tasks are selected and d-i has embarked on installing them, despite me not
pressing "continue".

This is very counterintuitive!

--

Jonathan Dowland



Bug#861573: debian-installer: function 'go-back' broken

2017-04-30 Thread DoctorD90
Package: debian-installer
Version: From Netinst.iso: Binary-1 20170116-10:57
Severity: critical
Tags: d-i
Justification: breaks the whole system

Dear Maintainer,

Im installing debian jessie from netinstall iso amd64.
For example (you will understand later), I've chosen "espeak-udeb" package.
When it asks to configure it, it just go back to that step (after choose lang),
but it doesnt do anything, then jump up to the "previous" next step.
The issue start to be important during settings of hard disk. I've chosen dm-
crypt in pack to load. When I setup a partition, it allowes me to choose
encrypted, but it doesnt allow me to choose "the use" (boot, home, root, etc).
When I choose for example "swap", next partition I will go to create, and I
enter in "formating", the selector highlights still "swap". The same if I click
a partition created yet.
Once I end with partitioning, and I enter in encryption phase, if I make a
mistake, after password settings, I have to reboot, because "go back" do not
unmount dm-crypt and doesnt allow to make new changes. In theory using "go-
back" should allow me to "reset" actions taken after that step, but this doesnt
happend. It is probably an issue in indexing of variable, and/or refreshing of
stage in which user is going to enter. Even if I choose "detect disk". The same
at one step during first stages, network settings if I remember well: it asks
me if I can load from a usb the firmware of wifi; I chose "no". If I restart
that stage, it will not ask me again. It is there an issue in "go back"
function to reset to the defaults options and show up again the questions.
Im running the installer on another pc (uefi), but the same "not reset" issue I
find out in netinstall of jan 2016, when I installed this system(not uefi).



-- System Information:
Debian Release: 8.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

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



Bug#849508: add GO BACK choice to save logs question

2016-12-27 Thread 積丹尼 Dan Jacobson
Package: installation-reports

Using
DISTRIB_RELEASE="9 (stretch) - installer build 20161212-00:04"
when getting to the question about saving logs,
the user is prompted with /mnt .

At this point the user wants to GO BACK to choose "open a shell" to
inspect what places are in fact mounted.

However at this point there is no GO BACK choice, only Continue!

In fact you might check for other questions that lack GO BACK to see if
they sould have it added or not.



UEFI Secure Boot back-door keys leak

2016-08-11 Thread Jose R R
"Either way, it'd be impossible in practise for MS to revoke every
bootmgr earlier than a certain point, as they'd break install media,
recovery partitions, backups, etc."

https://rol.im/securegoldenkeyboot/


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#584752: marked as done (debian-installer: "GO BACK" not working if harddisk mounted)

2016-06-28 Thread Debian Bug Tracking System
Your message dated Tue, 28 Jun 2016 15:41:46 +0200
with message-id <20160628154146.647ef54e@sylvester.codehelp>
and subject line Re: Bug#584752: same for keymap selection
has caused the Debian Bug report #584752,
regarding debian-installer: "GO BACK" not working if harddisk mounted
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.)


-- 
584752: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584752
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Version: "GO BACK" not working if harddisk mounted
Severity: minor

Dear Sir, 

I mounted the usb pendrive for the ip2100 fw that it asked during installation 
of hte debian testing i386.
OK

I get to the harddisk setup, and make my disks as I desired. 

But the pendrive is still mounted ,,, ... it says IGNORE CANCEL or GO BACK
before starting

I clicked on GO back and it continued anyhow , and did not go back to re-setup 
or whatever to propose to unmount my pendrive

best regards
Y.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-3-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


--- End Message ---
--- Begin Message ---
On Mon, 14 May 2012 23:31:58 +0200 Adam Borowski <kilob...@angband.pl>
wrote:
> On Mon, May 14, 2012 at 10:17:19PM +0100, Miguel Figueiredo wrote:
> > Hi,
> > 
> > On 13-05-2012 13:26, Adam Borowski wrote:
> > >Same for the keymap selection screen: if you select a wrong one,
> > >the   button doesn't work.
> > 
> > Can you give more information in which image this happens and steps
> > to reproduce it?
> 
> D-I alpha1, i386 netinst.
> VirtualBox (current from unstable).
> (not a lowmem issue, same on 64MB and 1G)
> 
> * Install
> * English
> 
> same: other/Europe/Poland/en_US.UTF-8 or United States
> 
> * Persian
> 
> reproducible every time.

Seems like other changes in the meantime have fixed this issue.
Selecting Persian allows the button in the position of Go Back to go
back to the installer menu.

Closing.

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



pgpgGZHnYZ2lk.pgp
Description: OpenPGP digital signature
--- End Message ---


Bug#822353: marked as done ([keyboard-configuration] update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults)

2016-04-23 Thread Debian Bug Tracking System
Your message dated Sun, 24 Apr 2016 00:59:54 +0300
with message-id <20160423215954.ge14...@debian.lan>
and subject line Re: Bug#822353: [keyboard-configuration] update-rc.d: warning: 
start and stop  actions are no longer supported; falling back to defaults
has caused the Debian Bug report #822353,
regarding [keyboard-configuration] update-rc.d: warning: start and stop  
actions are no longer supported; falling back to defaults
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.)


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

Package: keyboard-configuration
Version: 1.123
Severity: normal

#dpkg-reconfigure keyboard-configuration
...
update-rc.d: warning: start and stop actions are no longer supported; 
falling back to defaults


https://lists.debian.org/debian-devel/2013/05/msg01109.html
--- End Message ---
--- Begin Message ---
Package: keyboard-configuration
Version: 1.138

On Sat, Apr 23, 2016 at 09:16:50PM +0300, Alexey Pikalev wrote:
> 
> #dpkg-reconfigure keyboard-configuration
> ...
> update-rc.d: warning: start and stop actions are no longer supported;
> falling back to defaults
> 
> https://lists.debian.org/debian-devel/2013/05/msg01109.html

Fixed in version 1.138.

Anton Zinoviev--- End Message ---


Bug#822353: [keyboard-configuration] update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults

2016-04-23 Thread Alexey Pikalev

Package: keyboard-configuration
Version: 1.123
Severity: normal

#dpkg-reconfigure keyboard-configuration
...
update-rc.d: warning: start and stop actions are no longer supported; 
falling back to defaults


https://lists.debian.org/debian-devel/2013/05/msg01109.html



Re: Merging libnss-dns-udeb and libnss-files-udeb back into libc6-udeb

2016-03-13 Thread Aurelien Jarno
On 2016-03-13 02:26, Aurelien Jarno wrote:
> Hi,
> 
> For historical reason, disk space on boot floppies, the libnss_dns.so.2 
> and libnss_files.so.2 libraries are in separate udeb packages, namely
> libnss-dns-udeb and libnss-files-udeb. This is not the case of the deb
> package, where everything is in the libc6 package.
> 
> In practice these libraries are really small by nowadays standards (22kB
> and 47kB uncompressed), and moreover libnss-dns-udeb is already included 
> in all images. In addition these libraries are tightly coupled to the
> libresolv library which is in libc6-udeb. The recent CVE-2015-7547 has
> shown that, and Ubuntu hit a bug by having the two out of sync in their
> installer [1]. We would have got the same if debian-installer was pulling
> its udeb from debian-security.

Thinking a bit more about that we'll have the same problem. Our 8.3
debian-installer images will likely break when 8.4 is released.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: PGP signature


Re: Merging libnss-dns-udeb and libnss-files-udeb back into libc6-udeb

2016-03-13 Thread Philipp Kern
On Sun, Mar 13, 2016 at 02:26:26AM +0100, Aurelien Jarno wrote:
> For historical reason, disk space on boot floppies, the libnss_dns.so.2 
> and libnss_files.so.2 libraries are in separate udeb packages, namely
> libnss-dns-udeb and libnss-files-udeb. This is not the case of the deb
> package, where everything is in the libc6 package.
> 
> In practice these libraries are really small by nowadays standards (22kB
> and 47kB uncompressed), and moreover libnss-dns-udeb is already included 
> in all images. In addition these libraries are tightly coupled to the
> libresolv library which is in libc6-udeb. The recent CVE-2015-7547 has
> shown that, and Ubuntu hit a bug by having the two out of sync in their
> installer [1]. We would have got the same if debian-installer was pulling
> its udeb from debian-security.
> 
> That's why I would like to propose to merge back libnss-dns-udeb and
> libnss-files-udeb back into libc6-udeb. The idea is to make libc6-udeb
> to provide them, it seems udpkg supports that. The only packages having
> a dependency on libnss-files-udeb are espeakup-udeb, rdnssd-udeb,
> open-iscsi and openssh-client-udeb, and none of them has a versioned
> dependency. None of the udeb have a dependency on libnss-files-udeb.
> 
> Any opinion on that?

It sounds like a good idea to me. :)

Kind regards
Philipp Kern



Merging libnss-dns-udeb and libnss-files-udeb back into libc6-udeb

2016-03-12 Thread Aurelien Jarno
Hi,

For historical reason, disk space on boot floppies, the libnss_dns.so.2 
and libnss_files.so.2 libraries are in separate udeb packages, namely
libnss-dns-udeb and libnss-files-udeb. This is not the case of the deb
package, where everything is in the libc6 package.

In practice these libraries are really small by nowadays standards (22kB
and 47kB uncompressed), and moreover libnss-dns-udeb is already included 
in all images. In addition these libraries are tightly coupled to the
libresolv library which is in libc6-udeb. The recent CVE-2015-7547 has
shown that, and Ubuntu hit a bug by having the two out of sync in their
installer [1]. We would have got the same if debian-installer was pulling
its udeb from debian-security.

That's why I would like to propose to merge back libnss-dns-udeb and
libnss-files-udeb back into libc6-udeb. The idea is to make libc6-udeb
to provide them, it seems udpkg supports that. The only packages having
a dependency on libnss-files-udeb are espeakup-udeb, rdnssd-udeb,
open-iscsi and openssh-client-udeb, and none of them has a versioned
dependency. None of the udeb have a dependency on libnss-files-udeb.

Any opinion on that?

Thanks,
Aurelien

[1] https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1546459

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: PGP signature


Bug#266702: marked as done (want development task back)

2015-05-08 Thread Debian Bug Tracking System
Your message dated Sat, 9 May 2015 00:25:11 +0200
with message-id 20150508222511.ga12...@mraw.org
and subject line Re: Bug#266702: tasksel: want development task back
has caused the Debian Bug report #266702,
regarding want development task back
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.)


-- 
266702: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=266702
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: installation-reports

Debian-installer-version: 8/18/2004  RC1
uname -a: Linux
Date: 8/18/2004   11:30 AM
Method: NetInst  What did you boot off?  CDRom

Machine: Dell Inspiron 4000
Processor: PIII
Memory: 256Mb
Root Device: /dev/hda3
Root Size/partition table: 19.5 Mb
Output of lspci:

Base System Installation Checklist:

Initial boot worked:[O]
Configure network HW:   [O]
Config network: [O]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Create file systems:[O]
Mount partitions:   [O]
Install base system:[O]
Install boot loader:[O]
Reboot: [O]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Comments/Problems:

I note that in this version (possibly before), the method of selecting 
packages to install changed. It used to be possible to select by broad 
category (development, etc). I miss this. I'm now left with a much more 
tedious installation of routines that I used to be able to bulk select.

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

iD8DBQFBI6bHjeziQOokQnARAkrfAJ404QpgRbxjJGNHIPqKxdcvETBTcgCfe92y
cb7Arp6AqiHxCQh8tadtc7Q=
=K5xw
-END PGP SIGNATURE-

---End Message---
---BeginMessage---
Hello,

Jason Harrison jharri...@linuxbs.org (2004-08-22):
 Greetings,
 
 There use to be a development section where you could choose c/c++
 devleopment, python development etc.  Now this option is gone and to
 install the range of development tools that I use to use these tasks for
 is more tedious and difficult.  If you dont want to put the option back
 perhaps a list of packages that were in the development option could be
 provided?  Thank you for all the good work you guys do it is much
 appreciated.

I don't see this task coming back, so closing this bug report accordingly.

Mraw,
KiBi.


signature.asc
Description: Digital signature
---End Message---


Bug#759657: console-setup: problem back

2015-04-28 Thread Karsten Hilbert
Package: console-setup
Version: 1.123
Followup-For: Bug #759657

This problem is back: it hasn't happened since I added the wait4udev
thing but today it came back.

Karsten


-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 
'oldstable-updates'), (500, 'stable'), (500, 'oldstable'), (50, 'unstable'), 
(10, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.19.0-trunk-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages console-setup depends on:
ii  console-setup-linux 1.123
ii  debconf 1.5.56
ii  keyboard-configuration  1.123
ii  xkb-data2.12-1

console-setup recommends no packages.

Versions of packages console-setup suggests:
ii  locales2.19-18
ii  locales-all [locales]  2.19-18
ii  lsb-base   4.1+Debian13+nmu1

Versions of packages keyboard-configuration depends on:
ii  debconf 1.5.56
ii  initscripts 2.88dsf-59
ii  liblocale-gettext-perl  1.05-8+b1

Versions of packages console-setup-linux depends on:
ii  kbd 1.15.5-2
ii  keyboard-configuration  1.123

console-setup-linux suggests no packages.

Versions of packages console-setup is related to:
pn  console-common  none
pn  console-datanone
pn  console-tools   none
ii  kbd 1.15.5-2

-- debconf information:
  keyboard-configuration/xkb-keymap: de(nodeadkeys)
  console-setup/fontsize-text47: 8x16
  console-setup/framebuffer_only:
  keyboard-configuration/ctrl_alt_bksp: false
  keyboard-configuration/unsupported_options: true
  keyboard-configuration/modelcode: pc105
  keyboard-configuration/store_defaults_in_debconf_db: true
  keyboard-configuration/layout:
  console-setup/use_system_font:
  keyboard-configuration/variantcode: nodeadkeys
  keyboard-configuration/switch: No temporary switch
  console-setup/fontsize: 8x16
  keyboard-configuration/optionscode:
  debian-installer/console-setup-udeb/title:
  console-setup/store_defaults_in_debconf_db: true
  keyboard-configuration/altgr: The default for the keyboard layout
  keyboard-configuration/toggle: No toggling
  console-setup/guess_font:
  keyboard-configuration/variant: Deutsch - Deutsch (ohne Akzenttasten)
  keyboard-configuration/model: Generische PC-Tastatur mit 105 Tasten (Intl)
* console-setup/charmap47: UTF-8
* console-setup/fontsize-fb47: 8x16
  keyboard-configuration/layoutcode: de
  keyboard-configuration/unsupported_layout: true
  keyboard-configuration/unsupported_config_options: true
  console-setup/codesetcode: Lat15
  keyboard-configuration/compose: No compose key
  keyboard-configuration/unsupported_config_layout: true
* console-setup/fontface47: Terminus
  keyboard-configuration/other:
* console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic 
languages


-- 
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/20150428072757.30757.6531.report...@hermes.hilbert.loc



Bug#775444: Issue warning if falling back to sha1

2015-01-15 Thread jnqnfe
Package: debootstrap
Tags: security patch

Patch attached to output warning if falling back to sha1.
commit 0911f1a8ba757a013e4c97e017634eb0ab746997
Author: jnqnfe jnq...@gmail.com
Date:   Thu Jan 15 19:22:17 2015 +

Issue warning if having to fall back to sha1

diff --git a/debootstrap b/debootstrap
index 3d45c9c..c383517 100755
--- a/debootstrap
+++ b/debootstrap
@@ -461,6 +461,7 @@ if [ -z $SHA_SIZE ]; then
SHA_SIZE=256
 fi
 if ! in_path sha${SHA_SIZE}sum  ! in_path sha${SHA_SIZE}; then
+   warning SHA_SIZE Cannot find binary for checking sha%s checksums, 
falling back to sha1 ${SHA_SIZE}
SHA_SIZE=1
 fi
 DEBOOTSTRAP_CHECKSUM_FIELD=SHA$SHA_SIZE


Re: Bug#770525: tasksel: Task selection menu does not have Go Back button

2014-11-22 Thread Samuel Thibault
Control: reassign -1 tasksel
Control: retitle -1 tasksel: Task selection menu does not have Go Back button

Samuel Thibault, le Sat 22 Nov 2014 02:43:54 +0100, a écrit :
 Samuel Thibault, le Sat 22 Nov 2014 02:34:40 +0100, a écrit :
  Package: tasksel
 
 Oops, sorry, I'm just realizing that in d-i it's called pkgsel.

Mmm, but it's really tasksel which is running, reassigning back to
tasksel.

Samuel


-- 
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/2014110045.gl12...@type.youpi.perso.aquilenet.fr



Processed: Re: Bug#770525: tasksel: Task selection menu does not have Go Back button

2014-11-22 Thread Debian Bug Tracking System
Processing control commands:

 reassign -1 tasksel
Bug #770525 [pkgsel] pkgsel: Task selection menu does not have Go Back button
Bug reassigned from package 'pkgsel' to 'tasksel'.
Ignoring request to alter found versions of bug #770525 to the same values 
previously set
Ignoring request to alter fixed versions of bug #770525 to the same values 
previously set
 retitle -1 tasksel: Task selection menu does not have Go Back button
Bug #770525 [tasksel] pkgsel: Task selection menu does not have Go Back button
Changed Bug title to 'tasksel: Task selection menu does not have Go Back 
button' from 'pkgsel: Task selection menu does not have Go Back button'

-- 
770525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770525
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.b770525.14166936528889.transcr...@bugs.debian.org



Bug#770525: tasksel: Task selection menu does not have Go Back button

2014-11-21 Thread Samuel Thibault
Package: tasksel
Version: 3.29
Severity: normal

Hello,

The Software selection d-i dialog does not have a Go Back button any
more, which is not convenient when one wants to tinker a bit debconf
before starting the long installing tasks step.

Samuel

-- System Information:
Debian Release: jessie/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), 
(500, 'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.17.0 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages tasksel depends on:
ii  apt 1.0.9.3
ii  cdebconf [debconf-2.0]  0.192
ii  debconf [debconf-2.0]   1.5.53
ii  liblocale-gettext-perl  1.05-8+b1
ii  perl-base   5.20.1-2
ii  tasksel-data3.29

tasksel recommends no packages.

tasksel suggests no packages.

-- debconf information excluded

-- 
Samuel
...
rv_ et Ctrl alt F2 pour aller sous console
rv_ mais c koi pour passer d'un bureau a un autre !
rv_ au fait c koi le raccourci pour passer d'un bureau a un autre 'question 
stupide
cycyx ça dépend du window manager et de ta conf
Firebird ce qui fonctionne toujours c'est CTRL-ALT-BCKSP
-:- SignOff rv_: #linuxfr (Read error: EOF from client)
-:- rv_ [~rv@217.11.166.169] has joined #linuxfr
rv_ Firebird: MEURT...


-- 
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/20141122013440.ga25...@type.youpi.perso.aquilenet.fr



Re: Bug#770525: pkgsel: Task selection menu does not have Go Back button

2014-11-21 Thread Samuel Thibault
Control: reassign -1 pkgsel
Control: retitle -1 pkgsel: Task selection menu does not have Go Back button

Samuel Thibault, le Sat 22 Nov 2014 02:34:40 +0100, a écrit :
 Package: tasksel

Oops, sorry, I'm just realizing that in d-i it's called pkgsel.

Samuel


-- 
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/20141122014354.ga5...@type.youpi.perso.aquilenet.fr



Processed: Re: Bug#770525: pkgsel: Task selection menu does not have Go Back button

2014-11-21 Thread Debian Bug Tracking System
Processing control commands:

 reassign -1 pkgsel
Bug #770525 [tasksel] tasksel: Task selection menu does not have Go Back 
button
Bug reassigned from package 'tasksel' to 'pkgsel'.
No longer marked as found in versions tasksel/3.29.
Ignoring request to alter fixed versions of bug #770525 to the same values 
previously set
 retitle -1 pkgsel: Task selection menu does not have Go Back button
Bug #770525 [pkgsel] tasksel: Task selection menu does not have Go Back button
Changed Bug title to 'pkgsel: Task selection menu does not have Go Back 
button' from 'tasksel: Task selection menu does not have Go Back button'

-- 
770525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770525
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.b770525.141662064222758.transcr...@bugs.debian.org



(almost) all daily builds back to successful!

2013-09-21 Thread Cyril Brulebois
Hi all,

Cyril Brulebois k...@debian.org (2013-09-20):
 Daily build aggregator debian-boot@lists.debian.org (2013-09-20):
  Debian installer build overview
  ---
  
  Failed or old builds: [ many ]
 
 We know there's apt's #723705, so I've decronned the build aggregator for now.

thankfully, apt developers quickly found out where the regression
reported in #723705 came from, and came up with a fix; apt was
uloaded[1] yesterday, and made it possible to build d-i on almost
all archs.

 1. http://packages.qa.debian.org/a/apt/news/20130920T151855Z.html


The only exceptions so far are:
 - biber/i386, which has old builds (19th of september), likely because
   of a recent issue on the buildd[2]. 
 - praetorius/powerpc, which fails to build the cdrom part, apparently
   because of that particular apt bug. I'm currently in touch with its
   maintainer to figure out what happened; likely the chroot was't
   automatically upgraded, and that's getting fixed. Before that, it
   spent 10+ days without daily builds, due to a full filesystem.

 2. https://lists.debian.org/debian-wb-team/2013/09/msg00029.html


I've recronned the daily aggregator (responsible for building up the
overview page[3]), and mail notifications based on that page should
come back as well as a consequence. [Oops, I've actually too slow
typing this mail, a notification went in already; cdimage-logs
should look better next time.]

 3. http://d-i.debian.org/daily-images/build-logs.html


As I've mentioned lately[4], I'll try to work on keeping more build
logs, and making them easier to massage to find where regressions
come from; along with fixing stats (a configuration file has some
prerequisites that weren't obeyed when architectures got updated,
so stats are meaningless).

 4. https://lists.debian.org/debian-boot/2013/09/msg00406.html


Mraw,
KiBi.


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130921104341.ga24...@mraw.org



Bug#600428: marked as done (trouble going back and forth in installation steps)

2013-08-30 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 00:24:06 +0200
with message-id 201308310024.32985.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #600428,
regarding trouble going back and forth in installation steps
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.)


-- 
600428: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports

Boot method: How did you boot the installer? CD? floppy? network? CD
Image version: Full URL to image you downloaded is best
http://cdimage.debian.org/debian-cd/5.0.6/i386/iso-cd/debian-506-i386-CD-1.iso
Date: Date and time of the install yesterday

Machine: Description of machine (eg, IBM Thinkpad R32) acer aspire 5732ZG
Processor: pentium dual core
Memory:
Partitions: df -Tl will do; the raw partition table is preferred

Output of lspci -knn (or lspci -nn):

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:  [O ]
Load installer modules: [O ]
Detect hard drives: [O ]
Partition hard drives:  [O/E ]
Install base system:[O ]
Clock/timezone setup:   [O ]
User/password setup:[O ]
Install tasks:  [O ]
Install boot loader:[E ]
Overall install:[ ]

Comments/Problems:

Description of the install, in prose, and any thoughts, comments
  and ideas you had during the initial install.  Graphical
install.Apart from not recognizing atheros AR8132 and
AR5B93 Ethernet and Wireless card automatically, the real problem was
this: I managed to correctly choose my USB Stick for automatic
partitioning as I wanted and went ahead sucessfully until installing
the bootloader, I wanted it on the USB Stick rather than harddrive,
and to make sure to choose the right device designation for it, I went
back to menu and entered Partition hard drives again to look it up,
that's when trouble commenced: when I went back to the menu, I
couldn't re-enter installing the boot loader and was kicked back to
partitioning hard drives, when I finally chose to re-write the
partition table in order to be let out of the circle, after doing so,
installing the bootloader set in automatically without any prompts
(probably because that's where I had interrupted the journey forward
in installation, *but* in fact I hadn't chosen where to put it yet!)
and terminated with an error message to the respect that it couldn't
be installed, sorry, can't be more precise, but I think there was not
much more info.  I abandoned installation.
---End Message---
---BeginMessage---
Hi,

thank you for submitting installation reports, much appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they were caused by broken hardware and/or
- they have been from a development phase where things were not stable and/or
- they are quite old (and thus likely fixed today) and/or
- moreinfo was asked and not given or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to 
close wishlist bugs.)

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - thats often better, as the bug log 
will be clearer and shorter and not contain cruft.


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
---End Message---


Re: [Pkg-sysvinit-devel] installation-manual: Should it suggests to switch to run level 1 and back?

2013-04-30 Thread Samuel Thibault
Petter Reinholdtsen, le Thu 18 Apr 2013 06:30:58 +0200, a écrit :
 [Samuel Thibault]
  Which way?  Do you think we can still provide a recipe to manage to
  get the system booted, or should we forget about it and tell the
  user to just fix the issue and reboot?
 
 I suspect it is best to tell users to just reboot, because those users
 able to recover without a reboot are unlikely to need the instructions
 in the installation manual.

Indeed.  I have changed the manual thusly.

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130430213816.gk5...@type.youpi.perso.aquilenet.fr



Re: [Pkg-sysvinit-devel] installation-manual: Should it suggests to switch to run level 1 and back?

2013-04-22 Thread Henrique de Moraes Holschuh
On Wed, 17 Apr 2013, Petter Reinholdtsen wrote:
 [Regid Ichira]
  1. AM I right that strictly speaking, there are cases where the
  `easiest way' will not work?
 
 Yes.  Any daemon started from within rcS.d/ will be killed by
 /etc/rc1.d/S01killprocs and not started again when switching to
 runlevels 2-5.  This is the reason why I have recommended to move all
 daemon starting out of rcS.d/ and into rc[2-5].d/.  There is a lot of
 work left to do before this is done.  Luckily there isn't that that
 many daemons started from rcS.d/, so in many installations, switching
 to runlevel 1 and back will work.

There's networking: it may start deamons that are required for the
connection to remain operational in the medium/long term (dhcp-client,
wpa-supplicant, etc).   These are all killed and not restarted when you
switch to runlevel 1.

-- 
  One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie. -- The Silicon Valley Tarot
  Henrique Holschuh


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130422170857.ga26...@khazad-dum.debian.net



Re: [Pkg-sysvinit-devel] installation-manual: Should it suggests to switch to run level 1 and back?

2013-04-17 Thread Samuel Thibault
Petter Reinholdtsen, le Wed 17 Apr 2013 00:26:39 +0200, a écrit :
  2. Should the installation manual be modified?
 
 Perhaps. :)

Which way?  Do you think we can still provide a recipe to manage to get
the system booted, or should we forget about it and tell the user to
just fix the issue and reboot?

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130417225712.gi7...@type.youpi.perso.aquilenet.fr



Re: [Pkg-sysvinit-devel] installation-manual: Should it suggests to switch to run level 1 and back?

2013-04-17 Thread Petter Reinholdtsen
[Samuel Thibault]
 Which way?  Do you think we can still provide a recipe to manage to
 get the system booted, or should we forget about it and tell the
 user to just fix the issue and reboot?

I suspect it is best to tell users to just reboot, because those users
able to recover without a reboot are unlikely to need the instructions
in the installation manual.  But I have not investigated the current
status about the number of daemons started from rcS.d/.

-- 
Happy hacking
Petter Reinholdtsen


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130418043058.gf12...@ulrik.uio.no



Re: [Pkg-sysvinit-devel] installation-manual: Should it suggests to switch to run level 1 and back?

2013-04-16 Thread Petter Reinholdtsen
[Regid Ichira]
 1. AM I right that strictly speaking, there are cases where the
 `easiest way' will not work?

Yes.  Any daemon started from within rcS.d/ will be killed by
/etc/rc1.d/S01killprocs and not started again when switching to
runlevels 2-5.  This is the reason why I have recommended to move all
daemon starting out of rcS.d/ and into rc[2-5].d/.  There is a lot of
work left to do before this is done.  Luckily there isn't that that
many daemons started from rcS.d/, so in many installations, switching
to runlevel 1 and back will work.

 2. Should the installation manual be modified?

Perhaps. :)

-- 
Happy hacking
Petter Reinholdtsen


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130416222639.gb12...@ulrik.uio.no



installation-manual: Should it suggests to switch to run level 1 and back?

2013-03-28 Thread Regid Ichira
  http://www.debian.org/releases/stable/i386/ch07s02.html.en is
section 7.2, Mounting encrypted volumes.  From Chapter 7, Booting Into
Your New Debian System.  
The following assumes that this section has no substantial changes
in the squeeze manual.

  Quoting the bottom of section 7.2:

  If any volume holding noncritical system files could not be
mounted (/usr or /var), the system should still boot and you
should be able to mount the volumes manually like in the
previous case. However, you will also need to (re)start any
services usually running in your default runlevel because it
is very likely that they were not started. The easiest way to
achieve this is by switching to the first runlevel and back by
entering

# init 1

at the shell prompt and pressing Control+D when asked for the
root password.

That qoutation doesn't fully match the following quote, which is taken
from the warnings section of man init(8):

 On a Debian system, entering runlevel 1 causes  all  processes
 to  be  killed  except  for kernel threads and the script that
 does the killing and other processes in  its  session.   As  a
 consequence  of  this, it isn't safe to return from runlevel 1
 to a multi-user runlevel: daemons that were  started  in  run-
 level S and are needed for normal operation are no longer run-
 ning.  The system should be rebooted.

1. AM I right that strictly speaking, there are cases where the
   `easiest way' will not work?
2. Should the installation manual be modified?


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130329012028.gc7...@nt1.in



Bug#688650: debian-installer: Wrong IP added to interfaces config file if you go back to network setup menu

2012-09-24 Thread Juliano Jeziorny
Package: debian-installer
Version: 20110106+squeeze4+b1
Severity: normal

During the install you setup the IP informatio manually, then if you go back to 
the network setup screen and change the IP information the install doesn't add 
the new IP to the interfaces file, instead it creates the file with the OLD IP 
that was entered.


-- System Information:
Debian Release: 6.0.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120924144159.1260.72912.reportbug@test2



Bug#636211: marked as done (netcfg: Enter the passphrase for WPA PSK missing a go back button)

2012-06-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Jun 2012 06:02:31 +
with message-id e1sfpc7-0006m5...@franck.debian.org
and subject line Bug#636211: fixed in netcfg 1.71
has caused the Debian Bug report #636211,
regarding netcfg: Enter the passphrase for WPA PSK missing a go back button
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.)


-- 
636211: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636211
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: netcfg
Version: 1.66
Severity: normal

Hello,

I tried to use the freshly uploaded WPA support. However, my network
uses a two-phase authentication (anonymous then radius), so the Enter
the passphrase for WPA PSK question does not make sense here. Not
really a problem by itself (missing feature). But the problem is that
there is no go back button to go back to using e.g. eth0 instead of
wlan0.

Samuel

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.39-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

-- 
Samuel Thibault samuel.thiba...@fnac.net
* B kicks DW (non mais franchement)
* DW was kicked
 -+- #ens-mim - comment ça hopeless ? -+-


---End Message---
---BeginMessage---
Source: netcfg
Source-Version: 1.71

We believe that the bug you reported is fixed in the latest version of
netcfg, which is due to be installed in the Debian FTP archive:

netcfg-static_1.71_i386.udeb
  to main/n/netcfg/netcfg-static_1.71_i386.udeb
netcfg_1.71.dsc
  to main/n/netcfg/netcfg_1.71.dsc
netcfg_1.71.tar.gz
  to main/n/netcfg/netcfg_1.71.tar.gz
netcfg_1.71_i386.udeb
  to main/n/netcfg/netcfg_1.71_i386.udeb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 636...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christian Perrier bubu...@debian.org (supplier of updated netcfg package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 15 Jun 2012 07:22:39 +0200
Source: netcfg
Binary: netcfg netcfg-static
Architecture: source i386
Version: 1.71
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team debian-boot@lists.debian.org
Changed-By: Christian Perrier bubu...@debian.org
Description: 
 netcfg - Configure the network (udeb)
 netcfg-static - Configure a static network (udeb)
Closes: 636211 649747
Changes: 
 netcfg (1.71) unstable; urgency=low
 .
   * Team upload
 .
   [ Robert Millan ]
   * Ignore pfsync0, pflog0 and usbus0 devices on GNU/kFreeBSD.
   * Use 127.0.1.1 hack in /etc/hosts only on kernels that support it.
 (Closes: #649747)
 .
   [ Samuel Thibault ]
   * Also probe /dev/eth* and wl* on hurd-i386.
 .
   [ Sorina Sandu ]
   * Fix debconf backup capability handling.
 (Closes: #636211)
 .
   [ Aurelien Jarno ]
   * Add ppc64 to the Architecture field.
 .
   [ Updated translations ]
   * Amharic (am.po) by Tegegne Tefera
   * Arabic (ar.po) by Ossama Khayat
   * Asturian (ast.po) by Mikel González
   * Bulgarian (bg.po) by Damyan Ivanov
   * Bengali (bn.po) by Ayesha Akhtar
   * Tibetan (bo.po) by Tennom
   * Catalan (ca.po) by Jordi Mallach
   * Welsh (cy.po) by Dafydd Tomos
   * Danish (da.po) by Joe Hansen
   * German (de.po) by Holger Wansing
   * Greek, Modern (1453-) (el.po) by galaxico
   * Estonian (et.po) by Mattias Põldaru
   * Basque (eu.po) by Piarres Beobide
   * Finnish (fi.po) by Timo Jyrinki
   * Galician (gl.po) by Jorge Barreiro
   * Hebrew (he.po) by Omer Zak
   * Hungarian (hu.po) by SZERVÁC Attila
   * Indonesian (id.po) by Mahyuddin Susanto
   * Icelandic (is.po) by Sveinn í Felli
   * Italian (it.po) by Milo Casagrande
   * Central Khmer (km.po) by Khoem Sokhem
   * Kannada (kn.po) by Prabodh C P
   * Lao (lo.po) by Anousak Souphavanh
   * Lithuanian (lt.po) by Rimas Kudelis
   * Latvian (lv.po) by Rūdolfs Mazurs
   * Macedonian (mk.po) by Arangel Angov
   * Malayalam (ml.po) by Praveen Arimbrathodiyil
   * Marathi (mr.po) by sampada
   * Bokmål, Norwegian (nb.po) by Hans Fredrik Nordhaug
   * Dutch (nl.po) by Jeroen Schot
   * Panjabi (pa.po) by A S Alam

reassign 676001 back to initramfs-tools

2012-06-08 Thread Michael Tokarev
reassign 676001 initramfs-tools
thanks

Reassigning the bug back to initramfs-tools where it belongs
according to my comments below and lack of any arguments to
the opposite.  With all my dislike to such a ping-pong.

Thanks,

/mjt

On 05.06.2012 08:45, Michael Tokarev wrote:
[]
 I disagree it is a busybox problem, and don't think it is a
 switch_root business (be it from busybox or from util-linux).
 
 There are a few special directories which needs to be moved
 or umounted.  This includes /proc, /dev, /sys and not mentioned
 here /run.  These directories might be mounted in the new root
 already, or there may be some option passed to initramfs to
 not mount these, or there may be other local policy or whatever
 decisions.  All that can't be handled and can't be known to
 switch_root -- this is exactly why we have initramfs/init as
 a script, to be able to handle various local usecases/policies
 and made it extendable.
 
 Also, as shown by Vagrant in the initial bugreport, it is
 really trivial to fix it in initramfs.
 
 The fact that util-linux is doing this does not make it right
 thing to do.
 
 Why do you think it is a busybox bug?


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4fd19c52@msgid.tls.msk.ru



Processed: reassign 676001 back to initramfs-tools

2012-06-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 reassign 676001 initramfs-tools
Bug #676001 [busybox] initramfs-tools: busybox's switch_root doesn't handle 
/proc or /sys moving
Bug reassigned from package 'busybox' to 'initramfs-tools'.
Ignoring request to alter found versions of bug #676001 to the same values 
previously set
Ignoring request to alter fixed versions of bug #676001 to the same values 
previously set
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
676001: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676001
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: 
http://lists.debian.org/handler.s.c.133913710912651.transcr...@bugs.debian.org



kfreebsd-* d-i autobuilding back again

2012-05-17 Thread Christoph Egger
Hi all!

  The daily builds of d-i should now be back for both kfreebsd-
architectures. d-i.debian.org currently has binaries from my testrun ~2h
ago and should get feed by croned builds starting tonight.

Regards

Christoph

-- 
9FED 5C6C E206 B70A 5857  70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/874nrfaxb8@hepworth.siccegge.de



Re: kfreebsd-* d-i autobuilding back again

2012-05-17 Thread Steven Chamberlain
On 17/05/12 11:58, Christoph Egger wrote:
 The daily builds of d-i should now be back for both kfreebsd-
 architectures.

Hi Christoph,

Thanks a lot!  I can start testing these again.

Do you have any brief notes on what things you had to set up for this?
Or a link to some docs / Wiki page explaining this.  Just in case it
needs doing again or if someone else needs needs this for some new arch.

Thanks,
Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4fb4e2ce.2060...@pyro.eu.org



Re: kfreebsd-* d-i autobuilding back again

2012-05-17 Thread Christoph Egger
Steven Chamberlain ste...@pyro.eu.org writes:
 On 17/05/12 11:58, Christoph Egger wrote:
 The daily builds of d-i should now be back for both kfreebsd-
 architectures.

 Hi Christoph,

 Thanks a lot!  I can start testing these again.

 Do you have any brief notes on what things you had to set up for this?
 Or a link to some docs / Wiki page explaining this.  Just in case it
 needs doing again or if someone else needs needs this for some new arch.

It's documented in the README + script from [0]. Though you'll need
someone with access to the respective buildds for setup.

Regards

Christoph

[0] https://buildd.debian.org/git/di-autobuild.git/
-- 
9FED 5C6C E206 B70A 5857  70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87obpn9g36@hepworth.siccegge.de



Bug#636211: netcfg: Enter the passphrase for WPA PSK missing a go back button (Was: about bug #636211)

2012-04-07 Thread Samuel Thibault
Hello,

Please always include useful keywords in the Subject. We don't know bug
numbers by heart. Also always include the bug in Cc, it's better to
record too much information than too little.

Mesutcan Kurt, le Tue 03 Apr 2012 18:40:12 +0300, a écrit :
 I found bug #636211 [1] but I can't reproduce the problem. When I looked at 
 the
 source code there should be a back button.

But for some reason it's not shown on the screen, that's where
investigation is needed.

 Maybe request is for going back to interface select menu when back
 button is selected.

For instance, yes. Anything that is back, even if it's step by step
(WEP vs WPA, ESSID, then eventually interface selection). I've just
retried today's netboot image, and all these dialogs are missing a
back button:

- interface selection
- ESSID
- encryption type (WEP vs WPA)
- passphrase

Samuel



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120407233508.GB4149@type



Bug#636211: netcfg: Enter the passphrase for WPA PSK missing a go back button

2011-08-01 Thread Samuel Thibault
Package: netcfg
Version: 1.66
Severity: normal

Hello,

I tried to use the freshly uploaded WPA support. However, my network
uses a two-phase authentication (anonymous then radius), so the Enter
the passphrase for WPA PSK question does not make sense here. Not
really a problem by itself (missing feature). But the problem is that
there is no go back button to go back to using e.g. eth0 instead of
wlan0.

Samuel

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.39-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

-- 
Samuel Thibault samuel.thiba...@fnac.net
* B kicks DW (non mais franchement)
* DW was kicked
 -+- #ens-mim - comment ça hopeless ? -+-



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110801125313.ga16...@const.bordeaux.inria.fr



Bug#453661: marked as done (auto-install: Falling back to the package description)

2011-05-01 Thread Debian Bug Tracking System
Your message dated Sun, 01 May 2011 18:42:47 +
with message-id e1qgbbt-000448...@franck.debian.org
and subject line Bug#624719: Removed package(s) from unstable
has caused the Debian Bug report #453661,
regarding auto-install: Falling back to the package description
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.)


-- 
453661: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=453661
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: auto-install
Version: 1.2
Severity: normal

Hello,

In the install log are many lines like:

Nov 16 16:33:27 main-menu[1139]: INFO: Falling back to the package description 
for auto-install 
Nov 16 16:38:50 main-menu[1139]: INFO: Falling back to the package description 
for auto-install 
Nov 16 16:42:24 main-menu[1139]: INFO: Falling back to the package description 
for auto-install 

It would be nice if they could be avoided.


Cheers
Geert Stappers



---End Message---
---BeginMessage---
Version: 1.9+rm

Dear submitter,

as the package auto-install has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see http://bugs.debian.org/624719

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@debian.org.

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl (the ftpmaster behind the curtain)

---End Message---


Bug#616315: cdebconf in d-i via serial hides the option to go back

2011-03-10 Thread Ferenc Wagner
Miguel Figueiredo el...@debianpt.org writes:

 New proposal for the messages.

You still don't seem to handle the case when going back isn't
supported.  Is that entirely forbidden in the installer?
-- 
Regards,
Feri.



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87ei6fxmtn@tac.ki.iif.hu



Bug#616315: cdebconf in d-i via serial hides the option to go back

2011-03-10 Thread Christian PERRIER
Quoting Miguel Figueiredo (el...@debianpt.org):

 New proposal for the messages.

I ack'ed them on IRC. This mail just for the record.




signature.asc
Description: Digital signature


Bug#616315: cdebconf in d-i via serial hides the option to go back

2011-03-10 Thread Otavio Salvador
On Thu, Mar 10, 2011 at 11:00, Ferenc Wagner wf...@niif.hu wrote:
 Miguel Figueiredo el...@debianpt.org writes:

 New proposal for the messages.

 You still don't seem to handle the case when going back isn't
 supported.  Is that entirely forbidden in the installer?

Miguel,

Take a look on Joey comment about it not being support in case it has
backup disabled. It needs to support both behaviours.

-- 
Otavio Salvador                             O.S. Systems
E-mail: ota...@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/AANLkTi=ozkc-zzr8ka9ne14gbyckv008on54+wm8d...@mail.gmail.com



Bug#616315: cdebconf in d-i via serial hides the option to go back

2011-03-10 Thread Miguel Figueiredo
Hi all,

now i have created messages for systems that support 'go back' and conditions 
to deal with it.
I tested the udebs installing on a kvm and i get a text mode installer with 
the 'go back' in the prompt.

-- 
Melhores cumprimentos/Best regards,

Miguel Figueiredo
http://www.DebianPT.org
diff --git a/debian/cdebconf-text-udeb.templates b/debian/cdebconf-text-udeb.templates
index 3a960a7..9ec836b 100644
--- a/debian/cdebconf-text-udeb.templates
+++ b/debian/cdebconf-text-udeb.templates
@@ -36,17 +36,32 @@ _Description: No
 Template: debconf/text-prompt-default
 Type: text
 # :sl4:
-_Description: Prompt: '%c' for help, default=%d 
+_Description: Prompt: '%c': help, default: '%d' 
+
+Template: debconf/text-prompt-default-goback
+Type: text
+# :sl4:
+_Description: Prompt: '%c': help, '%c': go back, default: '%d' 
 
 Template: debconf/text-prompt
 Type: text
 # :sl4:
-_Description: Prompt: '%c' for help 
+_Description: Prompt: '%c': help 
+
+Template: debconf/text-prompt-goback
+Type: text
+# :sl4:
+_Description: Prompt: '%c': help, '%c': go back 
 
 Template: debconf/text-prompt-default-string
 Type: text
 # :sl4:
-_Description: Prompt: '%c' for help, default=%s 
+_Description: Prompt: '%c': help, default: '%s' 
+
+Template: debconf/text-prompt-default-string-goback
+Type: text
+# :sl4:
+_Description: Prompt: '%c': help, '%c': go back, default: '%s' 
 
 Template: debconf/cont-prompt
 Type: text
diff --git a/debian/changelog b/debian/changelog
index 6f33413..f21a0e0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,5 +1,9 @@
 cdebconf (0.155) UNRELEASED; urgency=low
 
+  [ Miguel Figueiredo]
+  * Add go back to prompt on text install. Closes: #616315.
+  
+  [ Colin Watson ]
   * Appease compiler warnings in align_text_renderer_render.  (In practice
 x_offset and y_offset are never uninitialised here, but knowing that
 requires knowing that cell_area can never be NULL.)
diff --git a/src/modules/frontend/text/text.c b/src/modules/frontend/text/text.c
index db4988d..918b3f2 100644
--- a/src/modules/frontend/text/text.c
+++ b/src/modules/frontend/text/text.c
@@ -343,11 +343,27 @@ static int text_handler_boolean(struct frontend *obj, struct question *q)
 		printf(  %d. %s%s, 2, question_get_text(obj, debconf/no, No), (2 == def ?  [*] : ));
 		printf(\n);
 		if (def)
-			printf(question_get_text(obj, debconf/text-prompt-default,
-	Prompt: '%c' for help, default=%d ), CHAR_HELP, def);
+		{
+			if (obj-methods.can_go_back (obj, q)) 
+printf(question_get_text(obj, debconf/text-prompt-default-goback, 
+	Prompt: '%c': help, '%c': go back, default: '%d' ), 
+	CHAR_HELP, CHAR_GOBACK, def);
+			else
+printf(question_get_text(obj, debconf/text-prompt-default, 
+	Prompt: '%c': help, default: '%d' ), 
+	CHAR_HELP, def);
+		} 
 		else
-			printf(question_get_text(obj, debconf/text-prompt,
-	Prompt: '%c' for help ), CHAR_HELP);
+		{
+			if (obj-methods.can_go_back (obj, q)) 
+printf(question_get_text(obj, debconf/text-prompt-goback, 
+	Prompt: '%c': help, '%c': go back ), 
+	CHAR_HELP, CHAR_GOBACK);
+			else
+printf(question_get_text(obj, debconf/text-prompt, 
+	Prompt: '%c': help ), 
+	CHAR_HELP);		
+		}
 		get_answer(buf, sizeof(buf));
 		if (buf[0] == CHAR_HELP  buf[1] == 0)
 			show_help(obj, q);
@@ -430,8 +446,14 @@ static int text_handler_multiselect(struct frontend *obj, struct question *q)
 
   DISPLAY:
 	printlist (obj, q, count, choices_translated, tindex, selected);
-	printf(question_get_text(obj, debconf/text-prompt-default-string, 
-		Prompt: '%c' for help, default=%s ), CHAR_HELP, defval);
+	if (obj-methods.can_go_back (obj, q)) 	
+		printf(question_get_text(obj, debconf/text-prompt-default-string-goback, 
+			Prompt: '%c': help, '%c': go back, default: '%s' ), 
+			CHAR_HELP, CHAR_GOBACK, defval);
+	else
+		printf(question_get_text(obj, debconf/text-prompt-default-string, 
+			Prompt: '%c': help, default: '%s' ), 
+			CHAR_HELP, defval);
 	get_answer(answer, sizeof(answer));
 	if (answer[0] == CHAR_HELP  answer[1] == 0)
 	{
@@ -549,13 +571,27 @@ static int text_handler_select(struct frontend *obj, struct question *q)
 	choice = -1;
 	do {
 		printlist (obj, q, count, choices_translated, tindex, selected);
-		if (def = 0  choices_translated[def]) {
-			printf(question_get_text(obj, debconf/text-prompt-default, 
-Prompt: '%c' for help, default=%d ),
+		if (def = 0  choices_translated[def]) 
+		{
+			if (obj-methods.can_go_back (obj, q))
+printf(question_get_text(obj, debconf/text-prompt-default-goback, 
+	Prompt: '%c' for help, '%c' go back, default: '%d' ), 
+	CHAR_HELP, CHAR_GOBACK, def+1);
+			else
+printf(question_get_text(obj, debconf/text-prompt-default, 
+	Prompt: '%c' for help, default: '%d' ), 
 	CHAR_HELP, def+1);
-		} else {
-			printf(question_get_text(obj, debconf/text-prompt,
-Prompt: '%c' for help ), CHAR_HELP);
+		} 
+		else 
+		{
+			if (obj-methods.can_go_back (obj, q))
+printf

Bug#616315: cdebconf in d-i via serial hides the option to go back

2011-03-09 Thread Miguel Figueiredo
Hi all,

A Sábado 05 Março 2011 10:20:11 Christian PERRIER você escreveu:

 There are a few inconsistencies in spaces:

[...]

 Is the difference between %s and %d needed. That adds an extra string
 to translate.

New proposal for the messages.

-- 
Melhores cumprimentos/Best regards,

Miguel Figueiredo
http://www.DebianPT.org
diff --git a/debian/cdebconf-text-udeb.templates b/debian/cdebconf-text-udeb.templates
index 3a960a7..84e0174 100644
--- a/debian/cdebconf-text-udeb.templates
+++ b/debian/cdebconf-text-udeb.templates
@@ -36,17 +36,17 @@ _Description: No
 Template: debconf/text-prompt-default
 Type: text
 # :sl4:
-_Description: Prompt: '%c' for help, default=%d 
+_Description: Prompt: '%c': help, '%c': go back, default: '%d' 
 
 Template: debconf/text-prompt
 Type: text
 # :sl4:
-_Description: Prompt: '%c' for help 
+_Description: Prompt: '%c': help, '%c': go back 
 
 Template: debconf/text-prompt-default-string
 Type: text
 # :sl4:
-_Description: Prompt: '%c' for help, default=%s 
+_Description: Prompt: '%c': help, '%c': go back, default: '%s' 
 
 Template: debconf/cont-prompt
 Type: text
diff --git a/debian/changelog b/debian/changelog
index 6f33413..f21a0e0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,5 +1,9 @@
 cdebconf (0.155) UNRELEASED; urgency=low
 
+  [ Miguel Figueiredo]
+  * Add go back to prompt on text install. Closes: #616315.
+  
+  [ Colin Watson ]
   * Appease compiler warnings in align_text_renderer_render.  (In practice
 x_offset and y_offset are never uninitialised here, but knowing that
 requires knowing that cell_area can never be NULL.)
diff --git a/src/modules/frontend/text/text.c b/src/modules/frontend/text/text.c
index db4988d..5cf9fa5 100644
--- a/src/modules/frontend/text/text.c
+++ b/src/modules/frontend/text/text.c
@@ -344,10 +344,10 @@ static int text_handler_boolean(struct frontend *obj, struct question *q)
 		printf(\n);
 		if (def)
 			printf(question_get_text(obj, debconf/text-prompt-default,
-	Prompt: '%c' for help, default=%d ), CHAR_HELP, def);
+	Prompt: '%c': help, '%c': go back, default: '%d' ), CHAR_HELP, CHAR_GOBACK, def);
 		else
 			printf(question_get_text(obj, debconf/text-prompt,
-	Prompt: '%c' for help ), CHAR_HELP);
+	Prompt: '%c': help, '%c': go back ), CHAR_HELP, CHAR_GOBACK);
 		get_answer(buf, sizeof(buf));
 		if (buf[0] == CHAR_HELP  buf[1] == 0)
 			show_help(obj, q);
@@ -431,7 +431,7 @@ static int text_handler_multiselect(struct frontend *obj, struct question *q)
   DISPLAY:
 	printlist (obj, q, count, choices_translated, tindex, selected);
 	printf(question_get_text(obj, debconf/text-prompt-default-string, 
-		Prompt: '%c' for help, default=%s ), CHAR_HELP, defval);
+		Prompt: '%c': help, '%c': go back, default: '%s' ), CHAR_HELP, CHAR_GOBACK, defval);
 	get_answer(answer, sizeof(answer));
 	if (answer[0] == CHAR_HELP  answer[1] == 0)
 	{
@@ -551,11 +551,11 @@ static int text_handler_select(struct frontend *obj, struct question *q)
 		printlist (obj, q, count, choices_translated, tindex, selected);
 		if (def = 0  choices_translated[def]) {
 			printf(question_get_text(obj, debconf/text-prompt-default, 
-Prompt: '%c' for help, default=%d ),
-	CHAR_HELP, def+1);
+Prompt: '%c' for help, '%c' go back, default: '%d' ),
+	CHAR_HELP, CHAR_GOBACK, def+1);
 		} else {
 			printf(question_get_text(obj, debconf/text-prompt,
-Prompt: '%c' for help ), CHAR_HELP);
+Prompt: '%c' for help, '%c' go back ), CHAR_HELP, CHAR_GOBACK);
 		}
 		get_answer(answer, sizeof(answer));
 		if (answer[0] == CHAR_HELP)
@@ -687,9 +687,9 @@ static int text_handler_string(struct frontend *obj, struct question *q)
 	const char *defval = question_getvalue(q, );
 	while (1) {
 		if (defval)
-			printf(question_get_text(obj, debconf/text-prompt-default-string, Prompt: '%c' for help, default=%s ), CHAR_HELP, defval);
+			printf(question_get_text(obj, debconf/text-prompt-default-string, Prompt: '%c' for help, '%c' go back, default: '%s' ), CHAR_HELP, CHAR_GOBACK, defval);
 		else
-			printf(question_get_text(obj, debconf/text-prompt, Prompt: '%c' for help ), CHAR_HELP);
+			printf(question_get_text(obj, debconf/text-prompt, Prompt: '%c' for help, '%c' go back ), CHAR_HELP, CHAR_GOBACK);
 		fflush(stdout);
 		get_answer(buf, sizeof(buf));
 		if (buf[0] == CHAR_HELP  buf[1] == 0)


Bug#616315: cdebconf in d-i via serial hides the option to go back

2011-03-05 Thread Christian PERRIER
Quoting Miguel Figueiredo (el...@debianpt.org):

  Prompt: '%c': help, '%c': go back, default: '%d'
 
 Here it goes the patch with Christian's suggestion.

There are a few inconsistencies in spaces:


 -_Description: Prompt: '%c' for help, default=%d 
 +_Description: Prompt: '%c': help, '%c': go back, default: '%d' 
   ^

 -_Description: Prompt: '%c' for help, default=%s 
 +_Description: Prompt: '%c': help, '%c': go back, default:'%s' 
^^

Is the difference between %s and %d needed. That adds an extra string
to translate.




signature.asc
Description: Digital signature


Bug#616315: cdebconf in d-i via serial hides the option to go back

2011-03-04 Thread Miguel Figueiredo
Hi,

A Sexta 04 Março 2011 07:26:25 Christian PERRIER você escreveu:
 Quoting Miguel Figueiredo (el...@debianpt.org):
  -_Description: Prompt: '%c' for help, default=%d
  +_Description: Prompt: '%c' for help, '%c' go back, default=%d
 
 The text could also be (shorter and imho more consistent):
 
 Prompt: '%c': help, '%c': go back, default: '%d'

Here it goes the patch with Christian's suggestion.

-- 
Melhores cumprimentos/Best regards,

Miguel Figueiredo
http://www.DebianPT.org
diff --git a/debian/cdebconf-text-udeb.templates b/debian/cdebconf-text-udeb.templates
index 3a960a7..487786e 100644
--- a/debian/cdebconf-text-udeb.templates
+++ b/debian/cdebconf-text-udeb.templates
@@ -36,17 +36,17 @@ _Description: No
 Template: debconf/text-prompt-default
 Type: text
 # :sl4:
-_Description: Prompt: '%c' for help, default=%d 
+_Description: Prompt: '%c': help, '%c': go back, default: '%d' 
 
 Template: debconf/text-prompt
 Type: text
 # :sl4:
-_Description: Prompt: '%c' for help 
+_Description: Prompt: '%c': help, '%c': go back 
 
 Template: debconf/text-prompt-default-string
 Type: text
 # :sl4:
-_Description: Prompt: '%c' for help, default=%s 
+_Description: Prompt: '%c': help, '%c': go back, default:'%s' 
 
 Template: debconf/cont-prompt
 Type: text
diff --git a/debian/changelog b/debian/changelog
index 6f33413..f21a0e0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,5 +1,9 @@
 cdebconf (0.155) UNRELEASED; urgency=low
 
+  [ Miguel Figueiredo]
+  * Add go back to prompt on text install. Closes: #616315.
+  
+  [ Colin Watson ]
   * Appease compiler warnings in align_text_renderer_render.  (In practice
 x_offset and y_offset are never uninitialised here, but knowing that
 requires knowing that cell_area can never be NULL.)
diff --git a/src/modules/frontend/text/text.c b/src/modules/frontend/text/text.c
index db4988d..2b3d4c2 100644
--- a/src/modules/frontend/text/text.c
+++ b/src/modules/frontend/text/text.c
@@ -344,10 +344,10 @@ static int text_handler_boolean(struct frontend *obj, struct question *q)
 		printf(\n);
 		if (def)
 			printf(question_get_text(obj, debconf/text-prompt-default,
-	Prompt: '%c' for help, default=%d ), CHAR_HELP, def);
+	Prompt: '%c': help, '%c': go back, default:'%d' ), CHAR_HELP, CHAR_GOBACK, def);
 		else
 			printf(question_get_text(obj, debconf/text-prompt,
-	Prompt: '%c' for help ), CHAR_HELP);
+	Prompt: '%c': help, '%c': go back ), CHAR_HELP, CHAR_GOBACK);
 		get_answer(buf, sizeof(buf));
 		if (buf[0] == CHAR_HELP  buf[1] == 0)
 			show_help(obj, q);
@@ -431,7 +431,7 @@ static int text_handler_multiselect(struct frontend *obj, struct question *q)
   DISPLAY:
 	printlist (obj, q, count, choices_translated, tindex, selected);
 	printf(question_get_text(obj, debconf/text-prompt-default-string, 
-		Prompt: '%c' for help, default=%s ), CHAR_HELP, defval);
+		Prompt: '%c': help, '%c': go back, default:'%s' ), CHAR_HELP, CHAR_GOBACK, defval);
 	get_answer(answer, sizeof(answer));
 	if (answer[0] == CHAR_HELP  answer[1] == 0)
 	{
@@ -551,11 +551,11 @@ static int text_handler_select(struct frontend *obj, struct question *q)
 		printlist (obj, q, count, choices_translated, tindex, selected);
 		if (def = 0  choices_translated[def]) {
 			printf(question_get_text(obj, debconf/text-prompt-default, 
-Prompt: '%c' for help, default=%d ),
-	CHAR_HELP, def+1);
+Prompt: '%c' for help, '%c' go back, default=%d ),
+	CHAR_HELP, CHAR_GOBACK, def+1);
 		} else {
 			printf(question_get_text(obj, debconf/text-prompt,
-Prompt: '%c' for help ), CHAR_HELP);
+Prompt: '%c' for help, '%c' go back ), CHAR_HELP, CHAR_GOBACK);
 		}
 		get_answer(answer, sizeof(answer));
 		if (answer[0] == CHAR_HELP)
@@ -687,9 +687,9 @@ static int text_handler_string(struct frontend *obj, struct question *q)
 	const char *defval = question_getvalue(q, );
 	while (1) {
 		if (defval)
-			printf(question_get_text(obj, debconf/text-prompt-default-string, Prompt: '%c' for help, default=%s ), CHAR_HELP, defval);
+			printf(question_get_text(obj, debconf/text-prompt-default-string, Prompt: '%c' for help, '%c' go back, default=%s ), CHAR_HELP, CHAR_GOBACK, defval);
 		else
-			printf(question_get_text(obj, debconf/text-prompt, Prompt: '%c' for help ), CHAR_HELP);
+			printf(question_get_text(obj, debconf/text-prompt, Prompt: '%c' for help, '%c' go back ), CHAR_HELP, CHAR_GOBACK);
 		fflush(stdout);
 		get_answer(buf, sizeof(buf));
 		if (buf[0] == CHAR_HELP  buf[1] == 0)


Bug#616315: cdebconf in d-i via serial hides the option to go back

2011-03-03 Thread Ian Jackson
Package: cdebconf-text-udeb
Version: 0.154

When running the squeeze installer via a serial console there should
be something in the prompt to tell you that you can go back; you
shouldn't have to read the help to know this.

The help is very long and go back is an important option.

Also I'm not convinced that having the go back option presented in
the help text only when it's available is a good idea.  I got the help
text from one prompt, which happened to be one which didn't have a go
back option, and that gave me the idea that it just wasn't possible.

In case it's of any use, attached is a transcript of me struggling
with it, before I got helpful advice on IRC to try .

Thanks,
Ian.

Mar  3 12:10:22.099451 Partitions formatting  ..33%
Mar  3 12:10:22.319420 !! ERROR: Failed to create a file system
Mar  3 12:10:22.331027 
Mar  3 12:10:22.331061 The ext3 file system creation in partition #1 of 
SCSI.CCISS (-,0,0) 
Mar  3 12:10:22.331127 (cciss/c0d0) failed.
Mar  3 12:10:22.335007 [Press enter to continue] 
Mar  3 12:18:27.714182 
Mar  3 12:18:27.714251 Starting up the partitioner  
..13%..22%..31%..40%..50%..63%..72%..81%..90%..100%
Mar  3 12:18:29.413851 This is an overview of your currently configured 
partitions and mount points. 
Mar  3 12:18:29.850330 Select a partition to modify its settings (file system, 
mount point, etc.), a 
Mar  3 12:18:29.862297 free space to create partitions, or a device to 
initialize its partition table.
Mar  3 12:18:29.874280   1. Guided partitioning
Mar  3 12:18:29.874330   2. Configure software RAID
Mar  3 12:18:29.874377   3. Configure the Logical Volume Manager
Mar  3 12:18:29.882277   4. Configure encrypted volumes
Mar  3 12:18:29.882329   5. 
Mar  3 12:18:29.882369   6. SCSI.CCISS (-,0,0) (cciss/c0d0) - 293.6 GB Compaq 
Smart Array
Mar  3 12:18:29.894281   7.  #1  primary  289.4 GB  B  f  ext3/
 
Mar  3 12:18:29.894344   8.  #5  logical4.1 GB F  swapswap 
 
Mar  3 12:18:29.906286   9. SCSI.CCISS (-,0,1) (cciss/c0d1) - 146.7 GB Compaq 
Smart Array
Mar  3 12:18:29.906421  10.  #1  primary  146.7 GB K  lvm  
 
Mar  3 12:18:29.918292  11. LVM VG 
VG_XenStorage-ec0bf0e3-b890-46ec-3bc2-bbca85298bc0, LV MGT - 4.2 MB Linux 
device-mapper (linear)
Mar  3 12:18:29.926314  12.  #1 4.2 MB 
 
Mar  3 12:18:29.926374  13. LVM VG 
VG_XenStorage-ec0bf0e3-b890-46ec-3bc2-bbca85298bc0, LV 
VHD-02b643ff-2044-42fc-b617-cf9a76f38270 - 25.8 GB Linux device-mapper (linear) 
   
Mar  3 12:18:29.950295  14.  #125.8 GB 
 
Mar  3 12:18:29.950358  15. LVM VG 
VG_XenStorage-ec0bf0e3-b890-46ec-3bc2-bbca85298bc0, LV 
VHD-08b420b5-6f61-47b2-85d0-1792d866678e - 16.8 MB Linux device-mapper (linear) 
   
Mar  3 12:18:29.969880  16.  #116.8 MB 
 
Mar  3 12:18:29.969942  17. LVM VG 
VG_XenStorage-ec0bf0e3-b890-46ec-3bc2-bbca85298bc0, LV 
VHD-148b1a50-0a2f-43ba-9430-8c1320195645 - 25.8 GB Linux device-mapper (linear) 
   
Mar  3 12:18:29.981944  18.  #125.8 GB 
 
Mar  3 12:18:29.994302  19. LVM VG 
VG_XenStorage-ec0bf0e3-b890-46ec-3bc2-bbca85298bc0, LV 
VHD-375de72f-c6de-46b6-bf52-fc01b598d4e8 - 25.8 GB Linux device-mapper (linear) 
   
Mar  3 12:18:30.002344  20.  #125.8 GB 
 
Mar  3 12:18:30.014291  21. LVM VG 
VG_XenStorage-ec0bf0e3-b890-46ec-3bc2-bbca85298bc0, LV 
VHD-3ebfc933-1b27-4b39-9c0f-fff57b37d929 - 25.8 GB Linux device-mapper (linear) 
   
Mar  3 12:18:30.026333  22.  #125.8 GB 
 
Mar  3 12:18:30.034298  23. LVM VG 
VG_XenStorage-ec0bf0e3-b890-46ec-3bc2-bbca85298bc0, LV 
VHD-4580d30e-7c83-4f29-a684-0bf6a9f50d0b - 21.5 GB Linux device-mapper (linear) 
   
Mar  3 12:18:30.046314  24.  #121.5 GB 
 
Mar  3 12:18:30.058286  25. LVM VG 
VG_XenStorage-ec0bf0e3-b890-46ec-3bc2-bbca85298bc0, LV 
VHD-61ad8a87-4e85-4679-ab4e-0b33f5b09d6f - 25.8 GB Linux device-mapper (linear) 
   
Mar  3 12:18:30.070308  26.  #125.8 GB 
 
Mar  3 12:18:30.070369  27. LVM VG 
VG_XenStorage-ec0bf0e3-b890-46ec-3bc2-bbca85298bc0, LV 
VHD-637d75dd-7217-4dcd-87f7-289da8f9b29c - 25.8 GB Linux device-mapper (linear) 
   
Mar  3 12:18:30.089903  28.  #125.8 GB 
 
Mar  3 12:18:30.089965  29. LVM VG 
VG_XenStorage-ec0bf0e3-b890-46ec-3bc2-bbca85298bc0, LV 
VHD-8fefd60a-e6c9-4ad9-9ef7-ed6c79caaec2 - 25.8 GB Linux device-mapper (linear) 
   
Mar  3 12:18:30.110088  30.  #125.8 GB 
 
Mar  3 12:18:30.110149  31. LVM VG 
VG_XenStorage-ec0bf0e3-b890-46ec-3bc2-bbca85298bc0, LV 
VHD-9368828d-3612-42f5-b429-bfee6c175d9a - 17.2 GB Linux device-mapper (linear) 
   
Mar  3 12:18:30.122360  32.  #117.2 GB 
 
Mar  3 12:18

Bug#616315: cdebconf in d-i via serial hides the option to go back

2011-03-03 Thread Miguel Figueiredo
Hi,

A Quinta 03 Março 2011 12:40:12 Ian Jackson você escreveu:
 Package: cdebconf-text-udeb
 Version: 0.154
 
 When running the squeeze installer via a serial console there should
 be something in the prompt to tell you that you can go back; you
 shouldn't have to read the help to know this.
 
 The help is very long and go back is an important option.
 
 Also I'm not convinced that having the go back option presented in
 the help text only when it's available is a good idea.  I got the help
 text from one prompt, which happened to be one which didn't have a go
 back option, and that gave me the idea that it just wasn't possible.
 
 In case it's of any use, attached is a transcript of me struggling
 with it, before I got helpful advice on IRC to try .
 
 Thanks,
 Ian.

In attachment a patch for cdebconf to be reviewed.

-- 
Melhores cumprimentos/Best regards,

Miguel Figueiredo
http://www.DebianPT.org
diff --git a/debian/cdebconf-text-udeb.templates b/debian/cdebconf-text-udeb.templates
index 3a960a7..8fe79dd 100644
--- a/debian/cdebconf-text-udeb.templates
+++ b/debian/cdebconf-text-udeb.templates
@@ -36,17 +36,17 @@ _Description: No
 Template: debconf/text-prompt-default
 Type: text
 # :sl4:
-_Description: Prompt: '%c' for help, default=%d 
+_Description: Prompt: '%c' for help, '%c' go back, default=%d 
 
 Template: debconf/text-prompt
 Type: text
 # :sl4:
-_Description: Prompt: '%c' for help 
+_Description: Prompt: '%c' for help, '%c' go back 
 
 Template: debconf/text-prompt-default-string
 Type: text
 # :sl4:
-_Description: Prompt: '%c' for help, default=%s 
+_Description: Prompt: '%c' for help, '%c' go back, default=%s 
 
 Template: debconf/cont-prompt
 Type: text
diff --git a/debian/changelog b/debian/changelog
index 6f33413..f21a0e0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,5 +1,9 @@
 cdebconf (0.155) UNRELEASED; urgency=low
 
+  [ Miguel Figueiredo]
+  * Add go back to prompt on text install. Closes: #616315.
+  
+  [ Colin Watson ]
   * Appease compiler warnings in align_text_renderer_render.  (In practice
 x_offset and y_offset are never uninitialised here, but knowing that
 requires knowing that cell_area can never be NULL.)
diff --git a/src/modules/frontend/text/text.c b/src/modules/frontend/text/text.c
index db4988d..92141a7 100644
--- a/src/modules/frontend/text/text.c
+++ b/src/modules/frontend/text/text.c
@@ -344,10 +344,10 @@ static int text_handler_boolean(struct frontend *obj, struct question *q)
 		printf(\n);
 		if (def)
 			printf(question_get_text(obj, debconf/text-prompt-default,
-	Prompt: '%c' for help, default=%d ), CHAR_HELP, def);
+	Prompt: '%c' for help, '%c' go back, default=%d ), CHAR_HELP, CHAR_GOBACK, def);
 		else
 			printf(question_get_text(obj, debconf/text-prompt,
-	Prompt: '%c' for help ), CHAR_HELP);
+	Prompt: '%c' for help, '%c' go back ), CHAR_HELP, CHAR_GOBACK);
 		get_answer(buf, sizeof(buf));
 		if (buf[0] == CHAR_HELP  buf[1] == 0)
 			show_help(obj, q);
@@ -431,7 +431,7 @@ static int text_handler_multiselect(struct frontend *obj, struct question *q)
   DISPLAY:
 	printlist (obj, q, count, choices_translated, tindex, selected);
 	printf(question_get_text(obj, debconf/text-prompt-default-string, 
-		Prompt: '%c' for help, default=%s ), CHAR_HELP, defval);
+		Prompt: '%c' for help, '%c' go back, default=%s ), CHAR_HELP, CHAR_GOBACK, defval);
 	get_answer(answer, sizeof(answer));
 	if (answer[0] == CHAR_HELP  answer[1] == 0)
 	{
@@ -551,11 +551,11 @@ static int text_handler_select(struct frontend *obj, struct question *q)
 		printlist (obj, q, count, choices_translated, tindex, selected);
 		if (def = 0  choices_translated[def]) {
 			printf(question_get_text(obj, debconf/text-prompt-default, 
-Prompt: '%c' for help, default=%d ),
-	CHAR_HELP, def+1);
+Prompt: '%c' for help, '%c' go back, default=%d ),
+	CHAR_HELP, CHAR_GOBACK, def+1);
 		} else {
 			printf(question_get_text(obj, debconf/text-prompt,
-Prompt: '%c' for help ), CHAR_HELP);
+Prompt: '%c' for help, '%c' go back ), CHAR_HELP, CHAR_GOBACK);
 		}
 		get_answer(answer, sizeof(answer));
 		if (answer[0] == CHAR_HELP)
@@ -687,9 +687,9 @@ static int text_handler_string(struct frontend *obj, struct question *q)
 	const char *defval = question_getvalue(q, );
 	while (1) {
 		if (defval)
-			printf(question_get_text(obj, debconf/text-prompt-default-string, Prompt: '%c' for help, default=%s ), CHAR_HELP, defval);
+			printf(question_get_text(obj, debconf/text-prompt-default-string, Prompt: '%c' for help, '%c' go back, default=%s ), CHAR_HELP, CHAR_GOBACK, defval);
 		else
-			printf(question_get_text(obj, debconf/text-prompt, Prompt: '%c' for help ), CHAR_HELP);
+			printf(question_get_text(obj, debconf/text-prompt, Prompt: '%c' for help, '%c' go back ), CHAR_HELP, CHAR_GOBACK);
 		fflush(stdout);
 		get_answer(buf, sizeof(buf));
 		if (buf[0] == CHAR_HELP  buf[1] == 0)


Bug#616315: cdebconf in d-i via serial hides the option to go back

2011-03-03 Thread Joey Hess
Miguel Figueiredo wrote:
 In attachment a patch for cdebconf to be reviewed.

Thanks for working on this.

Since backup support can be disabled or enabled at various times, a
fully correct patch would conditionalise the text on its status.

That may not matter in the context of using cdebconf in d-i, where
everything or almost everything supports backup. But it would matter
more when cdebconf is used on the installed system.

-- 
see shy jo


signature.asc
Description: Digital signature


Bug#616315: cdebconf in d-i via serial hides the option to go back

2011-03-03 Thread Christian PERRIER
Quoting Miguel Figueiredo (el...@debianpt.org):

 -_Description: Prompt: '%c' for help, default=%d 
 +_Description: Prompt: '%c' for help, '%c' go back, default=%d 

The text could also be (shorter and imho more consistent):

Prompt: '%c': help, '%c': go back, default: '%d' 




signature.asc
Description: Digital signature


Re: RFC: bringing back task packages

2011-02-18 Thread Christian PERRIER
Quoting Joey Hess (jo...@debian.org):

 ### i18n
 
 There are many language tasks in tasksel. It might be good to have
 the task packages be moved out of tasksel; I don't know if it'd make
 sense to have individual language teams maintain them, or what.


Many teams are definitely too small to do that (often one individual
and often someone not that deeply involved in Debian), so except for a
few real teams, it would probably make better sense to have i18n
(indeed often l10n) tasks maintained by the whole i18n crowd.




signature.asc
Description: Digital signature


Re: RFC: bringing back task packages

2011-02-18 Thread Josselin Mouette
Le jeudi 17 février 2011 à 19:20 -0400, Joey Hess a écrit : 
 ### gnome
 
 Would the gnome team want to maintain a task-gnome?
 Much of tasksel's gnome task is already taken from the gnome-core
 and gnome metapackages, with a few more things added. 

Yes, they fit globally the same purpose. There are just some small hacks
to handle tasksel; for example we allow OOo as an alternative to
gnome-office to avoid installing both by default when OOo was already
selected by the desktop task. I don’t think anything needs to change on
that matter.

 task-gnome
 would not need to deal with core X desktop stuff; task-desktop would
 still handle that. Although we could move away from having a task-desktop
 if you'd prefer.

I’d prefer to keep it separate. The gnome metapackage should be
installable on a session server without any X server installed.

 There are also many localized desktop tasks. Mostly these add things
 like localization packages for openoffice, and occasionally some fonts.
 I'd like to see those be maintained in conjunction with task-gnome,
 but it would mean some coordination with the dozens of people who
 currently maintain those localization tasks.

I’m afraid the approach of using tasks for localization does not scale.

Instead, I’d like to see introduced something like conditional
recommends: that is, recommends that would only be installed if a
third-party package if already here (and that would get installed when
installing the said third-party package).

This way, you could do in all packages something like:
Package: aspell 
Conditional-Recommends: aspell-en {task-english}, aspell-fr 
{task-french}, …

This would also be useful for some plugins. I don’t know how hard this
would be to implement in APT.

 Packages - Recommends
   Recommends may be better than what we have now in tasksel.
   If aptitude auto-selects *new* recommends of a previously installed
   package to be installed? Currently new Packages added to a task
   only affect new installations of that task.

AFAIK new Recommends are not installed. That is the reason why we still
heavily use Depends in metapackages instead.

Cheers,
-- 
 .''`.
: :' : “You would need to ask a lawyer if you don't know
`. `'   that a handshake of course makes a valid contract.”
  `---  J???rg Schilling


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1298020358.18394.59.camel@meh



Re: RFC: bringing back task packages

2011-02-18 Thread Andreas Tille
[Not sure whether we should keep the long To: - list, I'd suggest
 continuing on debian-devel but keep it for the moment.]

On Thu, Feb 17, 2011 at 07:20:30PM -0400, Joey Hess wrote:
 A long time ago, tasksel installed task packages, which were regular
 metapackages. This was dropped because the task packages had to Depend
 on many packages, which made the installed system brittle, and made 
 testing propigation a problem. Now that Recommends are installed by
 default, I'm revisiting the idea of using task packages. It solves
 many issues and inconsistencies with tasksel vs the rest of Debian.

If I understand the consequences of the statement correctly I welcome
this step very much.
 
 ### blends
 
 I think there is interest in getting some blends displayed in Taskel?

Yes, definitely!

 It's mostly orthagonal to this proposal, but this would help with
 giving you full control over what your tasks do. I do feel that blends
 need to be listed below the other tasks in tasksel, and probably with
 a divider between them.

This would be an acceptable approach.

 Also, we have been careful to only have ten
 tasks, to avoid overloading the user; and there is a limit to the length
 of the list before it begins scrolling, so the d-i team would have to
 look at the UI before adding Blends to the interface.

The requirement for a limited set of tasks to provide a good overview is
reasonable but has two flavours:  On one hand it restricts the number of
Blends we can include into the list and on the other hand it might have
an influence on the number of tasks[1] we are maintaining inside each
Blend which exceeds 10 drastically at least for three Blends (the most
active ones).

From my perspective the only reasonable solution for this reduced
number of list entries requirement is to close bug #273797 and have a
hierarchical task selection where you first select the Blend and than
select a set of tasks[1] inside the Blend.

[1]
Remark: I have the feeling that in the Blends context we are using the
term task in some different manner.  While it was probably influenced
by tasksel (and invented by the Debian Edu developers) it drifted a bit
away somehow.  I have the feeling that we should find a proper
definition what we mean when talking about Blends. 
 
 ## Implementation Option A
 
 Put everything in the task package.
 
 ...
 
 ## Implementation Option B
 
 Keep Test-*, Enhances, Relevance, and Section in the debian-tasks.desc
 file; move the other fields to the task packages.

I'm afraid I do not fully understand the difference / consequences of these
two options.  Can you provide some short examples?

Kind regards

   Andreas.

-- 
http://fam-tille.de


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110218134908.gh9...@an3as.eu



RFC: bringing back task packages

2011-02-17 Thread Joey Hess
A long time ago, tasksel installed task packages, which were regular
metapackages. This was dropped because the task packages had to Depend
on many packages, which made the installed system brittle, and made 
testing propigation a problem. Now that Recommends are installed by
default, I'm revisiting the idea of using task packages. It solves
many issues and inconsistencies with tasksel vs the rest of Debian.

The other problem with task packages before is that tasksel allowed the
user to select from amoung all that were available, and this resulted in a
confusing long mess of tasks to choose from. To avoid that, I intend to
keep the ultimate decision about what tasks are displayed in tasksel under
the control of the tasksel maintainers. But, I do hope that moving more of
the maintenance of tasks to the developers responsible for those areas of
Debian will result in a better selection of software and less work. We've
already had some good progress in that area with the gnome metapackages
which are used by tasksel.

If tasksel was switched to task packages, the task packages would probably
be initially built from tasksel's source. They could be split out of
tasksel's source as other groups stepped up to maintain them.


## Questions for teams

### gnome

Would the gnome team want to maintain a task-gnome?
Much of tasksel's gnome task is already taken from the gnome-core
and gnome metapackages, with a few more things added. task-gnome
would not need to deal with core X desktop stuff; task-desktop would
still handle that. Although we could move away from having a task-desktop
if you'd prefer.

There are also many localized desktop tasks. Mostly these add things
like localization packages for openoffice, and occasionally some fonts.
I'd like to see those be maintained in conjunction with task-gnome,
but it would mean some coordination with the dozens of people who
currently maintain those localization tasks.

### kde, lxde, xfce

See above and s/gnome/$you/

### cups

Would the cups maintainers be interested in maintaining a
task-print-server? Keeping the right ppds and cups packages in the task
has been an ongoing issue for me.

Note that a subset of cups is also installed as part of the desktop
tasks, and it would also make sense to have a metapackage on the cups
side that desktop tasks could use. The sole different currently is
that openprinting-ppds is included in the print server task, but not
the desktop tasks.

### blends

I think there is interest in getting some blends displayed in Taskel?
It's mostly orthagonal to this proposal, but this would help with
giving you full control over what your tasks do. I do feel that blends
need to be listed below the other tasks in tasksel, and probably with
a divider between them. Also, we have been careful to only have ten
tasks, to avoid overloading the user; and there is a limit to the length
of the list before it begins scrolling, so the d-i team would have to
look at the UI before adding Blends to the interface.

### i18n

There are many language tasks in tasksel. It might be good to have
the task packages be moved out of tasksel; I don't know if it'd make
sense to have individual language teams maintain them, or what.

If tasksel displayed Task packages' short Description fields, those
would need to be translated. I know we have translated Descriptions
but I don't know about coverage, or if that info is available when
tasksel runs in d-i?


## Comparing tasksel and dpkg fields

Key - Depends
This would be an improvement, as new Depends of a task would be
installed on upgrade; there is currently no way to upgrade a task
and get new packages that have been added to it.

Note that Britney already treats Key as Depends internally.
So this change would not impact testing migration.

Packages - Recommends
Recommends may be better than what we have now in tasksel.
If aptitude auto-selects *new* recommends of a previously installed
package to be installed? Currently new Packages added to a task
only affect new installations of that task.

Most packages in a task need to be Recommends, to avoid wedging
Britney, and to allow removing bits of a task that are not wanted.

Note that the Task field on the package side, which is added to the
archive based on data from tasksel, could go away.

Enhances - ???
The Enhances fields are not truely the same as Depends
(but are probably closer to Depends than to dpkg's Enhances).
A task that Enhances other tasks is hidden, and 
auto-force-installed when the other tasks are installed.

Relevance - ???
This is used to do some UI ordering of tasks. Closest equivilant
is Priority, but it's not granular enough.

Test- - ???
These fields specify programs to run to test if the 
task should be force-auto-installed, or hidden, or selected
for installation.

Description 

Bug#518808: marked as done (installation-guide: Put back booting from DOS section)

2011-01-24 Thread Debian Bug Tracking System
Your message dated Mon, 24 Jan 2011 12:17:52 +
with message-id e1phlmm-ri...@franck.debian.org
and subject line Bug#518808: fixed in installation-guide 20110122
has caused the Debian Bug report #518808,
regarding installation-guide: Put back booting from DOS section
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.)


-- 
518808: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=518808
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-guide
Severity: normal
Tags: patch

Hello,

Once install.bat gets back on debian-cd (#518807), please enable the
booting from DOS section again, as patch attached.

Samuel

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.28 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

-- 
Samuel
N (* If you have a precise idea of the intended use of the following code, 
please
Nwrite to eduardo.gime...@inria.fr and ask for the prize :-)
N-- Eduardo (11/8/97) *)
 -+- N sur #ens-mim - et c'était un des développeurs -+-
Index: en/boot-installer/x86.xml
===
--- en/boot-installer/x86.xml   (révision 5)
+++ en/boot-installer/x86.xml   (copie de travail)
@@ -95,9 +95,6 @@
 /para
   /sect2
 
-!-- FIXME the documented procedure does not exactly work, commented out
- until fixes
-
   sect2 arch=x86 id=install-from-dos
   titleBooting from a DOS partition/title
 
@@ -119,16 +116,9 @@
 
 /parapara
 
-Please note, there is currently a loadlin problem (#142421) which
-precludes filenameinstall.bat/filename from being used with the
-bf2.4 flavor. The symptom of the problem is an
-computeroutputinvalid compressed format/computeroutput error.
-
 /para
   /sect2
 
-END FIXME --
-
   sect2 arch=x86 id=boot-initrd
   titleBooting from Linux Using commandLILO/command or
   commandGRUB/command/title
---End Message---
---BeginMessage---
Source: installation-guide
Source-Version: 20110122

We believe that the bug you reported is fixed in the latest version of
installation-guide, which is due to be installed in the Debian FTP archive:

installation-guide-amd64_20110122_all.deb
  to main/i/installation-guide/installation-guide-amd64_20110122_all.deb
installation-guide-armel_20110122_all.deb
  to main/i/installation-guide/installation-guide-armel_20110122_all.deb
installation-guide-hppa_20110122_all.deb
  to main/i/installation-guide/installation-guide-hppa_20110122_all.deb
installation-guide-i386_20110122_all.deb
  to main/i/installation-guide/installation-guide-i386_20110122_all.deb
installation-guide-ia64_20110122_all.deb
  to main/i/installation-guide/installation-guide-ia64_20110122_all.deb
installation-guide-kfreebsd-amd64_20110122_all.deb
  to 
main/i/installation-guide/installation-guide-kfreebsd-amd64_20110122_all.deb
installation-guide-kfreebsd-i386_20110122_all.deb
  to main/i/installation-guide/installation-guide-kfreebsd-i386_20110122_all.deb
installation-guide-mips_20110122_all.deb
  to main/i/installation-guide/installation-guide-mips_20110122_all.deb
installation-guide-mipsel_20110122_all.deb
  to main/i/installation-guide/installation-guide-mipsel_20110122_all.deb
installation-guide-powerpc_20110122_all.deb
  to main/i/installation-guide/installation-guide-powerpc_20110122_all.deb
installation-guide-s390_20110122_all.deb
  to main/i/installation-guide/installation-guide-s390_20110122_all.deb
installation-guide-sparc_20110122_all.deb
  to main/i/installation-guide/installation-guide-sparc_20110122_all.deb
installation-guide_20110122.dsc
  to main/i/installation-guide/installation-guide_20110122.dsc
installation-guide_20110122.tar.gz
  to main/i/installation-guide/installation-guide_20110122.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 518...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christian Perrier bubu...@debian.org (supplier of updated installation-guide 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sat, 22

Bug#606242: Reproduces on multiple machines with multiple type mice, on at least two screen button icons; [Go Back] and [Continue].

2011-01-17 Thread techy techtech
installation-reports
Package: debian-squeeze-di-RC1-i386-binary-1 install, on 13.01.2011.
Using: Debian Installer, Graphical Installer, Release Candidate 1.
Change of Mouse to: 'Chic' optical 'faerie' Model: 3902 C255,
features a PS/2 plug, two button and a scroll wheel.
Machine: Motherboard: A bit KT7, Raid, 1 Ghz.
Processor: AMD AThlon K7, 850 Mhz, Socket 'A'
Memory: SDRAM 2 x 512Mb = 1Gb.
Chipset: Via KT 133 ATX, USB 1.0 compliant, UDMA 100, Socket 'A', FSB
200Mhz, AGP 4X.
(Further details of this machine are already reported previously above.)

Comments/Problems:

Example 1: The [Go Back] screen button icon also does not do it's job always.
From the Screen: 'Partition Disks','This is an overview of your
currently configured partitions and mount points'.
I selected my blue line #1 158 GB ext3.
I positioned the mouse screen cursor pointer tip in the centre of the
letter 'o' in the screen [Go Back] button icon.
I pressed the left mouse button, the icon greyed out, my selected line
turned a darker blue. The process went into a wait (froze).
I wrote these notes up. I waggled the mouse slightly, while the cursor
pointer was still contained inside the button icon borders.
The software [Go Back] process then proceeded to continue to the next screen OK.

Example 2: Another [Continue] screen button icon not working this time
with this THIRD mouse type.
Screen: 'Partition Disks','Partition Settings'.
Selected blue line: 'Done setting up the partition'.
Clicked left mouse button on the small hole in the letter 'e' in [Continue]
The continue button icon greyed out, the slected line turned a darker
blue, the process did not continue.

I wrote up my notes, microwaved my cold tea, waggled the mouse, the
process continued OK.

Example 3: No problems (so far) with the [Help] button icon.
Screen: 'Partition Disks','This is an overview of your currently
configured partitions and mount points'.
The [Help] button icon was tried 21 times at this screen with no
issue, problem or faiilures.

Example 4: No problems (so far) with the [Screen Shot] (Screenshot) button icon.
Screen: 'Partition Disks','This is an overview of your currently
configured partitions and mount points'.
The [Screenshot] button icon was tried 20 times at this screen with no
issue, problem or failures.

Example

 5: The [Continue] screen button icon failed to do it's job on an occurence of;
Screen: 'Save debug logs','Mounted file system. [Continue].
The selected line turned darker blue, the continue button icon greyed out.
The process did not continue. I wrote up my notes, waggled, the
process continued OK.

Off topic Note: rm removing most of my 'saved debug logs' ( after, I
am guessing, saving 5 logs)
 I bypassed a problem I encountered, and I could then resume saving
debug logs without error.
I was saving to and I entered /target/var/log/
# nano /target/var/log/install/syslog  showed;
Errors were encountered while processing: python-central  E: Sub-process
  /usr/bin/dpkg returned an error code (1)

Example 6: 14.01.2011.
I changed to a 4th? mouse, to a Compaq branded suznou Logitech Electronics Ltd,
ASSY P/N 334684-108  2001.04.12  38920101 Two button, mouse ball,
scroll wheel, PS/2 plug.
On machine: Motherboard: A bit KT7, Raid, 1 Ghz.
(Further details -less mouse- of this machine are already reported
previously above.)
I started a debian squeeze di RC1 i386 binary 1 DVD install session. I
had an occurence of [Continue] failing,
 on Screen: 'Set up users and passwords','?enter password?'
a little waggle took me to 'A user account will be created for you to
use...' Proceeded OK.

Example 7: [Go Back] failed at Screen: 'Finish the
installation','Installation complete'.
1) I wish GoBack would indicate where it was going to.
   It varies from; di-mm screen, to, where it came from.
2) Ouch, A spacebar tap to free screensaver, was taken by di as a [Continue].

Example 8: [GoBack] failed at Screen: 'Save debug logs','Mounted file system'.
[GoBack], failure, waggle, to screen: 'Directory in which to save
debug logs', OK.

Example 9: New start RC1 install, Screen Partition Disks','?Choose method?'
[Continue] failed (Froze), waggled, the process proceeded to continue OK.

In summary, The issue symptom reproduces on Multiple machines with
multiple mice,
 on at least two screen button icons; [Go Back] and [Continue].

I wonder what the library is called that supplies the screen widget software ?

di is great software getting greater. My regards to all involved, McTech.



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/AANLkTi=Y-2Wra3n7SLh2G_Waz=donksrpsd6-qsqc...@mail.gmail.com



Processed: same problem is back due to changes in d-i, reopening

2010-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 unarchive 603974
Bug #603974 {Done: Daniel Baumann dan...@debian.org} [live-installer] needs 
to reconfigure console-setup
Unarchived Bug 603974
 reopen 603974
Bug #603974 {Done: Daniel Baumann dan...@debian.org} [live-installer] needs 
to reconfigure console-setup
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
 found 603974 29
Bug #603974 [live-installer] needs to reconfigure console-setup
Bug Marked as found in versions live-installer/29.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
603974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603974
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: 
http://lists.debian.org/handler.s.c.129336925726948.transcr...@bugs.debian.org



Bug#510422: marked as done (tasksel: Schould switch back to xdm for XFCE and maybe also for LXDE tasks)

2010-12-06 Thread Debian Bug Tracking System
Your message dated Mon, 6 Dec 2010 14:26:33 -0400
with message-id 20101206182633.ga19...@gnu.kitenet.net
and subject line xdm for xfce
has caused the Debian Bug report #510422,
regarding tasksel: Schould switch back to xdm for XFCE and maybe also for LXDE 
tasks
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.)


-- 
510422: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510422
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: tasksel
Version: 2.77
Severity: wishlist

In Jan 2007 the Xfce desktop task was changed to use gdm instead of xdm 
because of #407342. However, that bug has long since been fixed.

The task should probably be changed back to use xdm as that better matches 
the character of the desktop.

Not sure if the same is true for the LXDE desktop task.

Also not sure whether or not this should be postponed until after lenny.


signature.asc
Description: This is a digitally signed message part.
---End Message---
---BeginMessage---
I talked this over with Corsac, and there was no desire for xdm
in the xfce task for squeeze. lightdm might be an option post-squeeze
(and once gdm is gone for gdm3, something lighter will certianly be
needed).

-- 
see shy jo


signature.asc
Description: Digital signature
---End Message---


Bug#600428: trouble going back and forth in installation steps

2010-10-18 Thread Miguel Figueiredo
Hi,

you used a Debian 'Lenny' cd image, although there's nothing wrong with that 
we are near the release of Debian 'Squeeze' and we are trying to identify/fix 
bugs for this release.
Care to try with the latest cd images and report if you encounter any/same 
problems?

http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-
cd/debian-testing-i386-netinst.iso

-- 
Melhores cumprimentos/Best regards,

Miguel Figueiredo
http://www.DebianPT.org

A Domingo 17 Outubro 2010 04:06:15 Jens Hochapfel você escreveu:
 Package: installation-reports
 
 Boot method: How did you boot the installer? CD? floppy? network? CD
 Image version: Full URL to image you downloaded is best
 http://cdimage.debian.org/debian-cd/5.0.6/i386/iso-cd/debian-506-i386-CD-1.
 iso Date: Date and time of the install yesterday

...




--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201010182117.09238.el...@debianpt.org



Bug#600428: trouble going back and forth in installation steps

2010-10-16 Thread Jens Hochapfel
Package: installation-reports

Boot method: How did you boot the installer? CD? floppy? network? CD
Image version: Full URL to image you downloaded is best
http://cdimage.debian.org/debian-cd/5.0.6/i386/iso-cd/debian-506-i386-CD-1.iso
Date: Date and time of the install yesterday

Machine: Description of machine (eg, IBM Thinkpad R32) acer aspire 5732ZG
Processor: pentium dual core
Memory:
Partitions: df -Tl will do; the raw partition table is preferred

Output of lspci -knn (or lspci -nn):

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:  [O ]
Load installer modules: [O ]
Detect hard drives: [O ]
Partition hard drives:  [O/E ]
Install base system:[O ]
Clock/timezone setup:   [O ]
User/password setup:[O ]
Install tasks:  [O ]
Install boot loader:[E ]
Overall install:[ ]

Comments/Problems:

Description of the install, in prose, and any thoughts, comments
  and ideas you had during the initial install.  Graphical
install.Apart from not recognizing atheros AR8132 and
AR5B93 Ethernet and Wireless card automatically, the real problem was
this: I managed to correctly choose my USB Stick for automatic
partitioning as I wanted and went ahead sucessfully until installing
the bootloader, I wanted it on the USB Stick rather than harddrive,
and to make sure to choose the right device designation for it, I went
back to menu and entered Partition hard drives again to look it up,
that's when trouble commenced: when I went back to the menu, I
couldn't re-enter installing the boot loader and was kicked back to
partitioning hard drives, when I finally chose to re-write the
partition table in order to be let out of the circle, after doing so,
installing the bootloader set in automatically without any prompts
(probably because that's where I had interrupted the journey forward
in installation, *but* in fact I hadn't chosen where to put it yet!)
and terminated with an error message to the respect that it couldn't
be installed, sorry, can't be more precise, but I think there was not
much more info.  I abandoned installation.


Bug#513253: marked as done (debian-installer: won't boot; kernel reboots back into bootloader)

2010-09-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Sep 2010 15:25:32 +
with message-id e1ourxm-0004wx...@ravel.debian.org
and subject line Closing oldbug report against debian-installer #513253
has caused the Debian Bug report #513253,
regarding debian-installer: won't boot; kernel reboots back into bootloader
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.)


-- 
513253: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513253
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: debian-installer
Version: debian-testing-powerpc-netinst-20081105
Severity: normal


- 'expert64' mode for installer reboots back into bootloader
- installation proceeds correctyl but after boot:
...
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM 
|
Elapsed time since release of system processors: 24254 mins 15 secs

Config file read, 4096 bytes

Welcome to yaboot version 1.3.13
Enter help to get some basic usage information
boot: 
  Linux  old  
boot: 
Please wait, loading kernel...
   Elf64 kernel loaded...
Loading ramdisk...
ramdisk loaded at 0290, size: 7372 Kbytes
OF stdout device is: /vdevice/v...@3000
Hypertas detected, assuming LPAR !

...and then reboots back into the bootloader


-- System Information:
Debian Release: 5.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-pps (SMP w/4 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash


---End Message---
---BeginMessage---
We are closing this bug report against debian-installer 
for one of the following reasons:
- it was reported with a pre-lenny version of Debian
  Installer.
- indications in the bug report give the feeling that
  the reported problem was lying in another software, unrelated to
  D-I, which we can't easily identify.
- indications in the installation report suggest that it may have been
  fixed in a more recent version of a D-I component
- it was successful and we forgot closing it..:-)
- it has no information we consider useful


The D-I team is currently in the process of cleaning out the old spool
of installation reports that haven't bene processed yet. 

In case you think that the problem you reported has chances to be
still present, please reiterate your installation test with
a more recent image of D-I, if you're in position of doing this.

You'll find daily builds at
http://www.debian.org/devel/debian-installer. We recommend you choose
the netboot image, in the daily builds section, then choose to
install squeeze when prompted.

If some problems are found, please report them with a new bug sent
against installation-reports.

Many thanks for your understanding and your help improving Debian,
past and present.


---End Message---


Bug#297001: marked as done (Instaalation screen becomes scrumbled after switching to another VC and back)

2010-09-07 Thread Debian Bug Tracking System
Your message dated Wed, 08 Sep 2010 03:57:54 +
with message-id e1otbng-0004wi...@ravel.debian.org
and subject line Closing old installation report #297001
has caused the Debian Bug report #297001,
regarding Instaalation screen becomes scrumbled after switching to another VC 
and back
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.)


-- 
297001: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=297001
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: Debian-installer
Version:   Current Sarge

Problem:

If one starts the installation of current Sarge release ( either from
custom DVD -Linux Magazin - or from the CD #1 from debian server )
the installation screen ( Virtual Console #1 ) becomes scratched after
activating another VC and switching back to VC #1 ( Installation screen
). E.G.: Press keys Alt-F3 enter to activate root console on 3rd VC.
  Then Alt-F1 to return to installation screen.
The sccren becomes unreadable ( stripes from top to bottom ) and no
restoration possible.

This does NOT happen when FBconsole is started ( using the vga=791
kernel boot prompt parameter) .

/RalfS




---End Message---
---BeginMessage---
We are closing this installation report for one of the following
reasons:
- it was reported with a pre-lenny version of Debian
  Installer.
- indications in the installation report give the feeling that
  the reported problem waslying in another software, unrelated to
  D-I, which we can't easily identify.
- indications in the installation report suggest that it may have been
  fixed in a more recent version of a D-I component
- it was successful and we forgot closing it..:-)
- it has no information we consider useful


The D-I team is currently in the process of cleaning out the old spool
of installation reports that haven't bene processed yet. 

In case you think that the problem you reported has chances to be
still present, please reiterate your installation test with
a more recent image of D-I, if you're in position of doing this.

You'll find daily builds at
http://www.debian.org/devel/debian-installer. We recommend you choose
the netboot image, in the daily builds section, then choose to
install squeeze when prompted.

If some problems are found, please report them with a new bug sent
against installation-reports.

Many thanks for your understanding and your help improving Debian,
past and present.


---End Message---


Bug#584752: debian-installer: GO BACK not working if harddisk mounted

2010-06-06 Thread yellow
Package: debian-installer
Version: GO BACK not working if harddisk mounted
Severity: minor

Dear Sir, 

I mounted the usb pendrive for the ip2100 fw that it asked during installation 
of hte debian testing i386.
OK

I get to the harddisk setup, and make my disks as I desired. 

But the pendrive is still mounted ,,, ... it says IGNORE CANCEL or GO BACK
before starting

I clicked on GO back and it continued anyhow , and did not go back to re-setup 
or whatever to propose to unmount my pendrive

best regards
Y.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-3-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20100606103116.22967.94227.report...@debian05.rp614v4



Back

2010-02-24 Thread Christian PERRIER
I'm back from 4 days away without mail access. I just catched up with
the list without really reading it. In case something important
needing my attention happened since Saturday evening, please mail me
privately.


-- 




signature.asc
Description: Digital signature


Bug#570755: installation-reports: Continue Back buttons switched on archive not found screen

2010-02-21 Thread Helge Kreutzmann
Package: installation-reports
Severity: normal

A few days ago I installed debian-504-amd64-netinst.iso (md5sum:
1781299ae37a2b99b75aefa39a8ee773) from
http://www.debian.org/CD/netinst/ on a new Dell laptop. Due to some
proxy configuration I did not have a net conection even though
dhclient reported one. Hence at the stage when download locations are
added to apt.conf the installer reported a failure (please note that I
did the install in German and roughly translated all strings back):

[!!] Configuring the package manager
Invalid archive mirror


After the explantion (which I did not copy above) I got two choices: 
Continue and Back.

Continue leads to the screen for selection a country for the debian
archive mirror and after intermediate screens back to the one above
with the error message

Back returns the message that no archive mirror can be found and the
installation continues.

As you can see by my wording, the two buttons seem to be switched,
i.e. pressing back activates the continue mechanism while pressing
continue returns back to the selection process for archive mirrors.

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software libre: http://www.ffii.de/


signature.asc
Description: Digital signature


Bug#570755: marked as done (installation-reports: Continue Back buttons switched on archive not found screen)

2010-02-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Feb 2010 11:34:35 +0100
with message-id 201002211134.36315.elen...@planet.nl
and subject line Re: Bug#570755: installation-reports: Continue  Back buttons 
switched on archive not found screen
has caused the Debian Bug report #570755,
regarding installation-reports: Continue  Back buttons switched on archive 
not found screen
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.)


-- 
570755: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports
Severity: normal

A few days ago I installed debian-504-amd64-netinst.iso (md5sum:
1781299ae37a2b99b75aefa39a8ee773) from
http://www.debian.org/CD/netinst/ on a new Dell laptop. Due to some
proxy configuration I did not have a net conection even though
dhclient reported one. Hence at the stage when download locations are
added to apt.conf the installer reported a failure (please note that I
did the install in German and roughly translated all strings back):

[!!] Configuring the package manager
Invalid archive mirror


After the explantion (which I did not copy above) I got two choices: 
Continue and Back.

Continue leads to the screen for selection a country for the debian
archive mirror and after intermediate screens back to the one above
with the error message

Back returns the message that no archive mirror can be found and the
installation continues.

As you can see by my wording, the two buttons seem to be switched,
i.e. pressing back activates the continue mechanism while pressing
continue returns back to the selection process for archive mirrors.

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software libre: http://www.ffii.de/


signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
reassign 570755 choose-mirror
thanks

Hi Helge,

On Sunday 21 February 2010, Helge Kreutzmann wrote:
 Continue leads to the screen for selection a country for the debian
 archive mirror and after intermediate screens back to the one above
 with the error message

 Back returns the message that no archive mirror can be found and the
 installation continues.

Even though it may seem inconsistent, it is not.

To understand it you have to realize that choose-mirror can be run in two 
ways:
1) directly from the main menu, as in netboot and businesscard CD installs
2) from apt-setup, as in netinst CD and full CD and DVD installs

Your case is 2).

The meaning of Continue and Go Back in both cases is:
- Continue: continue with mirror selection, i.e: select a different mirror
  and try again
- Go Back: abort mirror selection

In case 1) Go Back would return you to the main menu.

In your case 2) it returns you to where it came from: to apt-setup.
But it does not simply continue apt-setup as you suggest! apt-setup sees 
that mirror selection was aborted and thus asks for confirmation if you 
really want to continue without selecting a mirror (and if you answer no, 
it will start choose-mirror again).

The buttons are also consistent with how they are used in other error 
dialogs. Continue simply means I've read the dialog, proceed.

So IMO the buttons are correct and consistent. I'm closing the report, but 
if you wish to respond you can still reply.

Cheers,
FJP

---End Message---


Processed: Re: Bug#570755: installation-reports: Continue Back buttons switched on archive not found screen

2010-02-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 reassign 570755 choose-mirror
Bug #570755 [installation-reports] installation-reports: Continue  Back 
buttons switched on archive not found screen
Bug reassigned from package 'installation-reports' to 'choose-mirror'.
 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Bug#546983: console-setup-mini: fails to set the keyboard layout (and falls back to us layout)

2009-11-22 Thread Anton Zinoviev
On Fri, Nov 20, 2009 at 12:47:41AM +0100, Francesco Poli wrote:
 
  Where can I find a list of the symbols that the fonts in console-setup 
  need to support?
 
 As far as the toilet future font is concerned, you may wish to take a
 look at its complete definition in /usr/share/figlet/future.tlf
 (shipped in package toilet-fonts)...

Version 4.30-2 of console-terminus and version 1.49 of console-tools 
contain fonts that can display the characters in future by using 
approximations.  Because of this your font (lat9u) is still better.

Anton Zinoviev




-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#546983: console-setup-mini: fails to set the keyboard layout (and falls back to us layout)

2009-11-22 Thread Francesco Poli
On Sun, 22 Nov 2009 15:32:25 +0200 Anton Zinoviev wrote:

 On Fri, Nov 20, 2009 at 12:47:41AM +0100, Francesco Poli wrote:
  
   Where can I find a list of the symbols that the fonts in console-setup 
   need to support?
  
  As far as the toilet future font is concerned, you may wish to take a
  look at its complete definition in /usr/share/figlet/future.tlf
  (shipped in package toilet-fonts)...
 
 Version 4.30-2 of console-terminus and version 1.49 of console-tools 
 contain fonts that can display the characters in future by using 
 approximations.

Wow!  That's great!   :-)
I've just tested all the standard fonts (Fixed, Terminus,
TerminusBold, TerminusBoldVGA, VGA): they are all able to display
'toilet -f future' symbols in a strange, yet charming way!

I really like the result: I finally chose TerminusBoldVGA as my
favorite font.
Thank you very, very much for this console enhancement!   :-)

 Because of this your font (lat9u) is still better.

I tend to disagree: I now prefer TerminusBoldVGA!   ;-)

Actually, lat1u-16.psf.gz was a compromise solution for me, since it
was the only way I had to actually display 'toilet -f future' symbols
in a legible manner, but I wasn't really satisfied with the result...

Your approximations of 'toilet -f future' symbols with standard
fonts (especially with TerminusBoldVGA) really look futuristic and
great!   ;-)

Thank you again.
Bye.


-- 
 New location for my website! Update your bookmarks!
 http://www.inventati.org/frx
. Francesco Poli .
 GnuPG key fpr == C979 F34B 27CE 5CD8 DC12  31B5 78F4 279B DD6D FCF4


pgpVCeJS1q5rI.pgp
Description: PGP signature


Bug#546983: console-setup-mini: fails to set the keyboard layout (and falls back to us layout)

2009-11-19 Thread Anton Zinoviev
On Wed, Nov 18, 2009 at 11:13:57PM +0100, Francesco Poli wrote:
 
  I don't know why the fonts in console-setup didn't work for you (as I 
  don't use toilet)
 
 It should be easy to see for yourself: I suggest you to install toilet
 
   # aptitude install toilet
 
 and then try it out:

Now I see.

Well, the fonts in console-setup are produced automatically, so maybe it 
will be possible to support at least some of the symbols used by toilet 
Where can I find a list of the symbols that the fonts in console-setup 
need to support?

Anton Zinoviev




-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#546983: console-setup-mini: fails to set the keyboard layout (and falls back to us layout)

2009-11-19 Thread Francesco Poli
On Thu, 19 Nov 2009 18:56:59 +0200 Anton Zinoviev wrote:

 On Wed, Nov 18, 2009 at 11:13:57PM +0100, Francesco Poli wrote:
  
   I don't know why the fonts in console-setup didn't work for you (as I 
   don't use toilet)
  
  It should be easy to see for yourself: I suggest you to install toilet
  
# aptitude install toilet
  
  and then try it out:
 
 Now I see.

Excellent!  ;-)

 
 Well, the fonts in console-setup are produced automatically, so maybe it 
 will be possible to support at least some of the symbols used by toilet

This sounds as good news indeed (even though it doesn't mean the
console will get full Unicode support/coverage, or am I wrong?). :-)

 Where can I find a list of the symbols that the fonts in console-setup 
 need to support?

As far as the toilet future font is concerned, you may wish to take a
look at its complete definition in /usr/share/figlet/future.tlf
(shipped in package toilet-fonts)...


-- 
 New location for my website! Update your bookmarks!
 http://www.inventati.org/frx
. Francesco Poli .
 GnuPG key fpr == C979 F34B 27CE 5CD8 DC12  31B5 78F4 279B DD6D FCF4


pgp0VnXUMaYO0.pgp
Description: PGP signature


Bug#546983: console-setup-mini: fails to set the keyboard layout (and falls back to us layout)

2009-11-18 Thread Anton Zinoviev
Hello!

I really appreciate you efforts to report everything relevant in the bug 
tracking system.

On Sat, Nov 14, 2009 at 01:03:37AM +0100, Francesco Poli wrote:
 
 I got the following error:
 
   /var/lib/dpkg/info/console-setup.postinst: line 115: 
 /etc/console-setup/cached.kmap.gz: No such file or directory

This means the directory /etc/console-setup didn't exist.  As it is part 
of the package console-setup-mini I suppose this was caused by previous 
errors.

   # setupcon
   /bin/setupcon: line 367: /etc/console-setup/cached.kmap.gz: No such file or 
 directory

The same reason.

 Fonts do *not* show toilet -f future symbols correctly, the layout is
 still US (why?), and some keys (e.g.: Shift+6) do not produce the
 corresponding (US layout) character until other keys are pressed
 (I had never seen such a behavior before).

Because of the missing /etc/console-setup the file 
/etc/default/console-setup was not configured properly and the result is 
the us(intl) layout where Shift+6 is a dead-key (dead_circumflex).

 OK, let's restart from scratch.
 
   # dpkg-reconfigure console-setup
 
 Why us,dvorak ?  I have never asked for a dvorak layout !!

Againd, this was caused by the missing /etc/console-setup.

   /var/lib/dpkg/info/console-setup.postinst: line 115: 
 /etc/console-setup/cached.kmap.gz: No such file or directory
   # setupcon
   /bin/setupcon: line 367: /etc/console-setup/cached.kmap.gz: No such file or 
 directory

Same.

 During the tests I also got the following kernel errors:
 
 [21794.596239] circuit:12185 conflicting memory types 9000-9500 
 uncached-minus-write-combining
 [21794.596425] reserve_memtype failed 0x9000-0x9500, track 
 uncached-minus, req uncached-minus
 
 I don't know if those are related, but I had never seen them before...

I don't know what these are, but they are not related to console-setup.

 For the record, the generated /etc/default/console-setup is as follows
 and it does not seem to comply with my debconf answers:

The postinst of console-setup(-mini) starts with 'set -e'.  This caused 
the error caused by the missing /etc/console-setup to be fatal so the 
script never had the chance to put your settings inside the 
configuration file.

On Sun, Nov 15, 2009 at 12:29:13PM +0100, Francesco Poli wrote:
 
 Let's *really* restart from scratch:
 
   # aptitude -t unstable install console-setup console-setup-mini-

Almost from scratch - the configuration files of console-setup-mini are 
still there and they are shared by console-setup:

 However, this left configuration files for console-setup-mini around:
 
   # dpkg -l | grep ^rc | cut -c 1-60
   rc  console-setup-mini   1.45
   # ls /etc/console-setup/
   cached.kmap.gzcompose.ISO-8859-11.inc  
 compose.ISO-8859-6.inc
   compose.ARMSCII-8.inc compose.ISO-8859-13.inc  
 compose.ISO-8859-7.inc
   compose.CP1251.inccompose.ISO-8859-14.inc  
 compose.ISO-8859-8.inc
   compose.CP1255.inccompose.ISO-8859-15.inc  
 compose.ISO-8859-9.inc
   compose.CP1256.inccompose.ISO-8859-16.inc  compose.KOI8-R.inc
   compose.GEORGIAN-ACADEMY.inc  compose.ISO-8859-1.inc   compose.KOI8-U.inc
   compose.GEORGIAN-PS.inc   compose.ISO-8859-2.inc   compose.TIS-620.inc
   compose.IBM1133.inc   compose.ISO-8859-3.inc   compose.VISCII.inc
   compose.ISIRI-3342.inccompose.ISO-8859-4.inc   remap.inc
   compose.ISO-8859-10.inc   compose.ISO-8859-5.inc

Before version 1.46 console-setup and console-setup-mini shared common 
configuration files.  

 I think there's a problem though: if I purge console-setup-mini, I lose
 the /etc/console-setup/ directory!!

You are right!  Hopefuly with the new version of console-setup (1.47) 
there are no shared configuration files so there will be no problems of 
this sort any more.

 Do you want me to file a separate bug report for this problem?

I believe it is fixed in 1.47.  If you find a problem in version 1.47 or 
following, do not hesitate to report it.

 BTW, I think the reference to Goha and GohaClassic in the conffile
 comments is obsolete, as no such fonts seem to exist now.

They exist but they are visible only if you use Ethiopian character set.

 I added the following line to /etc/default/console-setup
 
   FONT=lat1u-16.psf.gz
 
 and set the following variables to empty strings:
 
   FONTFACE=
   FONTSIZE=

I suppose it wasn't necessary to put empty strings here.

 After issuing
 
   # setupcon
   # invoke-rc.d hal restart
   Restarting Hardware abstraction layer: hald.
 
 I finally get the fonts I wanted to get and an Italian layout (both
 on the console and in X).

I don't know why the fonts in console-setup didn't work for you (as I 
don't use toilet) but I am glad that with lat1u-16 finaly everything is 
ok. :)

Anton Zinoviev




-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact 

  1   2   3   4   >