Yes I did both as root, never worked with cp will try with cat. Thanks.
Will report soon
▼ Hide quoted text On Aug 11, 2013 11:19 AM, "Marian Corcodel" <
corcodel.mar...@gmail.com> wrote: cat debian-7.1.0-amd64-DVD-1.iso >
/dev/sdc is right and sync on root.
On Aug 11, 2013 11:19 AM, "Marian Corco
Thanks Ivan for the reply, I feel the only modification would be the grub
as I will have to install it over the whole hard disk as I have a dual boot
of windows.
Can you tell me more about my /home partition (Point # 2)
I will try your method and will report.
But I want to know, even after downlo
Hey Anubhav,
Not sure if you will like the way I would install in you situation (in case
of lack of internet connection).
Since you're debian user I'm proposing to install in the following way:
https://wiki.debian.org/Debootstrap.
You need to get ready debian-based system, configure /etc files,
On Sun, Jul 21, 2013 at 09:06:31PM +0200, Bernd Zeimetz wrote:
> On 06/22/2013 07:26 PM, Martin Zobel-Helas wrote:
> > * sparc: no working nflog (mild concern); no stable kernels in stable
> > (compiling clisp for instance crashes the kernel reliably on smetana). We
> > need to run sparc with olds
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/22/2013 07:26 PM, Martin Zobel-Helas wrote:
> * sparc: no working nflog (mild concern); no stable kernels in stable
> (compiling clisp for instance crashes the kernel reliably on smetana). We
> need to run sparc with oldstable kernels to provi
On Thu, Jun 06, 2013 at 12:47:07PM -0400, Robert Goley wrote:
> That sounds like a good idea but you would need to blacklist the PIDs of
> the commands called from your backup script as well. Most likely, they are
> the processes opening all of the files to start with. You might want to
> look at
RedHat are focusing their product on suiting the needs and
idiosyncrasies of companies that 'think' in the 'old iron' mentality.
RedHat have moved from being disruptive in the small end of town (start
ups, small ISP's etc) to chasing large fortune 500 companies. They have
unashamedly shaped th
On Wed, Jun 26, 2013 at 06:11:31PM +0200, Francesco Pietra wrote:
> Hi Lennart:
> I forgot that what is found on supercomputers might result also from what
> you say.
>
> I found it problematic to compile a code for molecular dynamics (MD)
> inclusive of an elaborate plugin. Better, I succeeded wh
Hi Lennart:
I forgot that what is found on supercomputers might result also from what
you say.
I found it problematic to compile a code for molecular dynamics (MD)
inclusive of an elaborate plugin. Better, I succeeded when only the
simplest part of the plugin was implemented, getting a valid MD ex
On 06/26/2013 10:40 AM, Lennart Sorensen wrote:
On Wed, Jun 26, 2013 at 04:33:20PM +0200, Francesco Pietra wrote:
Hello:
I noticed that in my country supercomputer center all machines, both CPU
(FERMI) and GPU (AURORA, PLX) run on RedHat Linux. As a long time user of
Debian GNU Linux amd64, I am
On Wed, Jun 26, 2013 at 04:33:20PM +0200, Francesco Pietra wrote:
> Hello:
> I noticed that in my country supercomputer center all machines, both CPU
> (FERMI) and GPU (AURORA, PLX) run on RedHat Linux. As a long time user of
> Debian GNU Linux amd64, I am curious whether such machines elsewhere al
Martin Zobel-Helas writes:
> [please consider replacing debian-ports@ldo with the appropriate port
> specific list when replying.]
>
> Comrades!
>
> At our recent Essen sprint, DSA went through the release qualification
> matrix (for wheezy, as there isn't one for jessie, yet) and defined a
> set
* Martin Zobel-Helas (zo...@debian.org) wrote:
> [please consider replacing debian-ports@ldo with the appropriate port
> specific list when replying.]
>
> * armel: no remote management (being worked on); no archive kernel for
> the machines we use.
>
> * armhf: no remote management (being work
On Tue, Jun 18, 2013 at 8:02 PM, John David Anglin wrote:
> Hi Aurelien,
>
>
> On 18-Jun-13, at 6:05 PM, Aurelien Jarno wrote:
>
>> This is true that they have recently contacted me through another email
>> address, but I haven't found time to work on that. Just stay tuned.
>
>
> That's great news
On 14-06-13 21:11, Thorsten Glaser wrote:
> Wouter, Mikael: input on switching C/C++ to 4.8?
We don't have much data either way, do we?
I suppose it shouldn't be too much of a problem, but I can't be sure. In
the past we've usually taken the plunge, and filed bugs if things go
really bad.
--
Th
Hi Aurelien,
On 18-Jun-13, at 6:05 PM, Aurelien Jarno wrote:
This is true that they have recently contacted me through another
email
address, but I haven't found time to work on that. Just stay tuned.
That's great news.
Helge and I have been working away as best we can to maintain the
po
hitectures (the latter confirmed by the Debian ARM porters). I did not
> >> get
> >> any feedback from other port maintainers, so unless this does change and
> >> port
> >> maintainers get involved with toolchain maintenance, the architectures
> >> s
On Sat, Jun 15, 2013 at 02:08:12AM -0700, DutchGlory wrote:
> I have printer driver here for "Epson AcuLaser C1100" if someone is able to
> convert this to x64... (amd64)
> i'll (and many others) be *MORE* than happy :)
It has no source code, only binaries, and the binary is 32bit only.
Now yo
Am 15.06.2013 03:22, schrieb Stephan Schreiber:
> GCC-4.8 should become the default on ia64 soon; some other changes are
> desirable:
> - The transition of gcc-4.8/libgcc1 to libunwind8.
> - A removal of the libunwind7 dependency of around 4600 packages on ia64 -
> when
> they are updated next ti
GCC-4.8 should become the default on ia64 soon; some other changes are
desirable:
- The transition of gcc-4.8/libgcc1 to libunwind8.
- A removal of the libunwind7 dependency of around 4600 packages on
ia64 - when they are updated next time after the transition. The
libc6.1 should (likely) de
Matthias Klose dixit:
>> I’d like to have gcj at 4.6 in gcc-defaults for m68k please,
>> until the 4.8 one stops FTBFSing.
>
>please send a patch.
For gcc-defaults? I think that one is trivial…
For gcj? I did not take Compiler Design in what two semesters
of Uni I managed until I ran out of mone
> any feedback from other port maintainers, so unless this does change and port
>> maintainers get involved with toolchain maintenance, the architectures
>> staying
>> at 4.6 or 4.7 shouldn't be considered for a successful release
>> (re-)qualification.
>
> I tru
Am 13.06.2013 21:47, schrieb Thorsten Glaser:
> Matthias Klose dixit:
>
>> The Java and D frontends now default to 4.8 on all architectures, the Go
>> frontend stays at 4.7 until 4.8 get the complete Go 1.1 support.
>
> I’d like to have gcj at 4.6 in gcc-defaults for m68k please,
> until the 4.8
Steven Chamberlain dixit:
>Before that can be changed, I think the gcc-defaults package expects
>package version (>= 4.8.1-2) whereas m68k still has only the 4.8.0-7 you
>uploaded.
Right. That’s because gcj FTBFSes.
>You will also first need newer binutils (>= 2.23.52) which is still in
>the bui
Hi,
On 13/06/13 20:47, Thorsten Glaser wrote:
> From me nothing against switching C/C++ to 4.8 for m68k at
> this point, but I’d like to hear at least Wouter’s opinion
> on that, and possibly Mikael [...]
Before that can be changed, I think the gcc-defaults package expects
package version (>= 4.8
Matthias Klose dixit:
>The Java and D frontends now default to 4.8 on all architectures, the Go
>frontend stays at 4.7 until 4.8 get the complete Go 1.1 support.
I’d like to have gcj at 4.6 in gcc-defaults for m68k please,
until the 4.8 one stops FTBFSing.
From me nothing against switching C/C++
not
> > get
> > any feedback from other port maintainers, so unless this does change and
> > port
> > maintainers get involved with toolchain maintenance, the architectures
> > staying
> > at 4.6 or 4.7 shouldn't be considered for a successful release
> &g
ntainers get involved with toolchain maintenance, the architectures staying
> at 4.6 or 4.7 shouldn't be considered for a successful release
> (re-)qualification.
I trust these are the architectures that are okay so far:
| gcc48_archs = amd64 armel armhf arm64 i386 x32 kfreebsd-amd64
kfre
y feedback from other port maintainers, so unless this does change and port
maintainers get involved with toolchain maintenance, the architectures staying
at 4.6 or 4.7 shouldn't be considered for a successful release
(re-)qualification.
The Java and D frontends now default to 4.8 on all arch
On Thu, 6 Jun 2013, Robert Goley wrote:
That sounds like a good idea but you would need to blacklist the PIDs of the
commands called from your backup script as well. Most likely, they are the
processes opening all of the files to start with. You might want to look at
using a python script for
Wasn't sure it had been thought out. Thought you were doing a single
backup script expecting blacklisting the single PID to work. The method
you have should work great.
On Thu, Jun 6, 2013 at 12:55 PM, Giacomo Mulas
wrote:
> On Thu, 6 Jun 2013, Robert Goley wrote:
>
> That sounds like a good
That sounds like a good idea but you would need to blacklist the PIDs of
the commands called from your backup script as well. Most likely, they are
the processes opening all of the files to start with. You might want to
look at using a python script for your backup script so you can more easily
c
Francesco Pietra wrote:
> Alexandru Cardaniuc wrote:
> > > Did I miss something during the debian installation? Why wasn't grub
> > > automatically installed on both disks?
> >
> > Seems like it should have been. I would file a bug against the
> > debian-installer or installation-reports.
>
> I st
On Tue, Jun 04, 2013 at 12:26:44PM +0200, Francesco Pietra wrote:
> Hello:
> I started this thread not because grub on both disks should be by default
> but because I found difficulties in recovering. If I performed badly, and
> there is no problem in installing grub on the working disk, then I see
Hello:
I started this thread not because grub on both disks should be by default
but because I found difficulties in recovering. If I performed badly, and
there is no problem in installing grub on the working disk, then I see no
problem. There are many raids, not limited to raid1. Perhaps it is bec
On Mon, Jun 03, 2013 at 02:32:39PM -0500, Karl Schmidt wrote:
> This is serious - I sure hope you wrote up a bug report?
I first wanted to make sure that the serious error isn't on my side.
Up to now I seem to be the only one affected...
S
--
To UNSUBSCRIBE, email to debian-amd64-requ...@lists
Alexandru Cardaniuc wrote:
> I just did 2 reinstalls in the last two weeks (upgrade from sqeeze to
> wheezy screwed up my grub config and then my 6 year old drives started
> failing - so much fun :), but basically during both reinstalls and
> creating MD devices with debian installer (md0/md1/md2)
This is serious - I sure hope you wrote up a bug report?
Karl Schmidt EMail k...@xtronics.com
Transtronics, Inc. WEB
http://secure.transtronics.com
3209
Bob Proulx writes:
>> Nonetheless, I'll try to digest your "manual". At this point, could
>> you also describe how to safely proceed, on this situation, to have
>> grub on both disks? It would be useful community wide, to complete
>> the raid1 installation from the Debian installer.
>
> As was al
--
> From: Francesco Pietra
> Date: Sat, Mar 2, 2013 at 10:11 AM
> Subject: Re: RAID1 all bootable
> To: Lennart Sorensen , amd64 Debian
> , debian-users
>
>
> Is this recipe devised for installing grub on both sda and sda with an
> undamag
On Thu, May 23, 2013 at 6:40 PM, peter green wrote:
>>
>> :-) I'm one who asked there some time back why java7 is no longer in
>> the archives (unstable/experimental), while the last binaries I had
>> installed still work OK on my mini-pc...
>>
>> I'm just curious, sorry for asking to the lists..
> "Émeric" == Émeric Maschino writes:
Émeric> Just to let you know that I've successfully installed Wheezy
Émeric> using the netinst CD on a spare HDD, using default parameters
Émeric> (using entire HDD and one single partition as partition
Émeric> scheme) except for localization of course.
:-) I'm one who asked there some time back why java7 is no longer in
the archives (unstable/experimental), while the last binaries I had
installed still work OK on my mini-pc...
I'm just curious, sorry for asking to the lists... I want to
understand if the mini-pc is still a low performance de
Hi,
Sorry for the late reply, I didn't have access to my zx6000 workstation
until now.
Just to let you know that I've successfully installed Wheezy using the
netinst CD on a spare HDD, using default parameters (using entire HDD and
one single partition as partition scheme) except for localization
On Mon, May 6, 2013 at 8:22 AM, Matthias Klose wrote:
> It's time to change the Java default to java7, and to drop java support on
> architectures with non-working java7.
Just asking as a loongson-2f user, :-)
What makes java7 not to work on those architectures? Building issues?
> ...
> So the
On Mon, May 13, 2013 at 10:02:00AM -0400, Harry Prevor wrote:
> Thanks again for all your help guys. I was having a lot of problems,
> but I somehow managed to start the computer for just long enough to
> quickly install memtest86+ before it crashed with a kernel panic. On
> memtest, every single t
Hey Matthias
On 06/05/13 15:22, Matthias Klose wrote:
It's time to change the Java default to java7, and to drop java support on
architectures with non-working java7.
+1
Patches for the transition to Java7 should be available in the BTS, mostly
submitted by James Page. Some may be still lur
Thanks again for all your help guys. I was having a lot of problems,
but I somehow managed to start the computer for just long enough to
quickly install memtest86+ before it crashed with a kernel panic. On
memtest, every single test was failing, so I decided to try taking out
my two 8GB RAM sticks
10.05.2013 21:23, Harry Prevor пишет:
> On 5/10/13, "Артём Н." wrote:
>> 10.05.2013 05:04, Harry Prevor пишет:
>>> The normal images didn't work
>>> for some reason now forgotten, so I had to use the unofficial
>>> installation images that included nonfree drivers.
>> What are the drivers?
> I've
On Fri, May 10, 2013 at 01:23:09PM -0400, Harry Prevor wrote:
> Thanks a lot for your helpful responses guys. I'm at a public computer
> right now and haven't had a chance to try your ideas yet, but I've
> noticed a few things that I'd like to clarify:
>
> On 5/9/13, Chris Swenson wrote:
> > Give
Thanks a lot for your helpful responses guys. I'm at a public computer
right now and haven't had a chance to try your ideas yet, but I've
noticed a few things that I'd like to clarify:
On 5/9/13, Chris Swenson wrote:
> Given that these problems were occurring before, I'm guessing you have bad
> h
(in case they've
failed badly), then try fscking the filesystems. Then try something like
"debsums -c" to search for changed files. With luck, you may just need
to re-install the kernel.
signature.asc
Description: Digital signature
> copy /var/log/messages, /var/log/syslog
> (and send to list, of course)?
Also /etc/fstab plus result of sfdisk -lxuM /dev/sd command (or pvs --all && lvs
--all, if you use LVM)...
--
To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contac
10.05.2013 05:04, Harry Prevor пишет:
> The normal images didn't work
> for some reason now forgotten, so I had to use the unofficial
> installation images that included nonfree drivers.
What are the drivers?
> please mute the audio
Interesting music... :-)
> Any ideas as to how to debug this? I
Using synaptic, you can see the various categories of the packages,
including Installed (local), which means synaptic is not aware of where you
got it. Further, if it's in a backport, then it will show without a debian
logo to the left, and those should be downgraded or uninstalled, too.
– Chris
Yes I have the debian packages for nvidia...
On Wed, May 8, 2013 at 8:57 AM, Lennart Sorensen <
lsore...@csclub.uwaterloo.ca> wrote:
> On Wed, May 08, 2013 at 03:18:09AM -0500, Jaime Ochoa Malagón wrote:
> > After my upgrade to wheezy my X has failed.
> >
> > I tried to find the problem to fix i
No I didn't uninstall them and I don't know how to list them...
Do you know how?
I have iceweasel and multimedia files...
On Wed, May 8, 2013 at 7:06 AM, Chris Swenson wrote:
> The instructions for upgrade note that removing third-party software
> (including software from Debian testing or s
On Wed, May 08, 2013 at 03:18:09AM -0500, Jaime Ochoa Malagón wrote:
> After my upgrade to wheezy my X has failed.
>
> I tried to find the problem to fix it, and I was not be able to do it...
>
> I have a partial success narrowing the problem...
>
> And I ask you for help to find it clearly I do
The instructions for upgrade note that removing third-party software
(including software from Debian testing or sid) should be uninstalled,
which would include the proprietary nvidia driver. I know I've installed
some unofficial backport packages that may cause this problem, and I plan
on taking an
Matthias Klose dixit:
>Currently java bindings/packages are built for all architectures, however some
>architectures still use gcj as the (only available) Java implementation, and
>some OpenJDK zero ports are non-functional at this point, and Debian porters
>usually don't care about that. So the
Matthias Klose, le Mon 06 May 2013 16:22:30 +0200, a écrit :
> - hurd never had openjdk support, and afaik, nobody is working on that.
There has been work towards this, notably by Jeremie Koenig. I don't
know the status, we just have not made it a strong priority so far.
Samuel
--
To UNSUBSCRI
> 'm-a a-i'
sorry, should be: m-a a-i nvidia
--
To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130429154448.7c88e...@mirrors.kernel.org
Karl,
I can see nvidia-kernel-source in my debian unstable package list, though i
have no 'src' line in sources.list. Probably because that package can not have
a binary counterpart unless you used it :)
When i used this package (along nvidia-glx and module-assistant) in the past,
i just issu
On Sat, Apr 27, 2013 at 10:23:49PM +0200, Michael wrote:
> Recently, accidently inserted an Itanium64 installer in an amd64 PC and there
> wasn't any feedback message at all ... just the DVD did not start.
>
> I wonder if it's just grub being architecture specific ?
>
> Nailing down the CPU is
Recently, accidently inserted an Itanium64 installer in an amd64 PC and there
wasn't any feedback message at all ... just the DVD did not start.
I wonder if it's just grub being architecture specific ?
Nailing down the CPU is a tricky thing. Even if you install and use the 'cpuid'
tool, you st
Nvidia's refusal to be Linux friendly is well known and they leave messes behind - but back to my
original question: does anyone use nouveau on later nvidia cards ? How well does it work? ( I've
read that it supports dual heading ) ..
I saw a few more kernel bugs for nouveau listed while I wa
On Fri, Apr 26, 2013 at 04:08:58PM +0200, Giacomo Mulas wrote:
> On Wed, 24 Apr 2013, Hans-J. Ullrich wrote:
>
> >Don't use the nvidia package from debian for googleearth. They do not work,
> >as
> >the 32-bit-libs of nvidia have dependency problems. Obviously no one cared
> >for
> >this at the
On Wed, 24 Apr 2013, Hans-J. Ullrich wrote:
Don't use the nvidia package from debian for googleearth. They do not work, as
the 32-bit-libs of nvidia have dependency problems. Obviously no one cared for
this at the moment.
Just download the installer from the nvidia website and execute it - work
On 04/24/2013 12:00 AM, Hans-J. Ullrich wrote:
Don't use the nvidia package from debian for googleearth. They do not work, as
the 32-bit-libs of nvidia have dependency problems. Obviously no one cared for
this at the moment.
Just download the installer from the nvidia website and execute it - wo
Don't use the nvidia package from debian for googleearth. They do not work, as
the 32-bit-libs of nvidia have dependency problems. Obviously no one cared for
this at the moment.
Just download the installer from the nvidia website and execute it - works
like a charm!
Good luck!
Hans
--
To
On Tue, Apr 23, 2013 at 11:29:03AM +0300, Vasileios Karaklioumis wrote:
>I would update the bios and run memtest86.M/B model?
Personally, I'd look at more of the error message before even starting
that.
>
>On Apr 23, 2013 11:27 AM, "Goswin von Brederlow" <[1]goswin-...@web.de>
>wrote
I would update the bios and run memtest86.M/B model?
On Apr 23, 2013 11:27 AM, "Goswin von Brederlow" wrote:
> On Mon, Apr 22, 2013 at 06:51:18AM -0500, Chris Swenson wrote:
> > It's possible you have a CPU that has 2 cores, but is still not 64-bit
> > compatible. I have a Dell laptop with Intel
On Mon, Apr 22, 2013 at 06:51:18AM -0500, Chris Swenson wrote:
> It's possible you have a CPU that has 2 cores, but is still not 64-bit
> compatible. I have a Dell laptop with Intel Core Duo that would seem to be
> 64-bit capable, but upon further inspection is not. Check your CPU hardware
> manufa
On Mon, Apr 22, 2013 at 03:05:51PM +1000, Dean Hamstead wrote:
> For a network install, whilst you boot from some form of attached media
> (cd/dvd/usb) all the actual .deb files are retrieved via
> http/ftp/whatever then copied to disk
>
>
>
> Dean
> On 22/04/13 14:57, wrote:
> > Debia
On Monday 22 April 2013, you wrote:
> This computer is the only one computer that I have..
You only need one.
> now, I am using WinXP x86
> and I check the System Information and look at the system summary
>
> *x86 Family 6 Model 37 stepping 2GenuinedIntel ~2945Mhz*
>
>
> so the machi
> I can install x86 debian on 2006's latptop, and I cannot install x64
> debian on 2010 computer (RAM is 4G)
> I was installed Debian x64 with 1 CD
You should try the amd64 CD which is for x86-64 port.
x64 is a different port.
--
Jean-Christophe
--
To UNSUBSCRIBE, email to debian-amd64-requ.
in the 32bit version, cat /proc/cpuinfo and paste it here.
2006 should be new enough and generally the boot disk will tell you
quite clearly that 64bit isnt supported, the full error would be helpful
if you can paste it.
the crash could be acpi related. try noacpi as a kernel option
Dean
On 22/
On Monday 22 April 2013, wrote:
> I can install x86 debian on 2006's latptop, and I cannot install x64
> debian on 2010 computer (RAM is 4G)
> I was installed Debian x64 with 1 CD
>
> when the booting procedure runs on
>
> [4.779430] [] ? system_call_fastpath+0x16/0x1b
>
>
>
>
It's possible you have a CPU that has 2 cores, but is still not 64-bit
compatible. I have a Dell laptop with Intel Core Duo that would seem to be
64-bit capable, but upon further inspection is not. Check your CPU hardware
manufacturer for the specs to see if it can handle 64-bit instructions.
– C
For a network install, whilst you boot from some form of attached media
(cd/dvd/usb) all the actual .deb files are retrieved via
http/ftp/whatever then copied to disk
Dean
On 22/04/13 14:57, wrote:
> Debian has several ways to install, but I don't understand about
> "Network Install"
>
On Sun, Apr 14, 2013 at 11:34 PM, Bob Proulx wrote:
> Francesco Pietra wrote:
> > Is any official (= working) advice on getting java at work with wheezy
> > (specifically in amd64, if relevant)?
>
> http://wiki.debian.org/Java
>
> > What should be installed/reconfigured/uninstalled other than t
Francesco Pietra wrote:
> Is any official (= working) advice on getting java at work with wheezy
> (specifically in amd64, if relevant)?
http://wiki.debian.org/Java
> What should be installed/reconfigured/uninstalled other than the packages
> obtained from wheezy desktop install, followed by up
On Sunday 14 Apr 2013, Zenaan Harkness wrote:
> My test (and Java app I want to run) is sweethome3d.
> Wasn't working on wheezy.
> Upgraded to sid. Sweethome3d worked.
> Upgraded some days back, now it doesn't work.
> Not sure if I'm doing anything wrong. 64-bit.
> Haven't tested in a browser.
> Ze
My test (and Java app I want to run) is sweethome3d.
Wasn't working on wheezy.
Upgraded to sid. Sweethome3d worked.
Upgraded some days back, now it doesn't work.
Not sure if I'm doing anything wrong. 64-bit.
Haven't tested in a browser.
Zenaan
--
To UNSUBSCRIBE, email to debian-amd64-requ...@lis
Hello everybody,
As googleearth-package maintainer, I'd like to give more details on this
situation/it's current condition, as well give you some news regarding its
development.
I'm aware of the multiarch problem for some time now, and have made and
finished the new version of package which deals
Now my packages are somewhat in a mess, and please allow me to ask this a
little off-topic (but not completely):
(1) how can i apply a 'purge' to all packages that are 'c' half-configured ?
There are hundreds it seems.
(2) how can i search for _installed_ i386 packages explicitly (and maybe
al
On a close look, it appeared that somewhere in my installation experiments,
lsb-core (amd64) was deinstalled completely. I fixed that, but the result is
nearly exactly the same, with one exception. If i start this, it say that now:
/usr/lib/googleearth/googleearth-bin: error while loading share
Goswin,
I tried your other suggestion (DEB_BUILD_ARCH=i386 make-googleearth-package)
and created the i386 debian package. Es expected it installed only
unconfigured, with
/tmp r: dpkg --configure googleearth
dpkg: dependency problems prevent configuration of googleearth:
googleearth depends o
Many thanks for your suggestions !
Klaus,
I d/l the latest i386 package ('current') then after the package is loaded into
the database (by dpkg -i) it still can not be configured, as expected, because:
/tmp r: dpkg --configure google-earth-stable
dpkg: dependency problems prevent configuratio
On Thu, Mar 14, 2013 at 10:32:16PM +0100, Michael wrote:
> I guess you meant i should download the i386 deb directly from google ?
>
I didn't mean that but rather fixing the google earth package in
debian to behave like your installing on i386 even if you are on
amd64. The dependencies i
Le jeudi 14 mars 2013 22:32:16, Michael a écrit :
> This seems to end up in dependency hell too :)
>
> google-earth requires lsb-core:i386 which does not recognize the already
> installed alien v 8.88 (which is arch:all), but still insists on alien >=
> 8.36 (but no arch specified).
>
> (I wond
; This is with debian testing / unstable.
>
> Any suggestions ?
1. Re-compile the application yourself, as a proper 64-bit application.
2. If they won't let you have the Source Code (which should be enough, in
and of itself, to raise a huge red flag in your mind; just what are
This seems to end up in dependency hell too :)
google-earth requires lsb-core:i386 which does not recognize the already
installed alien v 8.88 (which is arch:all), but still insists on alien >= 8.36
(but no arch specified).
(I wonder what prevents lsb-core from being arch:all.)
There seems to
Ah ! I was too focused on apt.
I guess you meant i should download the i386 deb directly from google ?
ok i'll do that now.
--
To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debi
Goswin,
> If your package is depending on ia32-libs then you are not using the
> right package for multiarch. Only the amd64 package would depend on
> ia32-libs. Use the i386 package instead.
The i386 package of what ?
I've got an amd64. My sources suck testing and unstable and i have multiarch
On Thu, 14 Mar 2013, Francesco Pietra wrote:
As to the problem of linking lapack, I wonder whether this is because
it deal of a C-language code, requiring a fine-tuned calling. Is any C
interface to lapack in Debian?
Ciao Francesco.
There are several implementation of lapack in debian. You sho
Hello João Luis:
Sorry for my lack of care in setting the addresses.
What I did was: install liblapack3gf-dev to complete the
installations, according to previous suggestions. Now, my guess for
the link is
LIBS="-L/usr/lib -llapack -L/usr/lib -lstdc++"
According to the README, a link to both
On Thu, Mar 14, 2013 at 12:00:43PM +0100, Francesco Pietra wrote:
> Hello
> May I ask how to correctly link lapack and C standard libraries with
> Debian amd64 wheezy?
>
> Packages installed: liblapack3gf liblapack3 libblas3 libc6 libc6-dev
> **
Try installing the "-dev" packages for
On 13/03/13 08:02, Jerome BENOIT wrote:
Hi Francesco,
your issue may not be a CUDA issue, but rather a NAMD.
CUDA debian packages are fine.
You may look in this directory, in particular for installing NAMD success story
on Debian
and for some deb ball written by some folks.
In general the ma
Hi Francesco,
your issue may not be a CUDA issue, but rather a NAMD.
CUDA debian packages are fine.
You may look in this directory, in particular for installing NAMD success story
on Debian
and for some deb ball written by some folks.
In general the main issue with these kinds of source is that
701 - 800 of 20693 matches
Mail list logo
