ddress issues if the maintainers / teams /
whoever fail to address them by themself. So for now, I'm not going to
force anybody to something. But I definitly will discuss issues with
different people during debconf.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
--
To UNSUBSCRIBE, emai
* Bastian Blank ([EMAIL PROTECTED]) [060428 22:50]:
> On Sat, Apr 22, 2006 at 08:33:38PM +0200, Andreas Barth wrote:
> > A combination of a working patch in the most current point release,
> > documentation in the etch release notes and a conflict with the current
> > p
s may be the case.
A combination of a working patch in the most current point release,
documentation in the etch release notes and a conflict with the current
package in sarge might however do the trick.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
--
To UNSUBSCRIBE, email to [EMAIL PROTE
h the core sarge tools
(whether the tools are dpkg or grub or ...). Can't the kernel packages
detect whether they have the sarge or the etch version of grub, and
behave acordingly?
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
at
correct?
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
we just let this be silent for a few days, and I'll
try to actively mediate it.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
itten for.
> This is incorrect. I know firmware[tm] blobs which only includes data.
> You can't decide if it is something which can be executed somewhere.
Can you define what "execute" means? Is it execution if e.g. data is
processed that defines a sound-wave for a DSP?
Cheers,
And
* Sven Luther ([EMAIL PROTECTED]) [060110 21:16]:
> On Tue, Jan 10, 2006 at 05:19:47PM +0100, Andreas Barth wrote:
> > difference to this. It might however make an difference to
> > GPL-compatibility, unless the license is GPL-compatible anyways.
>
> Nope, please read my
he kernel during link time) doesn't make any
difference to this. It might however make an difference to
GPL-compatibility, unless the license is GPL-compatible anyways.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "u
ething in the next release update.)
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi,
* Sven Luther ([EMAIL PROTECTED]) [060108 14:00]:
> On Sun, Jan 08, 2006 at 11:52:20AM +0100, Andreas Barth wrote:
> > What needs to be done to get the infrastructure ready? Do you think it
> > might make sense to try to get it done e.g. at a BSP?
> waldi is working on it
ream work than debian work, it is the better solution though,
> not sure if it would be ready for the etch timeframe though.
The question of sloppy licenses is indeed an upstream issue - however,
that doesn't mean we can shut our eyes when we come over such an issue.
The DFSG-freeness is our
before we can
release etch.
Now, my question is: Is there still work open? If so, what? Or is the
current removal of firmware enough, and we can relax on this topic?
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
* Sven Luther ([EMAIL PROTECTED]) [060103 23:02]:
> On Tue, Jan 03, 2006 at 10:31:38PM +0100, Andreas Barth wrote:
> > the other hand side, the difference is only one week - and if nothing is
> > broken by that, we can freeze the kernel at N-110 also.
> i think comparing t
at 09:24:19PM +0100, Andreas Barth wrote:
> > N-117 = Mon 30 Jul 06: freeze essential toolchain, kernels
> > N-110 = Mon 7 Aug 06: freeze base, non-essential toolchain (including
> > e.g. cdbs)
>
> Why do you put the kernel together with th
u need a newer udev, this driver doesn't
work anymore, ...}." I personally consider this as not really good.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
this way), it'll be a serious
time-sucker for getting all the issues resolved before we release it.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi,
* Andreas Barth ([EMAIL PROTECTED]) [051229 13:12]:
> * Sven Luther ([EMAIL PROTECTED]) [051229 13:05]:
> > > - Any security issues that happen need to be resolved - so we should
> > > limit the number of versions we offer.
> > Indeed, so the best is to have
* Sven Luther ([EMAIL PROTECTED]) [051229 13:05]:
> On Thu, Dec 29, 2005 at 12:15:53PM +0100, Andreas Barth wrote:
> > * Sven Luther ([EMAIL PROTECTED]) [051229 11:47]:
> > > The main problem are the too strict rules for building in volatile, which
> > > stop
> >
,
Andi
--
http://home.arcor.de/andreas-barth/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
to be mail, the wiki is more for
summarizing things up.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
r, I'm wary of uploading patched kernels to the
> main archive for all the different flavors as this would quickly
> result in a looong list of available kernels, which can cause
> confusion.
We could always decide later on to put some special kernel variants also
on the main archive.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ld know what you are getting
> into.
Well, perhaps we even should make the patches to be part of the
filename, so you can get something like
deb $url vserver/
oder
deb $url vserver-grsecurity/
With this szenario, you get only the kernels to see that you really
want.
Cheers,
Andi
--
, my question is: Is there some way to tell "everytime a new kernels
appears at $location, please apply all patches in $directory, and
compile it with this and that config for me"? If not, which would be the
way to do this?
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
--
T
* Sven Luther ([EMAIL PROTECTED]) [051028 20:04]:
> On Fri, Oct 28, 2005 at 10:46:02AM -0600, dann frazier wrote:
> > Andreas Barth has kindly offered to host debian.kernel.net on a system
> > which will have access to a buildd network (the same one that builds
> > expe
* Bastian Blank ([EMAIL PROTECTED]) [050830 11:22]:
> On Tue, Aug 30, 2005 at 06:08:56PM +0900, Horms wrote:
> > Due to growing frustrations with the continual changes to
> > the irc infastructure on freenode.net, such as no longer
> > being able to send messages as an unregistered user,
> This is
* Horms ([EMAIL PROTECTED]) [050811 23:46]:
> On Wed, Aug 10, 2005 at 07:56:00AM +0200, Sven Luther wrote:
> > > The latter, according to volatile policy (... must be autobuildable
> > > from the same release...).
> Is that part of the policy intended preclude providing an update to
> kernel-pac
* Horms ([EMAIL PROTECTED]) [050801 12:42]:
> On Mon, Aug 01, 2005 at 12:14:24PM +0200, Andreas Barth wrote:
> > * Horms ([EMAIL PROTECTED]) [050801 12:01]:
> > > On Mon, Aug 01, 2005 at 11:52:48AM +0200, Andreas Barth wrote:
> > > > Yes, that was about my intention
* Horms ([EMAIL PROTECTED]) [050801 12:01]:
> On Mon, Aug 01, 2005 at 11:52:48AM +0200, Andreas Barth wrote:
> > Yes, that was about my intention as well. So, yes, please move forward
> > with 2.4.27 and 2.6.8 and send a list of recommended updates.
> I need to go through th
* Horms ([EMAIL PROTECTED]) [050801 11:43]:
> On Mon, Aug 01, 2005 at 09:28:37AM +0200, Andreas Barth wrote:
> > * Horms ([EMAIL PROTECTED]) [050801 08:23]:
> > > I am wondering if others thing that volatile is a good
> > > place for us to make uploads of updated
* Horms ([EMAIL PROTECTED]) [050801 08:23]:
> I am wondering if others thing that volatile is a good
> place for us to make uploads of updated 2.6.8 and 2.4.27 kerels for
> Sarge? This would allow us to remove these kernels from unstable/testing
> and still provide maintenence releases for users.
this, built against k-t-2.4.27-9 (or 10?), these packages
> should not go into sarge? Did you file a bug or is the changelog entry
> sufficient?
As far as I can see, this package is already frozen - so there is no
danger of it going into sarge.
Cheers,
Andi
--
http://home.arcor.de/
manager first.
For a consolidated view, please see
http://neualius.turmzimmer.net/~aba/kernel-irc-summary
and for the log
http://neualius.turmzimmer.net/~aba/kernel-irc-log
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D
om/projects/netdev/archive/2005-04/msg00241.html
If you cannot attend this meeting, please consider to forward any issues
and reasons to any of Simon Horman (horms), Andres Salomon (dilinger) or
me.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9
* Andreas Barth ([EMAIL PROTECTED]) [050328 20:35]:
> If I understood the comments in base-installer/kernel/README correct,
> only the architectures with shell scripts that use KERNEL_ABI have this
> problem? If this is true, we only have it on hppa and s390, and in this
> case, I thi
* Andreas Barth ([EMAIL PROTECTED]) [050327 20:35]:
> Or, the generic solution would be to update update the udeb now in a way
> that it always downloads an appropriate meta-package (yes, that would be
> quite many meta-packages), so that we can can update the kernel and just
> upd
8 2.6.8-15 to sid.
Would would be the reason to not upload them? (And, IIRC, others archs
already updated to use the most recent kernelsource package.)
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
--
To UNSUBSCRIBE
ns
and the others who helped me.)
* Frans Pop ([EMAIL PROTECTED]) [050326 12:15]:
> On Saturday 26 March 2005 11:45, Andreas Barth wrote:
> > system 5. remove old udebs:
> >breaks businesscard cds the hard way, because they want to retrieve
> >them
&g
#288180 that I'm already
aware off)?
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
d by us.
Does that sound not too unreasonable?
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
* Martin Schulze ([EMAIL PROTECTED]) [050325 17:50]:
> Andreas Barth wrote:
> > Ok, summarising this means for me:
> >
> > If we change the abi for d-i, than a lot of work at a lot of places
> > needs to be done. Definitly possible, but not the thing we want to do
&g
* Joey Hess ([EMAIL PROTECTED]) [050325 17:05]:
> Andreas Barth wrote:
> > [What changes to d-i need to be done for a security upload?]
> Besides building the udebs, if the abi changes we have to update rootskel,
> base-installer, and the debian-installer build system.
>&
stem
> unbootable.
>
> It's a standard part of my system administration practices to keep a
> previous kernel version around that I can roll back to when upgrading to a
> new version; this approach would seem to make that more awkward.
That tells me that we should consider any kerne
lease team.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
over and over
> again, without an actual release. I sincerely hope sarge is ready in 1-2
> months.
I currently consider the kernel ABI-change the slowest part we (may)
need to finish for release.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85
ly great if we can manage to keep the heat out, that
would help us all to do a better (and more enjoyable) job.
Thanks for your attention,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
--
To UNSUBSCRIBE, email to [EMAIL PROTECT
* Andreas Barth ([EMAIL PROTECTED]) [041102 10:05]:
> * Steve Langasek ([EMAIL PROTECTED]) [041101 22:05]:
> > Package: kernel-image-2.4.27-netwinder
> > [...]
> > Version: 2.4.27
> > [...]
> > Depends: initrd-tools (>= 0.1.32), coreutils (>= 5.0), modutils
* Steve Langasek ([EMAIL PROTECTED]) [041101 22:05]:
> On Mon, Nov 01, 2004 at 10:00:00PM +0100, Andreas Barth wrote:
> > I think it is sufficient if the kernel is in sarge, e.g. 2.4.27, which
> > is above 2.4.24. Of course, this should be tested with exactly the
> > ke
* Steve Langasek ([EMAIL PROTECTED]) [041101 21:45]:
> On Fri, Oct 29, 2004 at 08:44:33PM +0200, Andreas Barth wrote:
>
> > during my investigation for the next release update, it seems that there
> > are more upgrade issues related to the kernel than I had tought. With
> &g
release. This said, I'd of course welcome if the emulation becomes
stable enough for release.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
.4.25-mips/2.4.25-0.040415.1
kernel-image-2.6.5-i386/2.6.5-4
kernel-image-2.6.6-i386/2.6.6-2
kernel-image-2.6.6-ia64/2.6.6-3
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
blobs are not allowed directly in the kernel, including not in modules.[1]
Cheers,
Andi
[1] http://lists.debian.org/debian-release/2004/04/msg00060.html
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
a comment that
this mean: Please look at 2.6.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
er works fine without the firmware on
> most cards it supports; the firmware is only needed in a few cases.
Please seperate two issues:
1. Are we distributing undistributalbe files?
2. Are we distributing non-free files in main?
This discussion was about 1., not about 2.
Cheers,
Andi
--
ept that?
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
te a README? Or should I just go ahead and upload the appropriate
> > files?
> Is anyone still using real i386 cpus?
See Bug #241497: yes. This problem was detected by an user, and so we
should solve it IMHO appropriate.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
upload? Just as "byhand",
and you sort it in? And how is the packages-file generated? In which
form do you want to have the README-file for that directory?
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
-i386.
As this bug is open since some time, my question is this:
Does anyone of you feel obligated to upload a kernel, tools and/or to
write a README? Or should I just go ahead and upload the appropriate
files?
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1
id of
> raidtools?
AFAIK we won't be able to kick off 2.2 for sarge. IIRC 2.2 will
probably be necessary for some m68k- and sparc-variants. I added
debian-kernel, perhaps we get some comment of the kernel-maintainers
whether they consider the raidtools to be necessary.
Cheers,
Andi
--
's not going to respond.
Are you up for a troll? Create fixes if you like, but don't whine
about problems that are likly to be not critical for sarge.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
* Francesco P. Lovergine ([EMAIL PROTECTED]) [040603 16:25]:
> On Thu, Jun 03, 2004 at 02:02:53PM +0200, Andreas Barth wrote:
> > * Robert Millan ([EMAIL PROTECTED]) [040603 13:55]:
> > > On Thu, Jun 03, 2004 at 07:11:01PM +1000, Herbert Xu wrote:
> > > > I thought t
* Robert Millan ([EMAIL PROTECTED]) [040603 14:25]:
> On Thu, Jun 03, 2004 at 01:32:59PM +0200, Andreas Barth wrote:
> > There
> > are proposals to override the SC for the release of sarge.
> Please answer this: Since you agree with proposals for future versions of the
>
developers want to release now? Please wait for the decision of the
developers in the GR. There is no need to rush now.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
* Robert Millan ([EMAIL PROTECTED]) [040603 13:25]:
> On Thu, Jun 03, 2004 at 11:09:49AM +0200, Andreas Barth wrote:
> > * Robert Millan ([EMAIL PROTECTED]) [040603 10:55]:
> > > Bear in mind that violating the DFSG is a release-critical bug, whereas
> > > disabling u
bian-release/2004/04/msg00060.html
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
s worth to go to a
unified kernel source package after release of sarge or not.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
* Jens Schmalzing ([EMAIL PROTECTED]) [040525 20:40]:
> Andreas Barth writes:
> > And the security team has already requested to reduce the number of
> > source packages drastically. So, I'm on the side of the security
> > team, i.e. to go to as less source packages as
* Sven Luther ([EMAIL PROTECTED]) [040524 18:10]:
> On Mon, May 24, 2004 at 05:26:48PM +0200, Andreas Barth wrote:
> > * Sven Luther ([EMAIL PROTECTED]) [040524 16:10]:
> > > On Mon, May 24, 2004 at 09:42:46AM -0400, Clint Adams wrote:
> > > > > Given that ever
o implement in any case - and are the
more important goals.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
eam has already requested to reduce the number of
source packages drastically. So, I'm on the side of the security team,
i.e. to go to as less source packages as possible.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
* Thiemo Seufer ([EMAIL PROTECTED]) [040523 21:25]:
> Andreas Barth wrote:
> [snip]
> > Sometimes there are more than one kernel version on a specific
> > architecture in testing.
> > http://people.debian.org/~aba/merkel/kernels.txt lists for which this
> > is curre
I file removal-requests
if there is more than one version in testing? Or something else? (And,
of course, this could be different from maintainer to maintainer, so
it's open to your individual decision.)
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6
patch-2.4.25-mips/2.4.25-0.040415.1 (2.4.25-0.040415.1)
# ignore version kernel-patch-2.4.25-powerpc/2.4.25-8 (2.4.25-8)
# ignore version xen/1.2-4 (1.2-4)
Any comments on this?
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
* Christian T. Steigies ([EMAIL PROTECTED]) [040517 16:10]:
> On Mon, May 17, 2004 at 03:35:34PM +0200, Andreas Barth wrote:
> > All I wish is that we reduce the number of source packages for the
> > kernel, to ease the load for the security team.
> I don't see how th
* Christian T. Steigies ([EMAIL PROTECTED]) [040517 12:10]:
> On Mon, May 17, 2004 at 10:02:03AM +0200, Andreas Barth wrote:
> > * Francesco P. Lovergine ([EMAIL PROTECTED]) [040517 09:55]:
> > > On Sun, May 16, 2004 at 09:34:46AM +0200, Andreas Barth wrote:
> >
> >
* Francesco P. Lovergine ([EMAIL PROTECTED]) [040517 09:55]:
> On Sun, May 16, 2004 at 09:34:46AM +0200, Andreas Barth wrote:
> > One other change I'd like to see ASAP is to having a "first class
> > architecture set" instead of a individual kernel for i386 and alpha
" /
I was also considering to step forward, but of course, I prefer if
someone else does it. ;)
One other change I'd like to see ASAP is to having a "first class
architecture set" instead of a individual kernel for i386 and alpha
(and possible more to add to this).
Cheers
101 - 178 of 178 matches
Mail list logo
