I did try to compile the 6.5.12 kernel over the weekend, and I got Makefile
errors, BUT, I applied the 6.5 realtime patch first, so the problem may
have been in the patch, and not in the kernel source itself. I should try
compiling an unpatched 6.5.12 kernel to be sure it's an issue with the
patch.
Le 20/06/2023 à 01:19, Ian Tan a écrit :
Hello,
Apologies for sending "rich text" of the same email previously. That
was an accident.
Here should be the plain text now.
Due to upstream issues, Virtualbox is not available on bookworm.
I have an urgent business use case, that required virtualbox
Roberto C. Sánchez writes:
> On Thu, Feb 16, 2023 at 10:37:00AM +0100, Andreas Leha wrote:
>>
>> Dear Tomas,
>>
>> Thanks for the swift reply!
>>
>> OK, then I should do `quilt pop -a` before the second compilation,
>> right?
>>
>> But that leads to another error message:
>>
>
> This can be
On Thu, Feb 16, 2023 at 10:37:00AM +0100, Andreas Leha wrote:
>
> Dear Tomas,
>
> Thanks for the swift reply!
>
> OK, then I should do `quilt pop -a` before the second compilation,
> right?
>
> But that leads to another error message:
>
This can be considered a bug in the package. The idea i
writes:
> On Thu, Feb 16, 2023 at 10:05:54AM +0100, Andreas Leha wrote:
>> Dear all,
>>
>> I am re-compiling xscreensaver.
>>
>> Re-compiling once works fine:
>>
>> apt-get source xscreensaver
>> cd xscreensaver-6.0.6+dfsg1
>
On Thu, Feb 16, 2023 at 10:05:54AM +0100, Andreas Leha wrote:
> Dear all,
>
> I am re-compiling xscreensaver.
>
> Re-compiling once works fine:
>
> apt-get source xscreensaver
> cd xscreensaver-6.0.6+dfsg1
> LANG=C debuild -us -uc
>
>
> R
Dear all,
I am re-compiling xscreensaver.
Re-compiling once works fine:
apt-get source xscreensaver
cd xscreensaver-6.0.6+dfsg1
LANG=C debuild -us -uc
Re-compiling a second time errors out, though:
> LANG=C debuild -us -uc
(skipped lines)
dpkg-source: info: us
Franco Martelli, on 2019-08-20:
> mm/memory.o: warning: objtool: remap_pfn_range()+0xd5: unsupported
> intra-function call
>
> that it's part of linux-kbuild-4.19 package maybe I should submit a bug
> report to this package or is another one a better choice?
Hi Franco,
Should you submit a bug re
On 19/08/19 at 21:18, Étienne Mollier wrote:
> Franco Martelli, on 2019-08-19:
>> I was thinking to submit a bug report against gcc-8 package. Now that I
>> have a work around, "bdver1" compiles without warnings, I can say
>> enough, what do you think about?
>
> I don't know, to me it sounds more
Franco Martelli, on 2019-08-19:
> I was thinking to submit a bug report against gcc-8 package. Now that I
> have a work around, "bdver1" compiles without warnings, I can say
> enough, what do you think about?
I don't know, to me it sounds more like little bugs on kernel
side, patches silencing war
I was thinking to submit a bug report against gcc-8 package. Now that I
have a work around, "bdver1" compiles without warnings, I can say
enough, what do you think about?
Best regards
--
Franco Martelli
Franco Martelli, on 2019-08-16:
> On 16/08/19 at 17:22, Étienne Mollier wrote:
[...]
> > Compilers may have good optimization routines to boost the speed
> > of the code in several situations, but in other ones there are
> > trade-offs to take between size and performance of the code. I
> > person
On 16/08/19 at 17:22, Étienne Mollier wrote:
> Bonjour,
>
> Woops, this sounds a bit like I might not have used a very clear
> wording. If I were at your place, I would proceed so; but I
> don't have a Piledriver CPU to do actual testing on my side.
> I'm still stuck with an old K10, not to menti
Bonjour,
Franco Martelli, on 2019-09-14:
> On 13/08/19 at 19:35, Étienne Mollier wrote:
[...]
> > I would do a few tests with a virtual
> > machine supporting bdver2 instructions before going live anyway,
> > and backups stored far away from the machine once testing, and
> > po
On 13/08/19 at 19:35, Étienne Mollier wrote:
> Hi Franco,
>
> I'm not fluent enough in GCC 8 for x86_64 to answer to all the
> various warnings you indicated. Some may be harmless, and some
> may eat your data. I would do a few tests with a virtual
> machine supporting bdver2 instructions before
Franco Martelli , on 2019-09-13:
> Hi, everybody
>
> in order to achieve Linux kernel optimized for my CPU AMD FX-8350
> Bulldozer2 I changed the line 121 of linux-source-4.19/arch/x86/Makefile
> from:
>
> cflags-$(CONFIG_MK8) += $(call cc-option,-march=k8)
>
> to:
>
> cflags-$(CONFIG_MK8) += $(cal
On Tue 16 Aug 2016 at 22:45:29 +0100, Lisi Reisz wrote:
[...Snip... The history is in previous mails].
> After a lot more wrong turnings and much agonising, thinking instead of
> panicking (at last!) and retrying:
>
> root@Eros:/home/lisi/Sane-Files# scanimage -L
> device `genesys:libusb:001:00
On Tuesday 16 August 2016 17:27:10 Brian wrote:
> On Tue 16 Aug 2016 at 15:39:00 +0100, Lisi Reisz wrote:
> > On Tuesday 16 August 2016 13:49:48 Brian wrote:
> > > Mea culpa. Please see the apt-get manual: build-dep (no "s").
> >
> > Thanks, both. :-)
> >
> > Everything now built, though there was
On Tuesday 16 August 2016 17:27:10 Brian wrote:
> Five .debs are built; only libsane, libsane-common and sane-utils need
> to be installed with 'dpkg -i'.
Ah! I don't know about senior moments. I need a rest, some sleep and a new
brain.
Lisi
On Tue 16 Aug 2016 at 15:39:00 +0100, Lisi Reisz wrote:
> On Tuesday 16 August 2016 13:49:48 Brian wrote:
> >
> > Mea culpa. Please see the apt-get manual: build-dep (no "s").
>
> Thanks, both. :-)
>
> Everything now built, though there was an error at the end:
>
> Now running lintian...
> warn
On Tuesday 16 August 2016 13:49:48 Brian wrote:
> On Tue 16 Aug 2016 at 12:57:50 +0100, Lisi Reisz wrote:
> > On Monday 15 August 2016 14:25:58 Brian wrote:
> > > A good guide to backporting is at
> > >
> > >
> > > https://raphaelhertzog.com/2010/12/15/howto-to-rebuild-debian-packages/
> > >
> >
On Tue 16 Aug 2016 at 12:57:50 +0100, Lisi Reisz wrote:
> On Monday 15 August 2016 14:25:58 Brian wrote:
> >
> > A good guide to backporting is at
> >
> > https://raphaelhertzog.com/2010/12/15/howto-to-rebuild-debian-packages/
> >
> > A deb-src line in sources.list for unstable is needed to do
>
Le 16/08/2016 à 13:57, Lisi Reisz a écrit :
> I have got stuck. Only slightly further on than I had already got stuck.
> (apt-get said it wasn't downloading what I had already downloaded!)
>
> root@Eros:/home/lisi/Sane-Files# apt-get build-deps libsane-common/testing
> E: Invalid operation bui
On Monday 15 August 2016 14:25:58 Brian wrote:
> On Mon 15 Aug 2016 at 14:23:36 +0200, didier gaumet wrote:
> > Le 15/08/2016 à 12:42, Lisi Reisz a écrit :
> > > Thanks, didier. That is nice to know.
> > >
> > > So it should be in the up-to-date tar ball, if I were to succeed in
> > > sorting that
On Mon 15 Aug 2016 at 19:05:55 +0100, Lisi Reisz wrote:
> On Monday 15 August 2016 14:25:58 Brian wrote:
> > A good guide to backporting is at
> >
> > https://raphaelhertzog.com/2010/12/15/howto-to-rebuild-debian-packages/
> >
> > A deb-src line in sources.list for unstable is needed to do
> >
>
On Monday 15 August 2016 14:25:58 Brian wrote:
> A good guide to backporting is at
>
> https://raphaelhertzog.com/2010/12/15/howto-to-rebuild-debian-packages/
>
> A deb-src line in sources.list for unstable is needed to do
>
> apt-get source libsane-common/unstable
>
> Then
>
> apt-get build-
On Mon 15 Aug 2016 at 15:47:00 +0200, didier gaumet wrote:
> Le 15/08/2016 à 15:25, Brian a écrit :
> [...]
> > I reckon the second approach will not work because the libraries need
> > an adjustment too.
>
> I plead guilty: Lisi just confirmed your point of view, In computer
> science, crime (of
Le 15/08/2016 à 15:25, Brian a écrit :
[...]
> I reckon the second approach will not work because the libraries need
> an adjustment too.
I plead guilty: Lisi just confirmed your point of view, In computer
science, crime (of lazyness) does not (always) pay ;-)
thanks for your input, Brian, I did
On Mon 15 Aug 2016 at 14:23:36 +0200, didier gaumet wrote:
> Le 15/08/2016 à 12:42, Lisi Reisz a écrit :
>
> > Thanks, didier. That is nice to know.
> >
> > So it should be in the up-to-date tar ball, if I were to succeed in sorting
> > that out. But are you suggesting that I would do better
On Monday 15 August 2016 13:23:36 didier gaumet wrote:
> Le 15/08/2016 à 12:42, Lisi Reisz a écrit :
> > Thanks, didier. That is nice to know.
> >
> > So it should be in the up-to-date tar ball, if I were to succeed in
> > sorting that out. But are you suggesting that I would do better to
> > bac
Le 15/08/2016 à 12:42, Lisi Reisz a écrit :
> Thanks, didier. That is nice to know.
>
> So it should be in the up-to-date tar ball, if I were to succeed in sorting
> that out. But are you suggesting that I would do better to backport from
> Stretch? I had decided that the tar ball would be s
On Monday 15 August 2016 08:52:15 didier gaumet wrote:
> Le 15/08/2016 à 00:13, Lisi Reisz a écrit :
> > Although Canon LiDE 220
>
> [...]
>
> > lisi@Eros:~$ lsusb | grep Canon
> > Bus 001 Device 003: ID 04a9:190f Canon, Inc.
> > lisi@Eros:~$ grep 190f /etc/sane.d/genesys.conf
> >
> > Having little
Le 15/08/2016 à 00:13, Lisi Reisz a écrit :
> Although Canon LiDE 220
[...]
> lisi@Eros:~$ lsusb | grep Canon
> Bus 001 Device 003: ID 04a9:190f Canon, Inc.
> lisi@Eros:~$ grep 190f /etc/sane.d/genesys.conf
>
> Having little faith, I cat-ed /etc/sane.d/genesys.conf, and the 220 driver
> was
> i
On 08/14/2016 06:13 PM, Lisi Reisz wrote:
Although Canon LiDE 220 is supposed to be covered completely, and although I
have had very good success with earlier models, I was having major problems
with this one, echoed by many on the internet. I tried all the usual tests,
culminating in:
lisi@Eros
On 2015-09-17 12:04 +0200, Florian Pelgrim wrote:
> I'm trying to static linking the coreutils. But for some reasons it
> fails with a cryptic bug for me.
>
> For building I'm using the vagrant box deb/jessie-amd64. So anyone who
> is interested can reproduce it.
>
> I have done the following step
Hi,
Florian Pelgrim writes:
> I would also be interested what this message means and if it can be
> ignored or anything should be done:
>> /home/vagrant/coreutils-8.23/src/whoami.c:85: warning: Using
>> 'getpwuid' in statically linked applications requires at runtime the
>> shared libraries from t
On Thu, 17 Sep 2015 06:04:03 -0400 (EDT), Florian Pelgrim wrote:
>
> I'm trying to static linking the coreutils. But for some reasons it
> fails with a cryptic bug for me.
>
> For building I'm using the vagrant box deb/jessie-amd64. So anyone who
> is interested can reproduce it.
>
> I have done
csanyi...@gmail.com writes:
> Gary Dale writes:
>
>> On 17/01/15 10:19 AM, csanyi...@gmail.com wrote:
>
>>> I have a headless powerpc box and run on it Debian Wheezy with kernel
>>> Linux b2 3.2.62-1 #1 Mon Aug 25 04:22:40 UTC 2014 ppc GNU/Linux .
>>>
>>> But this kernel doesn't have support for
Gary Dale writes:
> On 17/01/15 10:19 AM, csanyi...@gmail.com wrote:
>> I have a headless powerpc box and run on it Debian Wheezy with kernel
>> Linux b2 3.2.62-1 #1 Mon Aug 25 04:22:40 UTC 2014 ppc GNU/Linux .
>>
>> But this kernel doesn't have support for the rtl8192cu kernel-module.
>>
>> One
On 17/01/15 10:19 AM, csanyi...@gmail.com wrote:
Hi,
I have a headless powerpc box and run on it Debian Wheezy with kernel
Linux b2 3.2.62-1 #1 Mon Aug 25 04:22:40 UTC 2014 ppc GNU/Linux .
But this kernel doesn't have support for the rtl8192cu kernel-module.
One can to get the kernel source fr
The same problem, with kernel 3.10, was present
with Wheezy 486 on same computer.
Thanks
Regards
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/1383829602.35782
The same problem, with kernel 3.10, was present
with Wheezy 486 on same computer.
Thanks
Regards
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/1383828867.2
On Wed, 06 Nov 2013 15:07:58 -0500 (EST), Antispammbox-debian wrote:
>
> Hi all
>
> I try compiling kernel 3.10 on Squeeze 6.0.7. with cpu
> Intel Centrino1 32bit.
>
> Unpack source in /usr/src, and:
> adduser user src
> chown -R root:src /usr/src
> chmod -R g+w /usr/src
>
> cp /boot/config-`
On Sun, 11 Nov 2012 13:06:31 -0500 (EST), Martin Steigerwald wrote:
>
> I found I misread references to 2.6.8.
You raise an interesting point. Perhaps references to kernel-image vs.
linux-image have outlived their usefulness by now. I will consider
removing them in a future revision (and the re
On Sun, 11 Nov 2012 05:16:29 -0500 (EST), Ralf Mardorf wrote:
>
> I remember one issue that occurred very often,
> in /lib/modules/KERNEL_VERSION the /build and /source links were
> missing or bad.
> ...
> "build -> /usr/src/linux-3.6.5-rt14" but correct would be linked
> against "linux-headers-3.
On Tue, Nov 13, 2012 at 2:41 AM, Tom Furie wrote:
> On Tue, Nov 13, 2012 at 01:59:41AM -0500, Tom H wrote:
>
>> The documentation says
>>
>> - If you install the full sources, put the kernel tarball in a
>>directory where you have permissions (eg. your home directory)
>>
>> which basically me
On Tue, Nov 13, 2012 at 01:59:41AM -0500, Tom H wrote:
> The documentation says
>
> - If you install the full sources, put the kernel tarball in a
>directory where you have permissions (eg. your home directory)
>
> which basically means "don't use /usr/src" since a regular user
> doesn't ha
On Tue, Nov 13, 2012 at 1:22 AM, Tom Furie wrote:
> On Tue, Nov 13, 2012 at 12:10:55AM -0500, Tom H wrote:
>>
>> That RHEL/Fedora dont' use "/usr/src" might, on its own, not make it
>> good practice, but since they're following kernel documentation
>> perhaps it does!
>
> The kernel documentation
On Tuesday, November 13, 2012 01:22:50 AM Tom Furie wrote:
> On Tue, Nov 13, 2012 at 12:10:55AM -0500, Tom H wrote:
> > That RHEL/Fedora dont' use "/usr/src" might, on its own, not make it
> > good practice, but since they're following kernel documentation
> > perhaps it does!
>
> The kernel docum
On Tue, Nov 13, 2012 at 12:10:55AM -0500, Tom H wrote:
> That RHEL/Fedora dont' use "/usr/src" might, on its own, not make it
> good practice, but since they're following kernel documentation
> perhaps it does!
The kernel documentation does not say not to /usr/src, it says not to
use /usr/src/lin
On Sun, Nov 11, 2012 at 1:11 PM, Martin Steigerwald wrote:
> Am Sonntag, 11. November 2012 schrieb Tom H:
>>
>> I've also never seen any Debian documentation pointing to building a
>> kernel elsewhere than in "/usr/src/". It's been the RHEL/Fedora way
>> for years though.
>
> That doesn´t make it
On Sun, Nov 11, 2012 at 5:16 AM, Ralf Mardorf
wrote:
>
> I don't have time to read the current howto now, but I'll read it ASAP.
> It describes the way I build Debian and Ubuntu kernels since years, but
> while my scripts are a little bit outdated, Stephen updated his howto.
> However, even my out
On Sat, Nov 10, 2012 at 11:56:43AM +, Lisi Reisz wrote:
> I have been trying to get to grips with compiling a custom kernel. I have
> been shying away for too long.
>
> I am following Stephen's marvellous work, and had got this far:
>
> http://users.wowway.com/~zlinuxman/Kernel.htm#Unpack
>
On Sat, Nov 10, 2012 at 09:10:01PM +0100, Martin Steigerwald wrote:
> Well, if you apply common sense to what you read, old instructions can
> still be quite usable. The Linux Documentation Project (TLDP) is a good
> example for that.
If there was one common culture then "common sense" might act
Am Sonntag, 11. November 2012 schrieb Tom H:
> On Sat, Nov 10, 2012 at 2:15 PM, Lisi Reisz
wrote:
> > On Saturday 10 November 2012 18:46:09 Martin Steigerwald wrote:
> >> Am Samstag, 10. November 2012 schrieb Lisi Reisz:
> >>> I have been trying to get to grips with compiling a custom kernel.
> >
Am Samstag, 10. November 2012 schrieb Stephen Powell:
> On Sat, 10 Nov 2012 13:46:09 -0500 (EST), Martin Steigerwald wrote:
> > On Sat, 10 Nov 2012 Lisi Reisz wrote:
> >> I have been trying to get to grips with compiling a custom kernel.
> >> I have been shying away for too long.
> >>
> >> I am f
On Sat, 10 Nov 2012 17:45:20 -0500 (EST)
Stephen Powell wrote:
> On Sat, 10 Nov 2012 13:46:09 -0500 (EST), Martin Steigerwald wrote:
> > On Sat, 10 Nov 2012 Lisi Reisz wrote:
> >> I have been trying to get to grips with compiling a custom
> >> kernel. I have been shying away for too long.
> >>
>
On Sat, Nov 10, 2012 at 2:15 PM, Lisi Reisz wrote:
> On Saturday 10 November 2012 18:46:09 Martin Steigerwald wrote:
>> Am Samstag, 10. November 2012 schrieb Lisi Reisz:
>>>
>>> I have been trying to get to grips with compiling a custom kernel. I
>>> have been shying away for too long.
>>>
>>> I a
On Sat, 10 Nov 2012 13:46:09 -0500 (EST), Martin Steigerwald wrote:
> On Sat, 10 Nov 2012 Lisi Reisz wrote:
>> I have been trying to get to grips with compiling a custom kernel. I
>> have been shying away for too long.
>>
>> I am following Stephen's marvellous work, and had got this far:
>>
>> h
Am Samstag, 10. November 2012 schrieb Lisi Reisz:
> Thanks, Martin. Yes, I have looked at the website you refer to, and
> tried to use it. And I have the book to which you refer. The
> trouble is, that for the basic stuff they are simply above my
> head. Stephen gives more explanation and more
On Saturday 10 November 2012 18:46:09 Martin Steigerwald wrote:
> Hi Lisi,
>
> Am Samstag, 10. November 2012 schrieb Lisi Reisz:
> > I have been trying to get to grips with compiling a custom kernel. I
> > have been shying away for too long.
> >
> > I am following Stephen's marvellous work, and ha
Hi Lisi,
Am Samstag, 10. November 2012 schrieb Lisi Reisz:
> I have been trying to get to grips with compiling a custom kernel. I
> have been shying away for too long.
>
> I am following Stephen's marvellous work, and had got this far:
>
> http://users.wowway.com/~zlinuxman/Kernel.htm#Unpack
T
On Saturday 10 November 2012 15:36:27 Tom Furie wrote:
> On Sat, Nov 10, 2012 at 09:31:57AM -0500, Stephen Powell wrote:
> > Hi, Lisi. My guess is that this is a permissions issue. Is your id a
> > member of group src? (Issue the "groups" command and see if src is one
> > of the groups listed in
On Saturday 10 November 2012 13:34:59 Hugo Vanwoerkom wrote:
> Lisi Reisz wrote:
> > I have been trying to get to grips with compiling a custom kernel. I
> > have been shying away for too long.
> >
> > I am following Stephen's marvellous work, and had got this far:
> >
> > http://users.wowway.com/
Hi Stephen - and thanks!
On Saturday 10 November 2012 14:31:57 Stephen Powell wrote:
> My guess is that this is a permissions issue. Is your id a member
> of group src?
Yes!
[snip]
> (1) The directory /usr/src must be owned by user root and by group src.
It wasn't, and now is.
> (2) The gr
On Sat, Nov 10, 2012 at 09:31:57AM -0500, Stephen Powell wrote:
> Hi, Lisi. My guess is that this is a permissions issue. Is your id a member
> of group src? (Issue the "groups" command and see if src is one of the groups
> listed in the output of the command.) Here is a summary of the permiss
On Sat, 10 Nov 2012 06:35:21 -0500 (EST), Lisi Reisz wrote:
>
> I have been trying to get to grips with compiling a custom kernel. I have
> been shying away for too long.
>
> I am following Stephen's marvellous work, and had got this far:
>
> http://users.wowway.com/~zlinuxman/Kernel.htm#Unpac
Lisi Reisz wrote:
I have been trying to get to grips with compiling a custom kernel. I have
been shying away for too long.
I am following Stephen's marvellous work, and had got this far:
http://users.wowway.com/~zlinuxman/Kernel.htm#Unpack
But I get errors the end of which is below. I tried
On Sun, 28 Oct 2012 05:20:01 +0100
lee wrote:
> apt-get build-dep dvbcut
> apt-get source dvbcut
> cd dvbcut
> debuild -us -uc
>
>
> ... fails with a number of errors:
I hastily went through all the post with this subject and didn't notice anyone
suggesting:
apt-get install checkinstall
apt-
--- On Sat, 11/3/12, lee wrote:
> From: lee
> Subject: Re: compiling a Debian package
> To: debian-user@lists.debian.org
> Date: Saturday, November 3, 2012, 2:42 PM
> Go Linux
> writes:
>
> >> Just use either the drivers from their website or
> the Debian
&
Go Linux writes:
>> Just use either the drivers from their website or the Debian
>> version of
>> those. Won't that work?
>>
>>
>
> The Debian version of the driver wouldn't install. It advised me to
> use nouveau during the failed process. I had never used the sgfxi
> script before.
sgfxi s
--- On Fri, 11/2/12, lee wrote:
> From: lee
> Subject: Re: compiling a Debian package
> To: debian-user@lists.debian.org
> Date: Friday, November 2, 2012, 6:11 PM
> Go Linux
> writes:
>
> > po'd. Thankfully, I did manage to get the driver
> for the old
Jochen Spieker writes:
> lee:
>> Darac Marjal writes:
>>
>>> Nothing (that I'm aware of) in Debian bans you from using non-free
>>> software. There is only the understanding that support for non-free
>>> software is the responsibility of that software's provider.
>>
>> You already can't use it
Go Linux writes:
> po'd. Thankfully, I did manage to get the driver for the old nvidia
> card installed with the sgfxi script but had to blacklist nouveau to
> get it to work.
Just use either the drivers from their website or the Debian version of
those. Won't that work?
--
Debian testing i
Kelly Clowers writes:
> On Thu, Nov 1, 2012 at 10:09 AM, lee wrote:
>>
>>
>> Besides, I was told in an answer to a bug report that 32bit support will
>> not be available in the next release,
>
>
> Yeah, right. I'll believe that when I see a formal announcement of
> it on the front page of debian
Lisi Reisz writes:
> It is much the best solution to the problem you keep expounding.
It is not a solution at all.
> You clearly dislike Debian intensely, so it is daft to keep using it.
I don't dislike Debian, I only dislike that the developers broke it.
> Windows would give you everything y
--- On Thu, 11/1/12, lee wrote:
> From: lee
> Subject: Re: compiling a Debian package
> To: debian-user@lists.debian.org
> Date: Thursday, November 1, 2012, 12:35 PM
>
> Don't worry, I like free software a lot. I don't like
> dead ends,
> though.
>
lee:
> Darac Marjal writes:
>
>> Nothing (that I'm aware of) in Debian bans you from using non-free
>> software. There is only the understanding that support for non-free
>> software is the responsibility of that software's provider.
>
> You already can't use it anymore when it's 32bit software.
On Thu, Nov 1, 2012 at 10:09 AM, lee wrote:
>
>
> Besides, I was told in an answer to a bug report that 32bit support will
> not be available in the next release,
Yeah, right. I'll believe that when I see a formal announcement of
it on the front page of debian.org and on debian-announce. I expec
On Thursday 01 November 2012 17:16:24 lee wrote:
> Lisi Reisz writes:
> > On Wednesday 31 October 2012 15:25:52 Darac Marjal wrote:
> >> Anyway, I feel like I'm feeding a troll here, so I'll just point you to
> >> Debian's Social Contract[4] which describes this better than I can
> >
> > He likes
Darac Marjal writes:
> On Wed, Oct 31, 2012 at 03:39:04PM +0100, lee wrote:
> I'm not familiar with cinelerra but, according to the BTS([1] and [2]),
> there have been two^Wseveral attempts to package cinelerra that have
> fallen by the wayside. That latter bug seems to suggest that cinelerra
>
John Hasler writes:
> Lisi writes:
>> And it does rather sound as though he might be better off with
>> Windows. But at whom would he moan in that case?
>
> Microsoft, of course, with the advantage that there would be no danger
> that they would fix the problems that he moaned about.
Hilarious
Lisi Reisz writes:
> On Wednesday 31 October 2012 15:25:52 Darac Marjal wrote:
>> Anyway, I feel like I'm feeding a troll here, so I'll just point you to
>> Debian's Social Contract[4] which describes this better than I can
>
> He likes moaning. ;-) We are suggesting ways of solving his problem,
John Hasler writes:
> lee writes:
>> It is not illegal to use NVIDIA drivers, yet they are deprecated,
>> without alternative. It is probably not illegal to use firmware to
>> get hardware working that doesn't work without, yet firmware is
>> deprecated, without alternative.
>
>> The obsession w
On Wed, Oct 31, 2012 at 03:04:49PM +0100, lee wrote:
> Yeah and that's why you are forced to turn your system into a mess with
> brokenarch and are supposed to try packages from unstable which create
> only more dependency problems and mess things up even further.
>
> Think it through and you'll s
On Wed, Oct 31, 2012 at 10:04 AM, lee wrote:
> Andrei POPESCU writes:
>> On Mi, 31 oct 12, 04:13:59, lee wrote:
>>>
>>> Just try it and you'll see. Or you figure out how to do it and let me
>>> know. Like I said, it worked, then there was an update and it doesn't
>>> work anymore, probably beca
Lisi writes:
> And it does rather sound as though he might be better off with
> Windows. But at whom would he moan in that case?
Microsoft, of course, with the advantage that there would be no danger
that they would fix the problems that he moaned about.
--
John Hasler
--
To UNSUBSCRIBE, emai
On Wednesday 31 October 2012 15:25:52 Darac Marjal wrote:
> Anyway, I feel like I'm feeding a troll here, so I'll just point you to
> Debian's Social Contract[4] which describes this better than I can
He likes moaning. ;-) We are suggesting ways of solving his problem, but it
is more fun to slag
lee writes:
> It is not illegal to use NVIDIA drivers, yet they are deprecated,
> without alternative. It is probably not illegal to use firmware to
> get hardware working that doesn't work without, yet firmware is
> deprecated, without alternative.
> The obsession with free software unfortunatel
On Wed, Oct 31, 2012 at 03:39:04PM +0100, lee wrote:
> Darac Marjal writes:
>
> > libdvdcss2 brute forces the decryption on the disk and, so, might be
> > considered circumvention under the DMCA. This IS allowed in some cases
> > and in various other jurisdictions, but it's not really a sensible
On Wednesday 31 October 2012 14:22:31 lee wrote:
> Lisi Reisz writes:
> > You seem to be very unhappy with Debian. Why _are_ you still using
> > it?
>
> It's because I haven't found an alternative yet, and it's very time
> consuming to switch.
>
> > You could save your data and install something
Darac Marjal writes:
> libdvdcss2 brute forces the decryption on the disk and, so, might be
> considered circumvention under the DMCA. This IS allowed in some cases
> and in various other jurisdictions, but it's not really a sensible move
> for Debian to freely distribute such a package.
I'm awa
Lisi Reisz writes:
> You seem to be very unhappy with Debian. Why _are_ you still using
> it?
It's because I haven't found an alternative yet, and it's very time
consuming to switch.
> You could save your data and install something else.
Yes, but what?
> And granted that you would have to se
Jochen Spieker writes:
> lee:
>> Andrei POPESCU writes:
>>
>>> Firstly, you could have specified that instead of broad statements like
>>> "32 bit support has been removed from Debian". Debian is much more than
>>> the amd64 architecture.
>>
>> That is what 32bit support is about.
>
> No. Fi
Andrei POPESCU writes:
> On Mi, 31 oct 12, 04:13:59, lee wrote:
>>
>> Just try it and you'll see. Or you figure out how to do it and let me
>> know. Like I said, it worked, then there was an update and it doesn't
>> work anymore, probably because they modified the NVIDIA drivers, though
>> nob
Darac Marjal writes:
> libdvdcss2 brute forces the decryption on the disk and, so, might be
> considered circumvention under the DMCA. This IS allowed in some
> cases...
It is legal to use it to access a DVD you own in the USA as long as you
make no infringing copies. The problem is that the CCA
On Mi, 31 oct 12, 04:13:59, lee wrote:
>
> Just try it and you'll see. Or you figure out how to do it and let me
> know. Like I said, it worked, then there was an update and it doesn't
> work anymore, probably because they modified the NVIDIA drivers, though
> nobody knows. I've sent a bug repo
On Wed, Oct 31, 2012 at 04:23:42AM +0100, lee wrote:
> Chris Bannister writes:
>
> > On Tue, Oct 30, 2012 at 09:06:37PM +0100, lee wrote:
> >> Tom H writes:
> >>
> >> > Andrei called d-m.o deprecated because, AFAIK, most of the packages in
> >> > d-m.o are now available in d.o.
> >>
> >> Cinel
lee:
> Andrei POPESCU writes:
>
>> Firstly, you could have specified that instead of broad statements like
>> "32 bit support has been removed from Debian". Debian is much more than
>> the amd64 architecture.
>
> That is what 32bit support is about.
No. First and foremost, 32 Bit support is a
On Wednesday 31 October 2012 03:23:42 lee wrote:
> Chris Bannister writes:
> > On Tue, Oct 30, 2012 at 09:06:37PM +0100, lee wrote:
> >> Tom H writes:
> >> > Andrei called d-m.o deprecated because, AFAIK, most of the packages in
> >> > d-m.o are now available in d.o.
> >>
> >> Cinelerra is not in
1 - 100 of 1150 matches
Mail list logo
