Bug#707570: Error

2013-05-11 Thread Holger Wansing
Hi,

Cam Davies p...@live.com wrote:
 I typed pinggoogle and it says Unknown host.  I ytied tasksel and it did 
 nothing, I did debian desktop environent and it said command not found.  
 

So I would suspect you still have some problem with the network site, as it was
during installation as well.
Because of this network error during installation, the desktop environment
was not installed. 
And without network connection, you still cannot install it afterwards now.

If you log in as root: what's the output of 
ifconfig ?
In the output of lspci, is there a network card listed?


Holger



 On 2013-05-10, at 1:17 PM, Miguel Figueiredo el...@debianpt.org wrote:
 
  Em 10-05-2013 19:32, Holger Wansing escreveu:
  Hi,
  
  [...]
  
  From above I read, that the subscriber used a CD as installation
  medium, and the network configuration failed.
  So, it was an installation from a single CD, without network mirror.
  This most probably leads to a console-only install, without X.
  And I think, this is what the subscriber is missing: the graphical
  interface.
  
  Holger
  
  I've been discussing this by email with the OP and so it seems.
  If you don't oppose I will close the BR as it was a successful installation.



-- 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Created with Sylpheed 3.0.2
under  D e b i a n   G N U / L I N U X   6.0  ( S q u e e z e )
Registered LinuxUser #311290 - http://linuxcounter.net/
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =


-- 
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/20130511085434.0d76d3bf.li...@wansing-online.de



Bug#707567: marked as done (installation-reports: Wheezy i386 netinst fails installing base system: /var/cache/apt doesn't exist)

2013-05-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 May 2013 16:08:47 +0100
with message-id 518e5eff.4040...@debianpt.org
and subject line Re: Bug#707567: Installation finally worked after 
repartitioning and formatting
has caused the Debian Bug report #707567,
regarding installation-reports: Wheezy i386 netinst fails installing base 
system: /var/cache/apt doesn't exist
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.)


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

Error Message:

  [!!] Grundsystem Installieren
 Warnung: Failure trying to run: chroot /target dpkg --force depends --install
 /var/cache/apt/archives/base-files_7.1_i386.deb
 /var/cache/apt/archives/base-passwd_3.5.26_i386.deb

Actually, there is no directory apt in /var/cache/!
Anything I found in /var/cache was a lonely subdir anna with only the file 
Packages.default in it.

P.S.
df -Tl doesn't work within the busybox

-- Package-specific info:

Boot method: CD
Image version: 
http://cdimage.debian.org/debian-cd/7.0.0/i386/iso-cd/debian-7.0.0-i386-netinst.iso
 downloaded 2013-05-09
Date: 2013-05-09 11:39

Machine: Terra PIII-1GHz, 512MB RAM, 250GB Samsung HDD
Partitions: 
DeviceBoot StartEnd Blocks  Id System
/dev/sda1   * 63  485307584  242653761  83 Linux
/dev/sda2  485307646  4883920461542209+  5 Extended
/dev/sda5  485307648  4883920461542208+ 82 Linux Swap / Solaris


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

Comments/Problems:

After apt-get dist-upgrade failed leaving an unusable system (Bug#707045),
I decided to install Wheezy with a netinst-CD.
To archive a clean installation, i removed /usr, /bin, /var, ...
I kept /home (of course) and /etc, /mnt.

Of course I report these problems from a different machine.
So the information below isn't related to the PC with the 
installation problems.
But, before my attempt to upgrade to Wheezey, Debian 6.0.7 worked fine 
on both PCs

-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=5.0 (lenny) - installer build 20090123
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
umame -a: Linux Siemens 2.6.26-1-486 #1 Sat Jan 10 17:46:23 UTC 2009 i686 
unknown
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 
82443BX/ZX/DX Host bridge [8086:7190] (rev 03)
lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation 440BX/ZX/DX - 
82443BX/ZX/DX AGP bridge [8086:7191] (rev 03)
lspci -knn: 00:07.0 ISA bridge [0601]: Intel Corporation 82371AB/EB/MB PIIX4 
ISA [8086:7110] (rev 02)
lspci -knn: 00:07.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 
IDE [8086:7111] (rev 01)
lspci -knn: Kernel driver in use: PIIX_IDE
lspci -knn: Kernel modules: piix
lspci -knn: 00:07.2 USB Controller [0c03]: Intel Corporation 82371AB/EB/MB 
PIIX4 USB [8086:7112] (rev 01)
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci-hcd
lspci -knn: 00:07.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI 
[8086:7113] (rev 02)
lspci -knn: 00:0a.0 Multimedia audio controller [0401]: Ensoniq ES1371 
[AudioPCI-97] [1274:1371] (rev 02)
lspci -knn: 00:0e.0 Ethernet controller [0200]: 3Com Corporation 3c905C-TX/TX-M 
[Tornado] [10b7:9200] (rev 30)
lspci -knn: Kernel driver in use: 3c59x
lspci -knn: Kernel modules: 3c59x
lspci -knn: 00:10.0 USB Controller [0c03]: VIA Technologies, Inc. VT82x 
UHCI USB 1.1 Controller [1106:3038] (rev 61)
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci-hcd
lspci -knn: 00:10.1 USB Controller [0c03]: VIA 

Processed: your mail

2013-05-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 close 635882
Bug #635882 [debootstrap] Cannot create base.tgz on Sid
Bug #636023 [debootstrap] pbuilder fails to mount proc fs
Marked Bug as done
Marked Bug as done
 thanks
Stopping processing here.

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



Processed: Re: Bug#707789: requested info

2013-05-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 reassign 707789 flash-kernel
Bug #707789 [initramfs-tools] initramfs-tools: update-initramfs blocks with 
message root device ubi0:rootfs does not exist
Bug reassigned from package 'initramfs-tools' to 'flash-kernel'.
No longer marked as found in versions initramfs-tools/0.109.1.
Ignoring request to alter fixed versions of bug #707789 to the same values 
previously set
 stop
Stopping processing here.

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



Bug#707844: di-utils: No error message in case of wrong architecture

2013-05-11 Thread Salvo Tomaselli
Package: di-utils
Version: 1.92+deb7u1
Severity: minor

Dear Maintainer,
I've downloaded Debian 7.0 to use in a virtual machine.

I downloaded an amd64 image, and by mistake used qemu for i386.

I had the normal grub and then when selecting whether I wanted graphical
or normal installation, it would just hang and do nothing.
When trying to do an expert install it finally showed me what was
going on, and I could start qemu with the appropriate command line.

Could you make it print an error message in these cases, for any kind
of chosen kind of installation?
If a CD doesn't do anything but just hangs I could assume there is
something wrong with it, or the problem lies somewhere else.

Bye

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

Kernel: Linux 3.8.8a (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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/20130511195846.9408.40670.reportbug@localhost



Bug#707844: di-utils: No error message in case of wrong architecture

2013-05-11 Thread Robert Thomas Hayes Link
Dear Debian Bughunters:

This, for me, raises the question of when I should report what,
followed by, How, adequately?

I've got a dev setup that pretty much lets me bang away until
something works, then take snapshots when something interesting
happens (e.g., major package install finishes, run out of room on the
vm, c). But the box I'm working on is a hand-me down, with mint as
the can-opener, in which I run virtualbox, to acheive an approximation
of pure stable.

I would be delighted with feedback, off and on list, but the idea is
to contribute back, upstream, at least as good as I found it.

Best,

RL

 Package: di-utils
 Version: 1.92+deb7u1
 Severity: minor

 Dear Maintainer,
 I've downloaded Debian 7.0 to use in a virtual machine.

 I downloaded an amd64 image, and by mistake used qemu for i386.

 I had the normal grub and then when selecting whether I wanted
 graphical
 or normal installation, it would just hang and do nothing.
 When trying to do an expert install it finally showed me what was
 going on, and I could start qemu with the appropriate command line.

 Could you make it print an error message in these cases, for any kind
 of chosen kind of installation?
 If a CD doesn't do anything but just hangs I could assume there is
 something wrong with it, or the problem lies somewhere else.

 Bye

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

 Kernel: Linux 3.8.8a (SMP w/4 CPU cores)
 Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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/20130511195846.9408.40670.reportbug@localhost




Peace,

-- 
properclinic.com
unclog courts
go debian


--
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/e2f81864cfda8895525ab67ec40b763b.squir...@webmail.robertlink.org



Bug#699390: debian-policy: soften the wording recommending menu files

2013-05-11 Thread Michael Biebl
Hi Russ, hi Sune,

I'd like to second this request to reword the current section in the
policy regarding menu files, suggesting fdo .desktop files as the
recommended mechanism and make it clear that .menu files are only really
relevant for legacy or more exotic window managers.
Sune's patch looks fine to me.

As Sune already pointed out, the addition of menu-xdg actually is
harmful in case of modern DEs like KDE or GNOME, where the entries
generated via menu-xdg, duplicate a lot of existing entries, with no
icons or low res bitmaps, not translations etc and clutter it up in a
very bad way.
In GNOME shell this even leads to wrong application tracking, if the
wrong menu entry is chosen. That's why we decided to actively hide the
Debian menu.

Regarding the same issue, I talked to Christian, as tasksel
co-maintainer, a while ago, to drop menu from the desktop task. If my
memory serves me well, he basically agreed, but was worried, that my
request came rather late into the wheezy release, so I've filed [1] and
hope we can resolve that for jessie.

Regards,
Michael



[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699390
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#707890: Boot sequence stalls with message USB disconnect, device number

2013-05-11 Thread Runari


Package: installation-reports

Boot method: external USB hard drive
Image version: http://cdimage.debian.org/debian-cd/7.0.0/amd64/bt-dvd/
Date of install: around May 1, 2013

Machine: Apple iMac 12,1 (mid-2011 model, http://support.apple.com/kb/sp623)
Processor: 2.5GHz quad-core Intel Core i5
Memory: 4GB (2GBx2 1333MHz DDR3 memory)
Partitions: output of df -Tl
Filesystem Type 1K-blocks 
Used Available Use% Mounted on
rootfs rootfs 9612516  
5285112   3839112  58% /
udev   devtmpfs 10240   
 0 10240   0% /dev
tmpfs  tmpfs   403784  
852402932   1% /run
/dev/disk/by-uuid/5b9441e4-0101-45e0-9fb8-b27d55c51517 ext4   9612516  
5285112   3839112  58% /
tmpfs  tmpfs 5120   
 0  5120   0% /run/lock
tmpfs  tmpfs  3932600  
444   3932156   1% /run/shm
/dev/sdc4  ext4 263282748 
10232004 239676744   5% /home
/dev/sdc5  vfat 195213200  
2070080 193143120   2% /media/Storage


Output of lspci -knn:
00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor 
Family DRAM Controller [8086:0100] (rev 09)
Subsystem: Intel Corporation Device [8086:2010]
Kernel driver in use: agpgart-intel
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port [8086:0101] (rev 09)
Kernel driver in use: pcieport
00:02.0 Display controller [0380]: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller [8086:0102] (rev 09)
Subsystem: Intel Corporation Device [8086:2010]
Kernel driver in use: i915
00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
Subsystem: Intel Corporation Apple MacBookPro8,2 [Core i7, 15, 2011] 
[8086:7270]
00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset 
Family USB Universal Host Controller #5 [8086:1c2c] (rev 05)
Subsystem: Intel Corporation Apple MacBookPro8,2 [Core i7, 15, 2011] 
[8086:7270]
Kernel driver in use: uhci_hcd
00:1a.7 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset 
Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 05)
Subsystem: Intel Corporation Apple MacBookPro8,2 [Core i7, 15, 2011] 
[8086:7270]
Kernel driver in use: ehci_hcd
00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset 
Family High Definition Audio Controller [8086:1c20] (rev 05)
Subsystem: Intel Corporation Apple MacBookPro8,2 [Core i7, 15, 2011] 
[8086:7270]
Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset 
Family PCI Express Root Port 1 [8086:1c10] (rev b5)
Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset 
Family PCI Express Root Port 2 [8086:1c12] (rev b5)
Kernel driver in use: pcieport
00:1c.2 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset 
Family PCI Express Root Port 3 [8086:1c14] (rev b5)
Kernel driver in use: pcieport
00:1c.4 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset 
Family PCI Express Root Port 5 [8086:1c18] (rev b5)
Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset 
Family USB Universal Host Controller #1 [8086:1c27] (rev 05)
Subsystem: Intel Corporation Apple MacBookPro8,2 [Core i7, 15, 2011] 
[8086:7270]
Kernel driver in use: uhci_hcd
00:1d.7 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset 
Family USB Enhanced Host Controller #1 [8086:1c26] (rev 05)
Subsystem: Intel Corporation Apple MacBookPro8,2 [Core i7, 15, 2011] 
[8086:7270]
Kernel driver in use: ehci_hcd
00:1f.0 ISA bridge [0601]: Intel Corporation Z68 Express Chipset Family LPC 
Controller [8086:1c44] (rev 05)
Subsystem: Intel Corporation Device [8086:7270]
00:1f.2 SATA controller [0106]: Intel Corporation 6 Series/C200 Series Chipset 
Family SATA AHCI Controller [8086:1c02] (rev 05)
Subsystem: Intel Corporation Device [8086:7270]
Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 6 Series/C200 Series Chipset Family 
SMBus Controller [8086:1c22] (rev 05)
Subsystem: Intel Corporation Apple MacBookPro8,2 [Core i7, 15, 2011] 
[8086:7270]
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI 
Whistler [AMD Radeon HD 6600M Series] [1002:6741]
Subsystem: Apple Inc. Device [106b:6741]
Kernel 

Debian installer build: failed or old builds

2013-05-11 Thread Daily build aggregator
Debian installer build overview
---

Failed or old builds:

* FAILED BUILD: amd64 May 12 00:07 buildd@barber build_cdrom_isolinux 

http://d-i.debian.org/daily-images/amd64/daily/build_cdrom_isolinux.log

* FAILED BUILD: amd64 May 12 00:08 buildd@barber build_cdrom_gtk 

http://d-i.debian.org/daily-images/amd64/daily/build_cdrom_gtk.log

* FAILED BUILD: amd64 May 12 00:08 buildd@barber build_cdrom-xen 

http://d-i.debian.org/daily-images/amd64/daily/build_cdrom-xen.log

* FAILED BUILD: amd64 May 12 00:08 buildd@barber build_netboot 
http://d-i.debian.org/daily-images/amd64/daily/build_netboot.log

* FAILED BUILD: amd64 May 12 00:08 buildd@barber build_netboot-gtk 

http://d-i.debian.org/daily-images/amd64/daily/build_netboot-gtk.log

* FAILED BUILD: amd64 May 12 00:08 buildd@barber build_netboot-xen 

http://d-i.debian.org/daily-images/amd64/daily/build_netboot-xen.log

* FAILED BUILD: amd64 May 12 00:08 buildd@barber build_hd-media 

http://d-i.debian.org/daily-images/amd64/daily/build_hd-media.log

* FAILED BUILD: amd64 May 12 00:09 buildd@barber build_hd-media_gtk 

http://d-i.debian.org/daily-images/amd64/daily/build_hd-media_gtk.log

* FAILED BUILD: armel May 10 08:11 buildd@ancina build_iop32x_netboot 

http://d-i.debian.org/daily-images/armel/daily/build_iop32x_netboot.log

* FAILED BUILD: armel May 10 08:12 buildd@ancina 
build_iop32x_network-console_glantank 

http://d-i.debian.org/daily-images/armel/daily/build_iop32x_network-console_glantank.log

* FAILED BUILD: armel May 10 08:12 buildd@ancina 
build_iop32x_network-console_n2100 

http://d-i.debian.org/daily-images/armel/daily/build_iop32x_network-console_n2100.log

* FAILED BUILD: armel May 10 08:13 buildd@ancina 
build_iop32x_network-console_ss4000e 

http://d-i.debian.org/daily-images/armel/daily/build_iop32x_network-console_ss4000e.log

* FAILED BUILD: armel May 10 08:13 buildd@ancina build_kirkwood_netboot 

http://d-i.debian.org/daily-images/armel/daily/build_kirkwood_netboot.log

* FAILED BUILD: armel May 10 08:14 buildd@ancina build_kirkwood_netboot-gtk 

http://d-i.debian.org/daily-images/armel/daily/build_kirkwood_netboot-gtk.log

* FAILED BUILD: armel May 10 08:15 buildd@ancina build_kirkwood_network-console 

http://d-i.debian.org/daily-images/armel/daily/build_kirkwood_network-console.log

* FAILED BUILD: armel May 10 08:15 buildd@ancina build_orion5x_network-console 

http://d-i.debian.org/daily-images/armel/daily/build_orion5x_network-console.log

* FAILED BUILD: armel May 10 08:16 buildd@ancina build_versatile_netboot 

http://d-i.debian.org/daily-images/armel/daily/build_versatile_netboot.log

* FAILED BUILD: i386 May 12 00:06 buildd@biber build_cdrom_isolinux 

http://d-i.debian.org/daily-images/i386/daily/build_cdrom_isolinux.log

* FAILED BUILD: i386 May 12 00:06 buildd@biber build_cdrom_gtk 

http://d-i.debian.org/daily-images/i386/daily/build_cdrom_gtk.log

* FAILED BUILD: i386 May 12 00:06 buildd@biber build_cdrom-xen 

http://d-i.debian.org/daily-images/i386/daily/build_cdrom-xen.log

* FAILED BUILD: i386 May 12 00:06 buildd@biber build_netboot 
http://d-i.debian.org/daily-images/i386/daily/build_netboot.log

* FAILED BUILD: i386 May 12 00:06 buildd@biber build_netboot-gtk 

http://d-i.debian.org/daily-images/i386/daily/build_netboot-gtk.log

* FAILED BUILD: i386 May 12 00:06 buildd@biber build_netboot-xen 

http://d-i.debian.org/daily-images/i386/daily/build_netboot-xen.log

* FAILED BUILD: i386 May 12 00:07 buildd@biber build_hd-media 
http://d-i.debian.org/daily-images/i386/daily/build_hd-media.log

* FAILED BUILD: i386 May 12 00:07 buildd@biber build_hd-media_gtk 

http://d-i.debian.org/daily-images/i386/daily/build_hd-media_gtk.log

* FAILED BUILD: ia64 May 12 00:13 buildd@alkman build_cdrom 
http://d-i.debian.org/daily-images/ia64/daily/build_cdrom.log

* FAILED BUILD: ia64 May 12 00:14 buildd@alkman build_netboot 
http://d-i.debian.org/daily-images/ia64/daily/build_netboot.log

* OLD BUILD:kfreebsd-amd64 May 08 00:55 buildd@fano build_cdrom_grub 

http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_cdrom_grub.log

* OLD BUILD:kfreebsd-amd64 May 08 00:55 buildd@fano build_cdrom_gtk 

http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_cdrom_gtk.log

* OLD BUILD:kfreebsd-amd64 May 08 00:58 buildd@fano build_netboot 

http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot.log

* OLD BUILD:kfreebsd-amd64 May 08 01:01 buildd@fano build_netboot-9 


Bug#699390: debian-policy: soften the wording recommending menu files

2013-05-11 Thread Lisandro Damián Nicanor Pérez Meyer
On Sat 11 May 2013 21:04:01 Michael Biebl escribió:
 Hi Russ, hi Sune,
 
 I'd like to second this request to reword the current section in the
 policy regarding menu files, suggesting fdo .desktop files as the
 recommended mechanism and make it clear that .menu files are only really
 relevant for legacy or more exotic window managers.
 Sune's patch looks fine to me.

+1 from my side too.


-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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


Re: partman-zfs

2013-05-11 Thread Turbo Fredriksson
On May 11, 2013, at 12:25 AM, Turbo Fredriksson wrote:

 It seems that partman-zfs isn't quite finished. It
 doesn't create a root filesystem. Only allows you to
 create a volume, and on that put a root fs...
 
 I've added support for creating a root fs, setting the
 'bootfs' flag. I'm currently debugging it and trying
 to find every gotcha. I'll post a patch 'shortly'.

Patch is at https://github.com/FransUrbo/debian-partman-zfs/commits/master
in four different commits.

It's a little crude as yet, but it should be enough to
'get the ball rolling'...

Please test and give me comments.



Turbo Fredriksson (4):
  Support arch linux-any.
  + If os=linux, then modprobe and enable zfs partitioner.
  + Make absolutly sure that /boot/zfs exists before trying to import
a ZFS pool - will fail if pool exists, but /boot/zfs doesn't.
  + Since loading the module might take 'a while', show progress info.
  + Don't automatically mount the file system(s) when importing the pool.
  + If os=linux, then create the ZVOL with volblocksize=4096.
  + Add some support functions: fs_create(), fs_check_exists(), 
get_vg_value().
  + Support creating and mounting a ZFS (not ZVOL) and make it a root file 
system.

 choose_partition/zfs/do_option |   75 ++
 debian/changelog   |   12 
 debian/control |6 +-
 debian/partman-zfs.templates   |   48 +--
 fstab.d/zfs|   20 ++
 init.d/zfs-devices |   20 +-
 lib/zfs-base.sh|  134 +++-
 mount.d/zfs|   21 ++-
 8 files changed, 320 insertions(+), 16 deletions(-)
--
Build a man a fire, and he will be warm for the night.
Set a man on fire and he will be warm for the rest of his life.


--
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/7ebd79fc-5013-474e-b514-ae0793a95...@bayour.com



Re: partman-zfs

2013-05-11 Thread Christian PERRIER
(no need to CC me now : I'm subscribed to -boot and will follow this thread)

Quoting Turbo Fredriksson (tu...@bayour.com):
 On May 11, 2013, at 12:25 AM, Turbo Fredriksson wrote:
 
  It seems that partman-zfs isn't quite finished. It
  doesn't create a root filesystem. Only allows you to
  create a volume, and on that put a root fs...
  
  I've added support for creating a root fs, setting the
  'bootfs' flag. I'm currently debugging it and trying
  to find every gotcha. I'll post a patch 'shortly'.
 
 Patch is at https://github.com/FransUrbo/debian-partman-zfs/commits/master
 in four different commits.
 
 It's a little crude as yet, but it should be enough to
 'get the ball rolling'...
 
 Please test and give me comments.

Hello,

Thanks a lot for your work and caring about this. AFAIK, partman-zfs
didn't receive much attention during last months.

I can't really test myself but I'd be happy if someone cared eough
about partman-zfs to keep it maintained.

I you have an Alioth accound, how about validating it for D-I and
pushing your patch there, then uploading?

We're in early D-I development process, so we now may want to make
things released as soon as possible so that they can get real testing.





signature.asc
Description: Digital signature