[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#540000: marked as done (live-initramfs: can not mount /dev/loop0 (/live/image/live/filesystem.squashfs) on //filesystem.squashfs)



Your message dated Thu, 06 Aug 2009 01:16:52 +0200
with message-id <4A7A12E4.6050607@debian.org>
and subject line Re: Bug#540000: live-initramfs: can not mount /dev/loop0 (/live/image/live/filesystem.squashfs) on //filesystem.squashfs
has caused the Debian Bug report #540000,
regarding live-initramfs: can not mount /dev/loop0 (/live/image/live/filesystem.squashfs) on //filesystem.squashfs
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 owner@bugs.debian.org
immediately.)


-- 
540000: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540000
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: live-initramfs
Severity: normal

the bug was found after creating a recovery cd using live-helper

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

Kernel: Linux 2.6.26-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF8)
Shell: /bin/sh linked to /bin/bash



--- End Message ---
--- Begin Message ---
Jeff Chimene wrote:
> Then just close the bug, Daniel. I don't have more info. It looks like
> live-helper is using live-initramfs incorrectly. As far as I can tell,
> my job is just to report the bug.

your bug report is as helpful as 'i installed debian and the kernel
doesn't boot'.

first of all, when you build a live system with live-helper, there can
be hundrets of combinations, or even millions if one counts in the
package selection. there is no possible way to know or guess which
configuration you were using/building.

and even if we know, it always takes a lot of time to reproduce things.
for almost all bugs, i have spend at least *one* hour just to reproduce
things. and that is in the best case, where the submitter did give all
the required information (and yes, i have a bunch of fast machines at
home to do that sort of things in fastest time there can be)...

> Thanks /so much/ for your time and administrative attitude.
> 
> I've already removed live-helper from this system. Please feel free to
> carry on w/ your oh-so-justified existence as a prized debian developer.

...therefore, it is totally reasonable to ask you for the required
information and absolutely no grounds to be agressive.

second of all, when building images of unstable or testing, there are
times where it's not working due to the state of the archive. for those
situations were testing or unstable are known to be broken, we note this
under 'image status' on our website, where we link to a workaround.
maybe you've build testing and hit the squashfs version mismatch which
is referenced in the current image status?

however. come back when you are in a cooperative mood. until then, i'll
close the bug as you requested.

Regards,
Daniel

-- 
Address:        Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:          daniel.baumann@panthera-systems.net
Internet:       http://people.panthera-systems.net/~daniel-baumann/


--- End Message ---

Reply to: