Re: Bug#209240: NMU proposal for discover (i18n issues)
Am Die, den 18.11.2003 schrieb Branden Robinson um 16:43:
> [Please CC me on replies.]
>
> On Tue, Nov 18, 2003 at 04:38:20PM +0100, Petter Reinholdtsen wrote:
> > [Branden Robinson]
> > > Please feel free to go ahead.
> > >
> > > Progeny is concentrating on Discover 2.x:
> >
> > This sounds very good. When will this result in replies regarding the
> > patches we have been working on in the d-i team to get it to work with
> > d-i. As far as I know, we are now waiting for Progeny to get back to
> > us with comments on the patches so we can make up a plan to continue
> > the transition process to get d-i to use discover 2.
>
> The last I heard, Jeff Licquia had applied the patches you needed. Some
> of those have been reverted in the latest CVS snapshot, but the
> changelog explains all.
Unfortunately I can not find the changelog in the pre 2.0.2 tarball on
the progeny website. Where can I find it?
>
> For example, it turns out a "di-discover" tool wasn't needed after all;
> it was possible to pass arguments to the existing discover utility to
> get output in the format desired by the d-i team.
>
> * discover/discover/Makefile.in
> discover/discover/didiscover.c
> Remove didiscover.c. The effects of
> didiscover --data-path --data-vendor
> didiscover --data-path --data-model
> are achieved with
> discover -t --no-model
> discover -t --no-vendor
>
> Can you please refresh my memory on any other outstanding issues? I
> will open tickets for them in Progeny's RequestTracker system.
I sent 2 sets of patches[1][2] to Jeff and Eric, which as far as I could
see are not integrated in the snapshot and on which we had no feedback
so far. Also petter sent a mail asking for the current status of the
integration of discover2 into debian[3] which is unanswered until now.
Additionally it would be nice to have a newer discover-data package. The
newest I have found so far is about one year old and only contains very
few usable entries for usb devices.
We would also be interested to know your plans on how to get discover2
into the debian archive. Are you planning to replace discover1 or will
there be a new discover2 package. The debian-installer team would like
to be able to have discover1 and 2 in parallel to be sure to have a
working configuration while testing discover2. So please don't remove
discover1.
Thanks for your reply
gaudenz
[1]http://lists.debian.org/debian-boot/2003/debian-boot-200310/msg00042.html
[2]http://lists.debian.org/debian-boot/2003/debian-boot-200310/msg00835.html
[3]http://lists.debian.org/debian-boot/2003/debian-boot-200311/msg00543.html
>
> --
> Branden Robinson | GPG signed/encrypted mail welcome
> branden@progeny.com | 1024D/9C0BCBFB
> Progeny Linux Systems | D5F6 D4C9 E25B 3D37 068C
> | 72E8 0F42 191A 9C0B CBFB
>
Reply to: