On Sun, Feb 27, 2022 at 3:14 PM Grzesiek wrote:
> Hi there,
>
> I need to apply the following
>
> https://lore.kernel.org/linux-rdma/1645106372-23004-1-git-send-email-mike.marcinis...@cornelisnetworks.com/T/#u
> and rebuild ib_qib. To rebuild I wrote the following script
> .
On 2/27/22 23:13, Grzesiek wrote:
> Hi there,
>
> I need to apply the following
> https://lore.kernel.org/linux-rdma/1645106372-23004-1-git-send-email-mike.marcinis...@cornelisnetworks.com/T/#u
>
> and rebuild ib_qib. To rebuild I wrote the following script
> ($1 is th
On 2/27/22 22:21, Sven Hartge wrote:
Grzesiek wrote:
I need to apply the following
https://lore.kernel.org/linux-rdma/1645106372-23004-1-git-send-email-mike.marcinis...@cornelisnetworks.com/T/#u
and rebuild ib_qib.
The easiest way to ensure consistency would be to just rebuild the
kernel
Grzesiek wrote:
> I need to apply the following
> https://lore.kernel.org/linux-rdma/1645106372-23004-1-git-send-email-mike.marcinis...@cornelisnetworks.com/T/#u
> and rebuild ib_qib.
The easiest way to ensure consistency would be to just rebuild the
kernel package(s) as a who
Hi there,
I need to apply the following
https://lore.kernel.org/linux-rdma/1645106372-23004-1-git-send-email-mike.marcinis...@cornelisnetworks.com/T/#u
and rebuild ib_qib. To rebuild I wrote the following script
($1 is the kernel version, i.e. 5.16.0-3)
#!/bin/sh
#use in /usr/src
set -e -x
tar
On Thu 10 Feb 2022 at 02:44:50 (-0500), Felix Miata wrote:
> David Wright composed on 2022-02-09 23:36 (UTC-0600):
> > On Wed 09 Feb 2022 at 23:09:40 (-0500), Felix Miata wrote:
>
> >> # inxi -S
> >> System:
> >> Host: ab560 Kernel: 5.15.0-3-amd64 x86_64 bits: 64 Desktop: Trinity
> >>
On Wed, Feb 09, 2022 at 11:09:40PM -0500, Felix Miata wrote:
> mv: cannot move '/boot/initrd.img-5.15.0-3-amd64.new' to
> '/boot/initrd.img-5.15.0-3-amd64': Operation not permitted
> What can be done to make dpkg stop trying to replace the initrd that I have
> made
> immutable? I don't want it
David Wright composed on 2022-02-09 23:36 (UTC-0600):
> On Wed 09 Feb 2022 at 23:09:40 (-0500), Felix Miata wrote:
>> # inxi -S
>> System:
>> Host: ab560 Kernel: 5.15.0-3-amd64 x86_64 bits: 64 Desktop: Trinity
>> Distro: Debian GNU/Linux bookworm/sid
>> # dpkg --configure
On Wed 09 Feb 2022 at 23:09:40 (-0500), Felix Miata wrote:
> # inxi -S
> System:
> Host: ab560 Kernel: 5.15.0-3-amd64 x86_64 bits: 64 Desktop: Trinity
> Distro: Debian GNU/Linux bookworm/sid
> # dpkg --configure linux-image-5.15.0-3-amd64
> Setting up linux-image-5.15.0-3-amd64 (5.15.15-2)
# inxi -S
System:
Host: ab560 Kernel: 5.15.0-3-amd64 x86_64 bits: 64 Desktop: Trinity
Distro: Debian GNU/Linux bookworm/sid
# dpkg --configure linux-image-5.15.0-3-amd64
Setting up linux-image-5.15.0-3-amd64 (5.15.15-2) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating
Vincent Lefevre wrote:
> I was just asking, in case there would be some advantage.
> For instance, it seems to install build dependencies automatically.
I understand. It is bothering to install dependencies, I agree - but it is
one time job. I do it when setting up the build environment - it
On 2020-04-23 08:31:32 +0200, deloptes wrote:
> Vincent Lefevre wrote:
>
> > I was wondering whether apt-build could automate things even more
> > than my current solution, but it seems that my current solution can
> > do more, at least for the goal of just patching source packages and
> >
Vincent Lefevre wrote:
> I was wondering whether apt-build could automate things even more
> than my current solution, but it seems that my current solution can
> do more, at least for the goal of just patching source packages and
> rebuilding.
I did not miss this in the beginning. I did not
On 2020-04-22 22:18:19 +0200, deloptes wrote:
> Vincent Lefevre wrote:
>
> > On 2020-04-22 08:29:09 +0200, deloptes wrote:
> >> OK I understand now. I did not have a problem to add a new section in the
> >> changelog with
> >> dch -v "4:$BUILDISTRO_NAME" -D "$DISTRO_NAME" -c $debian/changelog \
Vincent Lefevre wrote:
> On 2020-04-22 08:29:09 +0200, deloptes wrote:
>> OK I understand now. I did not have a problem to add a new section in the
>> changelog with
>> dch -v "4:$BUILDISTRO_NAME" -D "$DISTRO_NAME" -c $debian/changelog \
>> "Autogenerated by building script"
>>
>>
On 2020-04-22 08:29:09 +0200, deloptes wrote:
> OK I understand now. I did not have a problem to add a new section in the
> changelog with
> dch -v "4:$BUILDISTRO_NAME" -D "$DISTRO_NAME" -c $debian/changelog \
> "Autogenerated by building script"
>
> $BUILDISTRO_NAME is the release number
Vincent Lefevre wrote:
> I think that you misunderstood. I'm not talking about the build log
> (which the end user will never see), but the Debian changelog file,
> which will be installed as
>
> /usr/share/doc//changelog.Debian.gz
>
> For instance, for libtool on my machines I can see e.g.:
>
On 2020-04-21 20:53:42 +0200, deloptes wrote:
> Vincent Lefevre wrote:
>
> > Patches don't add log messages in general. I meant like what dch
> > does.
> yes because you are working outside of debuild. debuild creates a build file
> that includes all the steps to produce the build
>
> in any
Vincent Lefevre wrote:
> Patches don't add log messages in general. I meant like what dch
> does.
yes because you are working outside of debuild. debuild creates a build file
that includes all the steps to produce the build
in any case
ention, it's
> > > relatively simple.
> >
> > Can it handle the rebuild for multiple architectures?
>
> No. As far as I can tell, you cannot pass it that '-a' flag for
> dpkg-buildpackage.
> But then, '-a' means cross-compilation, and that tends to implement its
> own,
ckages and would like those packages to be rebuilt with my changes
> > > when a new package version is available.
> >
> > apt install apt-build
> >
> > Requires some scripting to run without a human intervention, it's
> > relatively simple.
>
> Can it
version is available.
>
> apt install apt-build
>
> Requires some scripting to run without a human intervention, it's
> relatively simple.
Can it handle the rebuild for multiple architectures?
And can one provide a log message associated with each patch?
FYI, I currently use a
Hi,
Thank you, I will check this out.
Thomas
Le mar. 21 avr. 2020 à 15:45, Reco a écrit :
>
> Hi.
>
> On Tue, Apr 21, 2020 at 03:23:37PM +0200, Thomas Martin wrote:
> > My goal is simple : I'm applying few modifications on some Debian
> > packages and would like those packages to be
Hi.
On Tue, Apr 21, 2020 at 03:23:37PM +0200, Thomas Martin wrote:
> My goal is simple : I'm applying few modifications on some Debian
> packages and would like those packages to be rebuilt with my changes
> when a new package version is available.
apt install apt-build
Requires some
Hello,
I would like to know what is the simplest way to rebuild Debian
packages automatically when a new version of the package is released ?
My goal is simple : I'm applying few modifications on some Debian
packages and would like those packages to be rebuilt with my changes
when a new package
SOLUTION:
I went though and added all the keys again and now it's working again.
sudo apt-key adv --keyserver keyserver.debian.org --recv-keys [KEY_MISSING]
Works good now. Thanks everyone for the help.
Phil
On 16/05/2018 17:06, deloptes wrote:
Philip wrote:
I recently had to move a disk
Philip wrote:
> I recently had to move a disk image from machine to another machine
> however when I fired it up on the new machine the APT keys were
> broken/corrupted. The errors I'm getting are below... Is there a simple
> way of fixing this?
perhaps it is not only the gpg keys that got
I recently had to move a disk image from machine to another machine
however when I fired it up on the new machine the APT keys were
broken/corrupted. The errors I'm getting are below... Is there a simple
way of fixing this?
philip@cetus:~# apt update
Ign:1 http://mirrors.linode.com/debian
On 2018-01-25 23:03:50 +0100, Vincent Lefevre wrote:
> On 2018-01-25 15:30:02 +0100, to...@tuxteam.de wrote:
> > On Thu, Jan 25, 2018 at 02:56:17PM +0100, Vincent Lefevre wrote:
> > > To rebuild a Debian package, one can use:
> > >
> > > debuild -i -us -u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, May 15, 2018 at 06:48:15PM +1200, Philip wrote:
> Hi there,
>
> I've managed to break my apt keys is there a way to regenerate them?
If I understand you correctly, you want to re-install the package
"debian-archive-keyring".
Of course,
Hi there,
I've managed to break my apt keys is there a way to regenerate them?
Phil
iptables setup. So it fell back on my fail2ban protection
> against ssh scripts.
>
> /usr/bin/gcc-4.8 was on strange file permissions, with not even
> execute perms for root. Thus de dkms rebuild failed.
>
> now my questions:
>
> why was gcc-4.8 binary set to no execution, even
.
/usr/bin/gcc-4.8 was on strange file permissions, with not even execute
perms for root. Thus de dkms rebuild failed.
now my questions:
why was gcc-4.8 binary set to no execution, even for root?
why is xtables-addons-dkms not using gcc-4.9?
a simple chmod 700 /usr/bin/gcc-4.8 fixed the problem
On 2018-01-26 09:47:58 +, Curt wrote:
> On 2018-01-25, Vincent Lefevre wrote:
> > On 2018-01-25 14:53:14 +, Curt wrote:
> >> On 2018-01-25, wrote:
> >> >
> >> > It seems that you are missing the '386 (or more precisely the '686)
>
On 2018-01-25, Vincent Lefevre wrote:
> On 2018-01-25 14:53:14 +, Curt wrote:
>> On 2018-01-25, wrote:
>> >
>> > It seems that you are missing the '386 (or more precisely the '686)
>> > executables. Perhaps you need the package
On 2018-01-25 14:53:14 +, Curt wrote:
> On 2018-01-25, wrote:
> >
> > It seems that you are missing the '386 (or more precisely the '686)
> > executables. Perhaps you need the package dpkg-cross.
> >
> >> If I need binutils-i686-linux-gnu, shouldn't
On 2018-01-25 15:30:02 +0100, to...@tuxteam.de wrote:
> On Thu, Jan 25, 2018 at 02:56:17PM +0100, Vincent Lefevre wrote:
> > To rebuild a Debian package, one can use:
> >
> > debuild -i -us -uc -b
> >
> > But how to rebuild a Debian package for a foreign arch
On 2018-01-25, wrote:
>
> It seems that you are missing the '386 (or more precisely the '686)
> executables. Perhaps you need the package dpkg-cross.
>
>> If I need binutils-i686-linux-gnu, shouldn't dpkg-buildpackage fail
>> when checking the build
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jan 25, 2018 at 02:56:17PM +0100, Vincent Lefevre wrote:
> To rebuild a Debian package, one can use:
>
> debuild -i -us -uc -b
>
> But how to rebuild a Debian package for a foreign architecture?
> In my case for i386 fro
To rebuild a Debian package, one can use:
debuild -i -us -uc -b
But how to rebuild a Debian package for a foreign architecture?
In my case for i386 from an amd64 machine. I've tried
debuild -i -us -uc -b -a i386
but the build fails at some point:
[...]
dh_strip -a
dh_strip: Compatibility
On Sun, Jan 07, 2018 at 11:31:58PM +, Yao Wei wrote:
> It is caused by a missing dependency libelf-dev.
> It is already reported against linux-headers-4.14.0-3-amd64:
> https://bugs.debian.org/886474
>
> I have the same symptom of broadcom-sta-dkms
>
Interesting. I noticed the libelf
Hello Dan — thanks kindly, I had indeed not noticed….
I guess I’ll have a chance to test if the libelf-dev issue is really the fix
when the patches do roll out.
In that vein, I would like to note that
https://security-tracker.debian.org/tracker/CVE-2017-5754
ebulding the modules manually --
> https://askubuntu.com/questions/53364/command-to-rebuild-all-dkms-modules-for-all-installed-kernels/174017
>
> <https://askubuntu.com/questions/53364/command-to-rebuild-all-dkms-modules-for-all-installed-kernels/174017>
> -- did fix it.
>
> Did I miss something?
>
> Cheers!
>
> --
> Boyan Penkov
>
On 01/07/2018 07:47 PM, Boyan Penkov wrote:
> and a backport (4.14.0-bpo2) -- in light of meltdown --
To avoid a false sense of security: according to [1], [2], [3], the
current stretch-bpo kernel (linux-image-4.14.0-0.bpo.2-$arch) does *NOT*
yet include any mitigations against meltdown.
Daniel
e latest update to 4.9.0-5, and a backport (4.14.0-bpo2) -- in
> light of meltdown -- my nvidia drivers failed to load.
>
> Rebulding the modules manually --
>
> https://askubuntu.com/questions/53364/command-to-rebuild-all-dkms-modules-for-all-installed-kernels/174017
> -- did
Hello,
After the latest update to 4.9.0-5, and a backport (4.14.0-bpo2) -- in
light of meltdown -- my nvidia drivers failed to load.
Rebulding the modules manually --
https://askubuntu.com/questions/53364/command-to-rebuild-all-dkms-modules-for-all-installed-kernels/174017
-- did fix it.
Did I
I am currently trying to rebuild a RAID1 where one of the disks was
marked failed due to a power issue. I have re-added the disk like I
had done before when replacing other failed raid disks, but in this
case, once the raid rebuild starts, I start getting filesystem errors
and the filesystem gets
Le samedi 09 novembre 2013 à 20:30, Charles Plessy a écrit :
depuis la version 1.14.7 de dpkg, dpkg-buildpackage utilise automatiquement
fakeroot si nécessaire. Donc on peut omettre -rfakeroot.
Ça c'est une bonne nouvelle, ça va augmenter l'espérance de vie de mes
claviers ;-)
Merci pour
Bonjour,
Le tuto sur le BSP/Beginers est plutôt pas mal selon moi.
Je l'utilise régulièrement:
https://wiki.debian.org/BSP/BeginnersHOWTO
Joseph
2013/11/9 laurent Trinques scor...@qelectrotech.org:
Le vendredi 8 novembre 2013, 10:20:01 Guy Roussin a écrit :
Bonjour,
Bosses plutôt en tant
Le Fri, Nov 08, 2013 at 10:20:01AM +0100, Guy Roussin a écrit :
Bosses plutôt en tant que user normal ... sauf lorsqu'il s'agit
d'installerdes paquets (sudo ...).
p.ex. :
$ sudo apt-get build-dep toto
$ dpkg-buildpackage -rfakeroot -us -uc -b
Bonjour tout le monde,
depuis la version
Le vendredi 8 novembre 2013, 10:20:01 Guy Roussin a écrit :
Bonjour,
Bosses plutôt en tant que user normal ... sauf lorsqu'il s'agit
d'installerdes paquets (sudo ...).
p.ex. :
$ sudo apt-get build-dep toto
$ dpkg-buildpackage -rfakeroot -us -uc -b
Tu pourrais utiliser le numéro de
environnement propre, avec pbuilder par exemple,
pour vérifier les dépendances de build, surtout si tu envisages de le
rendre disponible.
3. Imaginons maintenant que le paquet toto, ce ne soit
pas n'importe quel paquet mais que ce soit carrément
linux-image-3.2.0-4-amd64. La méthode de rebuild
donnée
toto-foo sont incompatibles.
3. Imaginons maintenant que le paquet toto, ce ne soit
pas n'importe quel paquet mais que ce soit carrément
linux-image-3.2.0-4-amd64. La méthode de rebuild
donnée en exemple ci-dessus-elle toujours valable ?
Ou bien pour un rebuild du noyau, c'est un cas
spécifique
pas n'importe quel paquet mais que ce soit carrément
linux-image-3.2.0-4-amd64. La méthode de rebuild
donnée en exemple ci-dessus-elle toujours valable ?
Ou bien pour un rebuild du noyau, c'est un cas
spécifique ?
4. Même question pour le renommage. Lors du rebuild
de linux-image-3.2.0-4-amd64 : y
soit carrément
linux-image-3.2.0-4-amd64. La méthode de rebuild
donnée en exemple ci-dessus-elle toujours valable ?
Ou bien pour un rebuild du noyau, c'est un cas
spécifique ?
Je pense que fakeroot make deb-pkg suffit
--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org
/ftp.us.debian.org_debian_dists_wheezy_main_binary-amd64_Packages:
Hash Sum mismatch
E: Some index files failed to download. They have been ignored, or old
ones used instead.
E: Couldn't rebuild package cache
Thanks ahead for the suggestions,
I think that when your /var filled up, you were left
On Sun 24 Jun 2012 at 13:01:37 +0800, lina wrote:
On Sun, Jun 24, 2012 at 12:39 PM, lina lina.lastn...@gmail.com wrote:
Hi,
I don't know how to fix the following problem,
It's fixed after changing the source.list to my former mirror.
Switching backwards and forwards between mirrors may
,
Best regards,
W: Failed to fetch
gzip:/var/lib/apt/lists/partial/ftp.us.debian.org_debian_dists_wheezy_main_binary-amd64_Packages:
Hash Sum mismatch
E: Some index files failed to download. They have been ignored, or old
ones used instead.
E: Couldn't rebuild package cache
Thanks ahead
Hi,
I don't know how to fix the following problem,
W: Failed to fetch
gzip:/var/lib/apt/lists/partial/ftp.us.debian.org_debian_dists_wheezy_main_binary-amd64_Packages:
Hash Sum mismatch
E: Some index files failed to download. They have been ignored, or old
ones used instead.
E: Couldn't rebuild
/ftp.us.debian.org_debian_dists_wheezy_main_binary-amd64_Packages:
Hash Sum mismatch
E: Some index files failed to download. They have been ignored, or old
ones used instead.
E: Couldn't rebuild package cache
Thanks ahead for the suggestions,
Best regards,
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
instead.
E: Couldn't rebuild package cache
I looked for the solution to this myself some time ago, and found
somewhere something about a bug and that and bzip2 had to be installed
and then it worked without a hitch.
Hope that helps you.
Charlie
I am going to be rebuilding two workstations on my network, primarily to
get them to amd64 on new hardware. I've been watching the lists for any
gotchas that might have cropped up, but I haven't really seen anything. So
I thought I would ask before doing the reinstall. Is there anything that I
Hi all,
On my squeeze system, I would like to get a PHP 5.2 release.
This is for development, my dev team needs it.
This is the changelog about 5.2.6 http://goo.gl/Ndvxu
If I get the source package and just build it, I'll get the latest
version, which I dont want.
Where, in what archive
On Fri, 23 Sep 2011 16:35:37 +0300, Mihamina Rakotomandimby wrote:
On my squeeze system, I would like to get a PHP 5.2 release. This is for
development, my dev team needs it. This is the changelog about 5.2.6
http://goo.gl/Ndvxu
If I get the source package and just build it, I'll get the
On 09/23/2011 05:08 PM, Camaleón wrote:
Debian source packages for older versions can be fetched from here:
http://snapshot.debian.org/package/php5/
MMM,... I love Debian!
Thank Camaleon.
--
RMA.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of
Taylor Brown wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey, thanks! I guess it was a bug with the source because after a wait
and an update the kernel compiled fine.
Great! Glad it worked...
Hugo
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey, thanks! I guess it was a bug with the source because after a wait
and an update the kernel compiled fine.
Taylor
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609846
https://bugzilla.kernel.org/show_bug.cgi?id=34532
https://bugzilla.kernel.org/show_bug.cgi?id=15707
https://bugs.launchpad.net/bugs/703302
As a workaround, I am trying to rebuild the Debian kernel with a
modified DSDT file. I have edited
-bin/bugreport.cgi?bug=609846
https://bugzilla.kernel.org/show_bug.cgi?id=34532
https://bugzilla.kernel.org/show_bug.cgi?id=15707
https://bugs.launchpad.net/bugs/703302
As a workaround, I am trying to rebuild the Debian kernel with a
modified DSDT file. I have edited and recompiled the DSDT file
Pues yo usaria un arreglo RAID 5. Es mas completo que el RAID 1 en donde se
deserdician discos por el sistema espejo de los datos. Ademas, se sabe de
casos en los que incluso los RAID 1 han fallado y dado perdida de datos. Y la
mayoria casi siempre no tiene otra alternativa que la de pedir
El 10/05/11 14:31, salmuer escribió:
Pues yo usaria un arreglo RAID 5. Es mas completo que el RAID 1 en donde se
deserdician discos por el sistema espejo de los datos. Ademas, se sabe de
casos en los que incluso los RAID 1 han fallado y dado perdida de datos. Y
la
mayoria casi siempre
El mar, 10-05-2011 a las 12:31 +, salmuer escribió:
Pues yo usaria un arreglo RAID 5. Es mas completo que el RAID 1 en donde se
deserdician discos por el sistema espejo de los datos. Ademas, se sabe de
casos en los que incluso los RAID 1 han fallado y dado perdida de datos. Y
la
El Tue, 10 May 2011 14:50:28 +0200, Juan Antonio escribió:
El 10/05/11 14:31, salmuer escribió:
Pues yo usaria un arreglo RAID 5. Es mas completo que el RAID 1 en
donde se deserdician discos por el sistema espejo de los datos.
Ademas, se sabe de casos en los que incluso los RAID 1 han
de 160gb. Todo perfecto, pero un disco empezo a funcionar mal, apague,
cambie disco y funcion Rebuild.
Despues de 2 meses mando un reboot, y veo que aun sigue en Rebuild, es
decir nunca se realizo el mirroring de nuevo.
En su momento para que debian me tome el RAID, en la instalacion le di
el
active RAID y cree el array mirroring con 2 discos
de 160gb. Todo perfecto, pero un disco empezo a funcionar mal, apague,
cambie disco y funcion Rebuild.
Despues de 2 meses mando un reboot, y veo que aun sigue en Rebuild, es
decir nunca se realizo el mirroring de nuevo.
En su momento para que
Alex,
You can't rebuild single module. If you wanna do it the Debian way, you
have to rebuild whole kernel (install kernel-package and see make-kpkg
manual for details).
On Wed, Jun 23, 2010 at 02:41:45PM +1000, Alexander Samad wrote:
I need to make a quick change to a kernel module, I would
Okay, thats a bit extreme, m-a seems to be able to build a module with
just the headers.
so all I want to do is rebuild qcserial, patched it to add new id.
don't need to produce a deb.
what i tried was installed the linux-source-2.6.34-1 deb
copied .config from the headers directory did
make
Le 14783ième jour après Epoch,
Alexander Samad écrivait:
Okay, thats a bit extreme, m-a seems to be able to build a module with
just the headers.
so all I want to do is rebuild qcserial, patched it to add new id.
don't need to produce a deb.
what i tried was installed the linux-source
I need to make a quick change to a kernel module, I would like to just
get the source and make the change and build.
How can I build ??? I did a google, but couldn't find the debian way
of building with linux-headers..
Alex
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
On Mon, 2010-05-17 at 00:26 +0200, deloptes wrote:
John A. Sullivan III wrote:
libkode.so.1.0.0
you need this ... did you enable shared?
where do you get the code for kdepim-3.5.9? from Trinity project ?
regards
I used the Debian source. We had sponsored some fixes with Trinity
John A. Sullivan III wrote:
libkode.so.1.0.0
you need this ... did you enable shared?
where do you get the code for kdepim-3.5.9? from Trinity project ?
regards
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Hello, all. We are attempting to rebuild kdepim on Lenny using patches
supplied by the Trinity project (http://trinity.pearsoncomputing.net/)
to fix some of the critical Kontact issues. When we try to do so, we
fail with:
g++ -DHAVE_BOOST -DNDEBUG -DNO_DEBUG -g -O2 -g -Wall -O2
On Fri, Oct 24, 2008 at 06:54:17AM +0200, Peter Jordan wrote:
Hello,
I'm searching for a daemon which checks if a newer version of a package
is available, downloads its sorces, patches the sources, rebuilds the
package and if that all successes then the daemon should upload the new
package
then the daemon should upload the new
package to my debian repository.
Is there any working solution?
Something on top of buildd/wanna-build ?
Do you want to assume that a package has a get-orig-source target? A
debian/watch file?
I want to rebuild existing versions of a package, not new versions
Ron Johnson, 10/24/2008 07:46 AM:
On 10/23/08 23:54, Peter Jordan wrote:
Hello,
I'm searching for a daemon which checks if a newer version of a package
is available, downloads its sorces, patches the sources, rebuilds the
package and if that all successes then the daemon should upload the
On 10/24/08 08:26, Peter Jordan wrote:
Ron Johnson, 10/24/2008 07:46 AM:
On 10/23/08 23:54, Peter Jordan wrote:
Hello,
I'm searching for a daemon which checks if a newer version of a package
is available, downloads its sorces, patches the sources, rebuilds the
package and if that all
Hello,
I'm searching for a daemon which checks if a newer version of a package
is available, downloads its sorces, patches the sources, rebuilds the
package and if that all successes then the daemon should upload the new
package to my debian repository.
Is there any working solution?
Thanks,
On 10/23/08 23:54, Peter Jordan wrote:
Hello,
I'm searching for a daemon which checks if a newer version of a package
is available, downloads its sorces, patches the sources, rebuilds the
package and if that all successes then the daemon should upload the new
package to my debian repository.
with no problem at all.
Are you certain the rebuild was completed? Did you --add the drives
to the array after --remove'ing the broken ones?
State : active, degraded
[...]
0 00- removed
1 00- removed
2 340
Also sprach Mike Bird [EMAIL PROTECTED] [2007.08.18.1537 +0200]:
3) RAID 5 is not resilient against multiple failures. We now use RAID 1.
RAID 1 is also faster, although it sometimes requires more drives.
In extreme cases we use RAID 1 with three or more drives.
On Monday 20 August 2007
also sprach Mike Bird [EMAIL PROTECTED] [2007.08.20.1627 +0200]:
3) RAID 5 is not resilient against multiple failures. We now use RAID 1.
RAID 1 is also faster, although it sometimes requires more drives.
In extreme cases we use RAID 1 with three or more drives.
On Monday 20 August
a difference. I had not
partitioned the drives since mdadm seems okay without partitions. He
said even if I only use one drive-wide partition, I should still
partition the drives in a RAID first.
Fortunately, this was in a backup system so I can get new drives and
rebuild it from scratch
don't see why you'd have to do this. The partition table would get
overwritten anyway.
Fortunately, this was in a backup system so I can get new drives
and rebuild it from scratch with the larger drives. I've already
got ideas for using the failed drives that are proving to be
just fine.
Have you
friend is confused. :)
I don't see why you'd have to do this. The partition table would get
overwritten anyway.
I've noticed, though, that on one system I had originally defined the
raid using /dev/hde1, hdf1, and so on. When I tried to rebuild it
with /dev/hde, hdf, and so on, it would
, it had never started rebuilding the spare.
This situation *should* be recoverable. Contact me off-list if you'd
be willing to let me log in as root and have a look.
I've noticed, though, that on one system I had originally defined the
raid using /dev/hde1, hdf1, and so on. When I tried to rebuild
on. When I tried to rebuild
it with /dev/hde, hdf, and so on, it would not rebiuld.
Sure, partitions have different offsets, so the superblock could not
be found.
Have you inspected the smartctl output and checked for SMART
errors?
I looked at the logs. Is this a different output
also sprach Hal Vaughan [EMAIL PROTECTED] [2007.08.21.0003 +0200]:
Any suggestions or warnings from others so I can make sure this doens't
happen again are appreciated. Remember, the two drives I've already
removed that mdadm had said were bad have tested out as fine. I suspect
, find out why mdadm is not
rebuilding the RAID or to get it to rebuild it? It seems to think the
drives are all okay when it's adding them and doesn't report any issues
with any drives until it's done, then it says there aren't enough
drives to start the RAID.
Hal
--
To UNSUBSCRIBE, email
that there are actually two bad drives.
Any ideas how I can get more information, find out why mdadm is not
rebuilding the RAID or to get it to rebuild it? It seems to think the
drives are all okay when it's adding them and doesn't report any issues
with any drives until it's done, then it says
I just moved a debian installation from one system to another by mirroring
/opt, etc, /home, /var, and /usr/local -- and then using dpkg
--set-selections to get all the same packages installed on the new box.
Everything's gone great except for the alternatives system. For some reason,
none of the
1 - 100 of 214 matches
Mail list logo