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

Re: [Yaird-devel] Bug#457177: Bug#457177: keep yaird out of Testing

[final summary is at the end]

* Jonas Smedegaard (dr@jones.dk) [081231 19:00]:
> There has been progress.
> The issue he is specifically referring to above was cloned as 
> bug#457463. It was closed with the upload of yaird 0.0.13-1 5 months 
> ago.

Looking at the package archive shows:
     yaird |      yaird |   0.0.13-3 |      unstable | hppa, ia64, mips, mipsel, s390
     yaird |      yaird |   0.0.13-5 |      unstable | source, alpha, amd64, arm, armel, i386, powerpc, sparc

However, version 0.0.13-5 was uploaded on 29. Aug 2008. Why is this
package not uptodate on 5 architectures? What did you do to resolve
this problem?

Also, why are you discussing that now (as of end of December)? Was
there any progress since the upload of the package in August which I

Also, why should we accept this package into Lenny at this late stage
of the release process? What advantages would our users get by another
boot loader? (i.e. what can yaird do what other packages can't, and
how does that help our users?)

Which of the initial issue (as of maks report):

* overheating - none of the acpi modules lands on initramfs
  for some boxes it is *really* critical to load them earliest
* cmdline - ignores any of the boot passed arguments
  even critical ones like root, rootfs or rootdelay
* missing debian arch support - for example s390 
* UUID, Label - apparently only works for some fs
* missing firmware - several scsi drivers need firmware inside initramfs
  no loader on initramfs nor any mechanism to add it
* missing cryptsetup support see #336599
* no dmraid support
* no usplash support
* brutal hardcoding - breaks ony every new linux image
  either due to /proc, /sys or /boot/config hardcoded parsing
  see #443821 for the latest 2.6.23 variation
* dead upstream - 24 debian revsion

is resolved now? For which issue do you need more information from
maks but he refused to give them to you?

Looking at the following changelog entries:
  * Document limited support for firmware loading and encrypted disks
    (requires manual editing config files). Closes: bug#457463, #457464.
  * Add patch 2001 to disable INPUT, as a temporary workaround for
    recent kernels flagging more aggressively drivers offering buttons,
    until yaird gets support for more hardware or learns to suppress
    irrelevant button devices. Closes: bug#461997.  Add NEWS enry.
  * Semi-auto-update debian/control to apply above cdbs-related changes:
    DEB_AUTO_UPDATE_DEBIAN_CONTROL=yes fakeroot debian/rules clean
  * Add patch 1023 to only bail on encrypted root device with keyfiles
    (ignore non-root encrypted devices with keyfiles). This closes:
    bug#460818, thanks to Lubomir Host.
  * Add patch 1024 to load all available thermal modules. Closes:
    Bug#457459, thanks to maximilian attems.

they don't sound to me like it really should be. Documenting not
working stuff is of course better than nothing, but it is *not*
resolving the issue. Especially closing serious bug reports like
"missing firmware: no way to initiate some SCSI drivers" #457463 with
"it's documented it doesn't work" is not acceptable.

=> Summary: As things currently look to me, there are multiple reasons
why yaird shouldn't be part of Lenny, and I'm surprised why you're
trying to discuss that at the current moment, instead of fixing the
open issues.


Reply to: