Re: Bug#685268: unblock: isc-dhcp/4.2.4-1

[Cyril Brulebois]

Michael Gilbert  (18/08/2012):
> Andrew hasn't yet made it clear which version he's been planning to
> support in wheezy [0], but he did upload this one well before the
> freeze.

Nice try:
[2012-07-01] Accepted 4.2.4-1 in unstable (low) (Andrew Pollock)

Mraw,
KiBi.


signature.asc
Description: Digital signature

Processed: Re: [Pkg-utopia-maintainers] Bug#672140: prompts for root passwords on a sudo-only system

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 672140 debian-installer
Bug #672140 [policykit-1] prompts for root passwords on a sudo-only system
Bug reassigned from package 'policykit-1' to 'debian-installer'.
No longer marked as found in versions policykit-1/0.104-2.
Ignoring request to alter fixed versions of bug #672140 to the same values 
previously set
> retitle 672140 sudo users should be in sudo group
Bug #672140 [debian-installer] prompts for root passwords on a sudo-only system
Changed Bug title to 'sudo users should be in sudo group' from 'prompts for 
root passwords on a sudo-only system'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
672140: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672140
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.134537233625686.transcr...@bugs.debian.org

Bug#672140: [Pkg-utopia-maintainers] Bug#672140: prompts for root passwords on a sudo-only system

[Ivo De Decker]

reassign 672140 debian-installer
retitle 672140 sudo users should be in sudo group
thanks

Hi,

Going through the RC bug list for wheezy, I noticed this bug.

On Tue, May 08, 2012 at 10:39:03PM +0200, Michael Biebl wrote:
> > If there is some setting we can make in d-i to new installs to make
> > policykit use sudo, please let me know, and I will make it. It wouldn't
> > solve the problem when upgrading existing installs that use sudo, but
> > it'd be better than nothing.
> 
> Adding a user to group sudo should be sufficient to mark it as account
> with admin privileges, i.e. a d-i setup which adds the user to group
> sudo (which is the case for a password-less root-account) should work ootb.

As Michael provided the information to implement this in d-i (which Joey asked
for), this bug should be reassigned to d-i.

Cheers,

Ivo De Decker


-- 
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/20120819103203.ga22...@ugent.be

Bug#672140: Processed: Re: [Pkg-utopia-maintainers] Bug#672140: prompts for root passwords on a sudo-only system

[Christian PERRIER]

reassign 672140 user-setup
thanks

Quoting Debian Bug Tracking System (ow...@bugs.debian.org):
> Processing commands for cont...@bugs.debian.org:
> 
> > reassign 672140 debian-installer
> Bug #672140 [policykit-1] prompts for root passwords on a sudo-only system
> Bug reassigned from package 'policykit-1' to 'debian-installer'.
> No longer marked as found in versions policykit-1/0.104-2.
> Ignoring request to alter fixed versions of bug #672140 to the same values 
> previously set
> > retitle 672140 sudo users should be in sudo group
> Bug #672140 [debian-installer] prompts for root passwords on a sudo-only 
> system
> Changed Bug title to 'sudo users should be in sudo group' from 'prompts for 
> root passwords on a sudo-only system'

Reassigning to the right D-I component.

However, in user-setup-apply:

if [ -e $ROOT/etc/sudoers ]; then
# Test if we can add the user to the sudo group
# (possible if sudo >= 1.7.2-2 is installed on the 
target system)
# If we can, do it this way, otherwise add the user to 
sudoers
# See #597239
if ! $log $chroot $ROOT adduser "$USER" sudo >/dev/null 
2>&1; then
echo "$USER ALL=(ALL) ALL" >> $ROOT/etc/sudoers
fi
else
# sudo failed to install, system won't be usable
exit 1
fi


In short, according to this code, this is already implemented, as of
user-setup 1.34, assuming the sudo group exists at the time this is
done. Adding the sudo user to sudoers is only a fallback.




signature.asc
Description: Digital signature

Processed: Re: Processed: Re: [Pkg-utopia-maintainers] Bug#672140: prompts for root passwords on a sudo-only system

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 672140 user-setup
Bug #672140 [debian-installer] sudo users should be in sudo group
Bug reassigned from package 'debian-installer' to 'user-setup'.
Ignoring request to alter found versions of bug #672140 to the same values 
previously set
Ignoring request to alter fixed versions of bug #672140 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
672140: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672140
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.1345373453511.transcr...@bugs.debian.org

Bug#685303: report bugs

[abdelkader belahcene]

Package: installation-reports

Boot method: 
Image version: <
http://cdimage.debian.org/debian-cd/6.0.5/i386/iso-cd/debian-6.0.5-i386-netinst.iso>
Date: 

Machine: 
Processor:
Memory:
Partitions: <

 rootfs19G  4,0G
14G  23% /

udev1002M 0
1002M   0% /dev
tmpfs202M  576K
202M   1% /run
/dev/disk/by-uuid/c6219362-5918-4e75-90ed-7c4643ce325f19G  4,0G   14G  23% /
tmpfs5,0M 0
5,0M   0% /run/lock
tmpfs404M   28K
404M   1% /tmp
tmpfs404M  140K
404M   1% /run/shm

>

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

Comments/Problems:

< The installation is not completed.

I tried as expert, sometimes  I couldn't kill process,  like mdadm or
mount /dev/sda4 /media  for what ??

Detect hw is a problem, same pb with ethernet card and disk hard, ther
is no button  to cancel a step,  I used other termina (ctrl+alt+F2)
to kill process and come back to previous step.

   >

Bug#681656: Detect Network Hardware stops Wheezy install

[ricky...@libero.it]

Sorry for my bad english...
I've the same problem, which DIDN'T appear in the ALPHA release. This bug is 
shown only in the BETA WHEEZY release.
If there is a non-free firmware, the installer stopped the installation.
A solution can be insert a USB pendrive with the firmwares, it works for me.

Please, solve this bug, it's very important in my opinion. 


-- 
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/17144457.7051261345383344872.JavaMail.root@wmail54

Bug#685308: Installation report Wheezy Beta 1

[S Threeoh]

Package: installation-reports

Boot method: 
CD

Image version: 
Wheezy release Beta 1 AMD64 Netinst
http://cdimage.debian.org/cdimage/wheezy_di_beta1/amd64/iso-cd/debian-wheezy-DI-b1-amd64-netinst.iso

Date: 
August 18 and August 19, several attempts

Machine: 
Lenovo IdeaCentre K210

Processor: Intel Dual Core Pentium E5200
Memory: 4G
Partitions: 
Partition 1: Windows Vista (620 GB)
Partition 2: free space (19 GB)

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

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

Comments/Problems:

I tried several attempts, with different partitioning.

In each case, I preserved partition 1, which held a Windows Vista partition.
The free space was either partitioned into a swap and a root partition, or
was used as an encrypted partition with LVM holding a swap and root logical
volume.  I also tried several choices about what partitions were bootable.
I didn't really know what this should have been, which may well have been
part of the problem.  One of the choices I tried was to let the installer
automatically partition the free space.

For all of these choices, when I got to the Grub screen, the installer
did not recognize the Vista installation.  Eventually, I went ahead anyway
and let grub install.  But the installation to the MBR got a fatal error,
and trying to let grub install elsewhere eventually got my system pretty
messed up.  Telling grub to install at /dev/sda2 finally did it in and its
not bootable now.  Next step will be to try a clean install to the entire
drive, overwriting the Vista.


As a second oddity, once when I was at the Popularity Contest screen,
I hit the Go Back button.  This was a mistake, as it locked up the installation
and I eventually had to restart the machine and installation to unfreeze it.


Thanks for all the great work you people do.  I hope this report helps make
Debian a bit better.
  

--
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/bay145-w485d26144cc5b26865402488...@phx.gbl

Bug#672689: debian-installer: grub-pc failed to install into /target/

[rcm0502]

Hello:

I can reproduce this bug as I tried to do an expert install booting the
mini installer image FROM a USB stick, which happens to be the only USB
device attached. What I suggest is that the grub installer menu option to
prompt the user to select the target to install grub to if the installer
cannot determine the correct one on its own. This way the installer will
properly install grub to the correct target.

Hope this helps

Cheers,

R

Bug#685186: IA64 (Itanium) Wheezy, ELILO installation failed, patch proposal

[Stephan Schreiber]

Source: kernel-image-3.2.0-3-itanium-di




The failed command is in debian/elilo.sh:

fstype=vfat

mount -t "$fstype" -o  
codepage=437,iocharset=iso8859-1,rw,noexec,umask=077$loop "$boot"  
"$TMP/bootstrap.$$"

what is perfect to mount an EFI system partition - much better than UTF-8.

A mount -t vfat -o codepage=437,iocharset=iso8859-1 needs the kernel  
modules nls_iso8859-1, nls_cp437, vfat, fat.


I ran the installer again. After the ELILO error message I tried
lsmod
on the shell; the most importand lines that it reported were:
nls_cp437
vfat
fat
nls_utf8

The nls_iso8859-1 module was not loaded.


The existing fat-modules-3.2.0-3-itanium-di.udeb includes the  
following modules:

nls_utf8.ko
nls_cp437.ko
fat.ko
vfat.ko

There isn't a nls_iso8859-1.ko.

The kernel config is right, linux-3.2.21/debian/config/config:

CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="utf8"

CONFIG_NLS_CODEPAGE_437=m
CONFIG_NLS_ISO8859_1=m

The nls_iso8859-1.ko isn't included in the  
fat-modules-3.2.0-3-itanium-di.udeb for the installer, that's the only  
problem.

A patch proposal is attached

I'm still using Lenny which has a 'debootstrapped' Wheezy userland on  
a chroot.
I built the kernel-image-3.2.0-3-itanium-di package again; copied the  
generated udebs into the build/localudebs directory of the  
debian-installer and build the debian-installer package after that. I  
extracted the generated debian-installer-images_20120712-ia64.tar.gz  
to a local mirror which already had files from the Wheezy beta-1. I  
built a set of netinst CDs with the debian-cd packge which used the  
mentioned local mirror.

The installer could install ELILO after that.


Kind regards
Stephan Schreiber





add_iso8859_1.patch
Description: add_iso8859_1.patch

Bug#685186: IA64 (Itanium) Wheezy, ELILO installation failed, patch proposal

[Julien Cristau]

Control: reassign -1 elilo

On Sun, Aug 19, 2012 at 17:07:00 +0200, Stephan Schreiber wrote:

> The failed command is in debian/elilo.sh:
> 
> fstype=vfat
> 
> mount -t "$fstype" -o
> codepage=437,iocharset=iso8859-1,rw,noexec,umask=077$loop "$boot"
> "$TMP/bootstrap.$$"
> what is perfect to mount an EFI system partition - much better than UTF-8.
> 
> A mount -t vfat -o codepage=437,iocharset=iso8859-1 needs the kernel
> modules nls_iso8859-1, nls_cp437, vfat, fat.
> 
> I ran the installer again. After the ELILO error message I tried
> lsmod
> on the shell; the most importand lines that it reported were:
> nls_cp437
> vfat
> fat
> nls_utf8
> 
> The nls_iso8859-1 module was not loaded.
> 
> 
> The existing fat-modules-3.2.0-3-itanium-di.udeb includes the
> following modules:
> nls_utf8.ko
> nls_cp437.ko
> fat.ko
> vfat.ko
> 
> There isn't a nls_iso8859-1.ko.
> 

< bwh> 'iocharset=iso8859-1' is a bug; Linux standard character encoding
   is UTF-8
< bwh> for filenames, at least
< bwh> So, assign to whatever contains the debian/elilo.sh script

So reassigning to elilo.

Cheers,
Julien


signature.asc
Description: Digital signature

Processed: Re: Bug#685186: IA64 (Itanium) Wheezy, ELILO installation failed, patch proposal

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 elilo
Bug #685186 [installation-reports] IA64 (Itanium) Wheezy, ELILO installation 
failed
Bug reassigned from package 'installation-reports' to 'elilo'.
Ignoring request to alter found versions of bug #685186 to the same values 
previously set
Ignoring request to alter fixed versions of bug #685186 to the same values 
previously set

-- 
685186: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685186
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.b685186.134539071323862.transcr...@bugs.debian.org

Re: [pkg-dhcp-devel] Bug#685268: unblock: isc-dhcp/4.2.4-1

[Michael Gilbert]

On Sun, Aug 19, 2012 at 6:25 AM, Cyril Brulebois wrote:
> Michael Gilbert  (18/08/2012):
>> Andrew hasn't yet made it clear which version he's been planning to
>> support in wheezy [0], but he did upload this one well before the
>> freeze.
>
> Nice try:
> [2012-07-01] Accepted 4.2.4-1 in unstable (low) (Andrew Pollock)

Anyway, it was close.  I don't know whether 0330 UTC July 1 is before
the exact time of the freeze or not, but I do recall the packaging
having an automatic unblock (and a block-udeb) during the month of
July.

Regardless, I don't really care which way the call on this goes, I
just need the call made so I can fix the right version.

Best wishes,
Mike


-- 
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/CANTw=mnpovgskln6edzdri4o0xzeyyejhra4vps5jlzqwqc...@mail.gmail.com

Re: [pkg-dhcp-devel] Bug#685268: unblock: isc-dhcp/4.2.4-1

[Cyril Brulebois]

Michael Gilbert  (19/08/2012):
> On Sun, Aug 19, 2012 at 6:25 AM, Cyril Brulebois wrote:
> > Michael Gilbert  (18/08/2012):
> >> Andrew hasn't yet made it clear which version he's been planning to
> >> support in wheezy [0], but he did upload this one well before the
> >> freeze.
> >
> > Nice try:
> > [2012-07-01] Accepted 4.2.4-1 in unstable (low) (Andrew Pollock)
> 
> Anyway, it was close.

“close” isn't exactly “well before” as you previously claimed.

> I don't know whether 0330 UTC July 1 is before the exact time of the
> freeze or not, but I do recall the packaging having an automatic
> unblock (and a block-udeb) during the month of July.

Perhaps you should read the freeze announce then?

> Regardless, I don't really care which way the call on this goes, I
> just need the call made so I can fix the right version.

I don't see any reasons why the version currently sitting in testing
would not be the version in wheezy. Which should answer your question
I think.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Re: [pkg-dhcp-devel] Bug#685268: unblock: isc-dhcp/4.2.4-1

[Michael Gilbert]

On Sun, Aug 19, 2012 at 12:23 PM, Cyril Brulebois wrote:
>> Anyway, it was close.
>
> “close” isn't exactly “well before” as you previously claimed.

Wording mistake.  Sorry.

> I don't see any reasons why the version currently sitting in testing
> would not be the version in wheezy. Which should answer your question
> I think.

Thank you.

Best wishes,
Mike


--
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/CANTw=mo0ndhwyy70padg7vvtj09ez0tkscfkmoq6i8waxiz...@mail.gmail.com

Bug#685308: Wheezy beta 1 installation report

[S Threeoh]

Thinking more about this now, I never made a separate partition for the /boot 
mount point.  I suspect that was the root cause of my problems.  But I tried 
the option of letting the installer automatically partition my free space, and 
that didn't work, either.  Hope this helps.
  

Re: Bug#685268: unblock: isc-dhcp/4.2.4-1

[Andrew Pollock]

On Sun, Aug 19, 2012 at 12:25:52PM +0200, Cyril Brulebois wrote:
> Michael Gilbert  (18/08/2012):
> > Andrew hasn't yet made it clear which version he's been planning to
> > support in wheezy [0], but he did upload this one well before the
> > freeze.
> 
> Nice try:
> [2012-07-01] Accepted 4.2.4-1 in unstable (low) (Andrew Pollock)

Thanks for trying Michael.

I'd been desperately trying to get 4.2.4-1 in before the freeze, but Real
Life got in the way, and I didn't feel I had a good case for a freeze
exception for 4.2.4-1, given it was my own inability to get it in on time
that was the reason it got caught up by the freeze.


signature.asc
Description: Digital signature

Bug#685303: marked as done (report bugs)

[Debian Bug Tracking System]

Your message dated Mon, 20 Aug 2012 06:03:31 +0200
with message-id <20120820040331.gf5...@mykerinos.kheops.frmug.org>
and subject line Re: Bug#685303: report bugs
has caused the Debian Bug report #685303,
regarding report bugs
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.)


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

Boot method: 
Image version: <
http://cdimage.debian.org/debian-cd/6.0.5/i386/iso-cd/debian-6.0.5-i386-netinst.iso>
Date: 

Machine: 
Processor:
Memory:
Partitions: <

 rootfs19G  4,0G
14G  23% /

udev1002M 0
1002M   0% /dev
tmpfs202M  576K
202M   1% /run
/dev/disk/by-uuid/c6219362-5918-4e75-90ed-7c4643ce325f19G  4,0G   14G  23% /
tmpfs5,0M 0
5,0M   0% /run/lock
tmpfs404M   28K
404M   1% /tmp
tmpfs404M  140K
404M   1% /run/shm

>

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

Comments/Problems:

< The installation is not completed.

I tried as expert, sometimes  I couldn't kill process,  like mdadm or
mount /dev/sda4 /media  for what ??

Detect hw is a problem, same pb with ethernet card and disk hard, ther
is no button  to cancel a step,  I used other termina (ctrl+alt+F2)
to kill process and come back to previous step.

   >
--- End Message ---
--- Begin Message ---
Quoting abdelkader belahcene (abelahc...@gmail.com):

> I tried as expert, sometimes  I couldn't kill process,  like mdadm or
> mount /dev/sda4 /media  for what ??
> 
> Detect hw is a problem, same pb with ethernet card and disk hard, ther
> is no button  to cancel a step,  I used other termina (ctrl+alt+F2)
> to kill process and come back to previous step.


Thisproblem is now identified as a kernel problem and is worked around
in mountmedia. You can try daily images that implement the workaround.




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

Bug#681656: marked as done (Detect Network Hardware stops Wheezy install)

[Debian Bug Tracking System]

Your message dated Mon, 20 Aug 2012 06:04:24 +0200
with message-id <20120820040424.gg5...@mykerinos.kheops.frmug.org>
and subject line Re: Bug#681656: Detect Network Hardware stops Wheezy install
has caused the Debian Bug report #681656,
regarding Detect Network Hardware stops Wheezy install
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.)


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

Just grabbed this ISO image:

debian-wheezy-DI-b1-i386-kde-CD-1.jigdo


Which is dated 15-JUL-2012 via Jigdo (verified Checksum as ok)

System is currently running Lenny (oldstable) and I'm planning on wiping it
and installing Wheezy...

However, the Wheezy installer stops at Detecting Network Hardware.. The
mouse cursor can freely move around the screen and it looks like the
installer doesn't try to detect any network hardware (no progress bar!).

Here are 3 screenshots..
http://imgur.com/a/3Fp0T

Not sure what to do from here as there doesn't seem to be any way to
continue the install.
--- End Message ---
--- Begin Message ---
Quoting ricky...@libero.it (ricky...@libero.it):
> Sorry for my bad english...
> I've the same problem, which DIDN'T appear in the ALPHA release. This bug is 
> shown only in the BETA WHEEZY release.
> If there is a non-free firmware, the installer stopped the installation.
> A solution can be insert a USB pendrive with the firmwares, it works for me.
> 
> Please, solve this bug, it's very important in my opinion. 


This is a known problem that has been identified in the kernel and
currently worked around in mountmedia. To go  around it, you need to
use daily built images.




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