Meanwhile, the amd64-microcode package made it to unstable.
I'll work with that for the next days, and see what can be done that way,
which is easier and faster on my end.
We can migrate it to firmware-nonfree later. It shouldn't be a problem,
since it will be multiarch-foreign anyway, regardles
On Sun, 2012-06-24 at 20:44 -0300, Henrique de Moraes Holschuh wrote:
> On Sun, 24 Jun 2012, Ben Hutchings wrote:
> > On Sun, 2012-06-24 at 13:05 -0300, Henrique de Moraes Holschuh wrote:
> > [...]
> > > > > 3. firmware-nonfree _really_ needs a README.source :-)
> > > >
> > > > Yeah.
> > [...]
> >
On Sun, 24 Jun 2012, Ben Hutchings wrote:
> On Sun, 2012-06-24 at 13:05 -0300, Henrique de Moraes Holschuh wrote:
> [...]
> > > > 3. firmware-nonfree _really_ needs a README.source :-)
> > >
> > > Yeah.
> [...]
>
> Fixed in svn; let me know if it's missing anything.
Ah, it helps a lot, thanks.
On Sun, 2012-06-24 at 13:05 -0300, Henrique de Moraes Holschuh wrote:
[...]
> > > 3. firmware-nonfree _really_ needs a README.source :-)
> >
> > Yeah.
[...]
Fixed in svn; let me know if it's missing anything.
Ben.
--
Ben Hutchings
I say we take off; nuke the site from orbit. It's the only way
On Sun, 24 Jun 2012, Ben Hutchings wrote:
> On Sun, 2012-06-24 at 12:21 -0300, Henrique de Moraes Holschuh wrote:
> > On Sat, 23 Jun 2012, Ben Hutchings wrote:
> > > > > The package template system currently only supports one optional
> > > > > postinst action, but it wouldn't be hard to extend to
On Sun, 2012-06-24 at 12:21 -0300, Henrique de Moraes Holschuh wrote:
> On Sat, 23 Jun 2012, Ben Hutchings wrote:
> > > > The package template system currently only supports one optional
> > > > postinst action, but it wouldn't be hard to extend to add others.
>
> Ok, I tried to ship the microcode
On Sat, 23 Jun 2012, Ben Hutchings wrote:
> > > The package template system currently only supports one optional
> > > postinst action, but it wouldn't be hard to extend to add others.
Ok, I tried to ship the microcode for amd processors using firmware-nonfree.
There are a few problems:
1. firmwa
On Sat, 23 Jun 2012, Ben Hutchings wrote:
> On Fri, 2012-06-22 at 23:49 -0300, Henrique de Moraes Holschuh wrote:
> > On Sat, 23 Jun 2012, Ben Hutchings wrote:
> > > On Fri, 2012-06-22 at 16:03 -0300, Henrique de Moraes Holschuh wrote:
> > > > On Fri, 22 Jun 2012, Ben Hutchings wrote:
> > > > > On
On Fri, 2012-06-22 at 23:49 -0300, Henrique de Moraes Holschuh wrote:
> On Sat, 23 Jun 2012, Ben Hutchings wrote:
> > On Fri, 2012-06-22 at 16:03 -0300, Henrique de Moraes Holschuh wrote:
> > > On Fri, 22 Jun 2012, Ben Hutchings wrote:
> > > > On Sat, 2012-06-16 at 15:08 -0300, Henrique de Moraes H
On Sat, 23 Jun 2012, Ben Hutchings wrote:
> On Fri, 2012-06-22 at 16:03 -0300, Henrique de Moraes Holschuh wrote:
> > On Fri, 22 Jun 2012, Ben Hutchings wrote:
> > > On Sat, 2012-06-16 at 15:08 -0300, Henrique de Moraes Holschuh wrote:
> > > > They have to:
> > > >
> > > > 1. Issue sysfs commands
On Fri, 2012-06-22 at 16:03 -0300, Henrique de Moraes Holschuh wrote:
> On Fri, 22 Jun 2012, Ben Hutchings wrote:
> > On Sat, 2012-06-16 at 15:08 -0300, Henrique de Moraes Holschuh wrote:
> > > On Tue, 12 Jun 2012, Daniel Baumann wrote:
> > > > On 06/12/2012 06:04 PM, Henrique de Moraes Holschuh wr
On Fri, 22 Jun 2012, Ben Hutchings wrote:
> On Sat, 2012-06-16 at 15:08 -0300, Henrique de Moraes Holschuh wrote:
> > On Tue, 12 Jun 2012, Daniel Baumann wrote:
> > > On 06/12/2012 06:04 PM, Henrique de Moraes Holschuh wrote:
> > > > I don't care as long as nobody is going to get in the way of an
>
On Sat, 2012-06-16 at 15:08 -0300, Henrique de Moraes Holschuh wrote:
> On Tue, 12 Jun 2012, Daniel Baumann wrote:
> > On 06/12/2012 06:04 PM, Henrique de Moraes Holschuh wrote:
> > > I don't care as long as nobody is going to get in the way of an
> > > urgency=high upload of firmware-nonfree to st
sounds all very reasonable to me, thanks Henrique.
--
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email: daniel.baum...@progress-technologies.net
Internet: http://people.progress-technologies.net/~daniel.baumann/
--
To UNSUBSCRIBE, email to debian-wnpp-requ..
On Tue, 12 Jun 2012, Daniel Baumann wrote:
> On 06/12/2012 06:04 PM, Henrique de Moraes Holschuh wrote:
> > I don't care as long as nobody is going to get in the way of an
> > urgency=high upload of firmware-nonfree to stable-proposed-updates or
> > stable-updates.
>
> there have been updates of f
On 06/12/2012 06:04 PM, Henrique de Moraes Holschuh wrote:
> I don't care as long as nobody is going to get in the way of an
> urgency=high upload of firmware-nonfree to stable-proposed-updates or
> stable-updates.
there have been updates of firmware-* packages in the past and more
recently for sq
On Tue, 12 Jun 2012, Daniel Baumann wrote:
> > so what is the point of adding it to firmware-nonfree?
>
> it would be nice to have everything in one place (= one src package),
> than to have things split over several, make the firmware stuff be
> updated all at once, and better integrated (by usin
On 06/12/2012 01:34 PM, Henrique de Moraes Holschuh wrote:
> However, amd64-microcode has a different upstream
iirc so do the different firmware parts that src:firmware-nonfree builds.
> and it would already
> have to generate a separate binary package anyway for license reasons,
iirc so are the
On Mon, 11 Jun 2012, Daniel Baumann wrote:
> On 06/10/2012 04:31 PM, Henrique de Moraes Holschuh wrote:
> > The microcode data file for Linux contains the latest microcode definitions
> > for all AMD AMD64 processors.
>
> i'm aware that there's the intel-microcode package, however, why not
> integ
On 06/10/2012 04:31 PM, Henrique de Moraes Holschuh wrote:
> The microcode data file for Linux contains the latest microcode definitions
> for all AMD AMD64 processors.
i'm aware that there's the intel-microcode package, however, why not
integrate this into firmware-nonfree (as firmware-amd-microc
Package: wnpp
Severity: wishlist
Owner: Henrique de Moraes Holschuh
* Package name: amd64-microcode
Version : 0.20120117
Upstream Author : AMD, Inc
* URL : http://www.amd64.org/support/microcode.html
* License : proprietary
Description : Processor microco
21 matches
Mail list logo
