Re: with 3~beta21 too, was: Re: "E: Broken packages" with 2.8
On 9/18/06, Toni Mueller <[EMAIL PROTECTED]> wrote: [...] > You are using a developer version from the FAI apt repository, or the > version from Debian testing. The version I'm using comes from Debian unstable. The latest version I found in the Cologne FAI repository was 2.10.5. There is also a development apt repository which should have always the newest developer version. I chose to try the 3-something version when I hit too many problems with the 2.x version (latest problems were something with dpkg and no way to create a working NFSROOT) Not being able to build a sarge NFSROOT on a sarge server, for sarge installation with FAI 2.x seems like a very strange error. This easy task should always be possible. Did you report details about this proble to this list? , and that I'll need to have 3.x to install Etch OR on amd64 anyway. So... I think I'll probably change the configuration to (try to) install testing instead of sarge RSN. What does RSN mean? I also understood some of the mails on this list as meaning that 2.10.x is more or less EOL'ed already. With EOL you mean End of Live, and with that, that we don't support FAI 2.x anymore, right? Here's as I see it: As far as I know, FAI 2.x is not being obsoleted or removed from the FAI apt repo at Uni Koeln. Actually, it can't because for FAI 3 we don't support compatibility to sarge, so we have to support it as long sarge is stable, at least. There's no decision if we will provide bugfixes for FAI 2.x until etch release or even after that. I problems are very heavy and there are a lot of users interested in that, it will be possible. > Fai 3 and above isn't made to work on a sarge server and to install > sarge clients. This has been announced a while ago. Ugh. I somehow managed to miss the announcement that it won't run on a sarge server. Where should I be looking? At least on fai-devel, maybe also somewhere on linux-fai, and maybe in some changelogs. In general, you should know that you cannot just install any package from unstable on stable and expect it to work flawlessly, so an announcement is nice, but not strictly necessary - you should now what you do when using unstable :) > But If the only change that make FAI 3 still work on sarge, to install > sarge, are in the config files, then this should be documented in the > wiki, I think. Would be nice of you if you could provide you full > NFSROOT config file there to help others. Once I get it working... Post further problems here, we might have answers. You can always grab the fai sources, change and rebuild them yourself. Of course it would be cool if we can retain backwards compatibilty. Subversion access (so you are able to checkin your changes in a developer branch for all to review and for thomas to put into trunk) can be obtained from thomas by getting and account on alioth. Henning
Re: with 3~beta21 too, was: Re: "E: Broken packages" with 2.8
Hello Henning, I'm on the list. So, please don't Cc me. On Mon, 18.09.2006 at 12:28:31 +0200, Henning Sprang <[EMAIL PROTECTED]> wrote: > On 9/18/06, Toni Mueller <[EMAIL PROTECTED]> wrote: > >I band-aided the problem and turned the 'install' into an 'aptitude' in > >fai/NFSROOT, removing some conflicting packages by hand. > >Is that the suggested course of action, or am I heading for other problems > >(except > >maybe increased disk usage)? > > Maybe you will be missing programs needed in the install process in > the nfsroot if yoiu just randomly remove packages. The conflicts occurred amongst the packages I added manually, so I don't think there'll be a problem. Also, I have a habit of replacing 'joe' (or was it 'jove'?) with vim, but that shouldn't have any impact on the system either. ;-) > You are using a developer version from the FAI apt repository, or the > version from Debian testing. The version I'm using comes from Debian unstable. The latest version I found in the Cologne FAI repository was 2.10.5. I chose to try the 3-something version when I hit too many problems with the 2.x version (latest problems were something with dpkg and no way to create a working NFSROOT), and that I'll need to have 3.x to install Etch OR on amd64 anyway. So... I think I'll probably change the configuration to (try to) install testing instead of sarge RSN. I also understood some of the mails on this list as meaning that 2.10.x is more or less EOL'ed already. > Fai 3 and above isn't made to work on a sarge server and to install > sarge clients. This has been announced a while ago. Ugh. I somehow managed to miss the announcement that it won't run on a sarge server. Where should I be looking? > We still might be able to add smaller fixes which are easy for us to > apply if there is no too much work to help you keep using fai 3 and > above with sarge, but it will not be our focus. Ok, understood. I hoped to deploy this server before Etch, however. > But If the only change that make FAI 3 still work on sarge, to install > sarge, are in the config files, then this should be documented in the > wiki, I think. Would be nice of you if you could provide you full > NFSROOT config file there to help others. Once I get it working... Best, --Toni++
Re: with 3~beta21 too, was: Re: "E: Broken packages" with 2.8
Hi Toni, On 9/18/06, Toni Mueller <[EMAIL PROTECTED]> wrote: [...] I band-aided the problem and turned the 'install' into an 'aptitude' in fai/NFSROOT, removing some conflicting packages by hand. Is that the suggested course of action, or am I heading for other problems (except maybe increased disk usage)? Maybe you will be missing programs needed in the install process in the nfsroot if yoiu just randomly remove packages. You are using a developer version from the FAI apt repository, or the version from Debian testing. Fai 3 and above isn't made to work on a sarge server and to install sarge clients. This has been announced a while ago. We still might be able to add smaller fixes which are easy for us to apply if there is no too much work to help you keep using fai 3 and above with sarge, but it will not be our focus. But If the only change that make FAI 3 still work on sarge, to install sarge, are in the config files, then this should be documented in the wiki, I think. Would be nice of you if you could provide you full NFSROOT config file there to help others. Henning
Re: with 3~beta21 too, was: Re: "E: Broken packages" with 2.8
Hello, On Sat, 16.09.2006 at 21:48:53 +0200, Toni Mueller <[EMAIL PROTECTED]> wrote: > # make-fai-nfsroot -v > ... lots of messages here, then: > The following packages have unmet dependencies: > texlive-lang-german: Depends: texlive-common but it is not going to be > installed > E: Broken packages > ERROR: 25600 25600 > ... some more messages, and then: I band-aided the problem and turned the 'install' into an 'aptitude' in fai/NFSROOT, removing some conflicting packages by hand. Is that the suggested course of action, or am I heading for other problems (except maybe increased disk usage)? Best, --Toni++
with 3~beta21 too, was: Re: "E: Broken packages" with 2.8
Hi, On Wed, 11.05.2005 at 10:00:57 +0200, Thomas Lange <[EMAIL PROTECTED]> wrote: > > On Wed, 11 May 2005 02:35:05 +0200 (CEST), [EMAIL PROTECTED] said: > > 2.6.5. it seems that there are really broken packages somewhere. > Call make-fai-nfsroot -v and see which package is broken. trying to build an install server on a sarge system for installing sarge, but with FAI 3~beta21, I also had # fai-setup ... some messages here... Upgrading /usr/lib/fai/nfsroot Adding additional packages to /usr/lib/fai/nfsroot: fai-nfsroot module-init-tools dhcp3-client ssh rdate lshw hwinfo portmap bootpc rsync wget lftp rsh-client less dump reiserfsprogs usbutils psmisc pciutils hdparm smartmontools parted mdadm lvm2 dnsutils ntpdate dosfstools cvs xfsprogs xfsdump sysutils dialog discover mdetect libnet-perl netcat libapt-pkg-perl console-tools console-common cfengine2 expect iproute vim debian-keyring apt-proxy python-twisted-conch libapache-mod-perl libapache-mod-ssl moinmoin-common python-moinmoin emacs21 emacs21-el pymacs latex-ucs tetex-extra latex-ucs-uninames texlive-lang-german grub lilo dmidecode hwtools read-edid E: Broken packages ERROR: 25600 25600 ... some more messages, and then: FAI setup finished. So, according to your advice above, I ran the make-fai-nfsroot alone: # make-fai-nfsroot -v ... lots of messages here, then: The following packages have unmet dependencies: texlive-lang-german: Depends: texlive-common but it is not going to be installed E: Broken packages ERROR: 25600 25600 ... some more messages, and then: make-fai-nfsroot finished properly. Well, what is a successful NFSROOT, then, if packages fail to install properly, and how can I tell the difference between a successful and a failed install in such a case, except for applying my personal judgement and agree that texlive-something might not be that important? Also, why are these packages, now listed in the file This is all i386 and sarge, except for the FAI versions which are somewhat mixed (latest of everything, preferred release 'koeln')... I think I'm a bit confused at this point. 8-\ So far, I'm iterating over the output of make-fai-nfsroot -v, adding packages to /etc/fai/NFSROOT as I go. There should be a better way. Best, --Toni++
Re: "E: Broken packages" with 2.8
> On Wed, 11 May 2005 22:00:03 +0200 (CEST), [EMAIL PROTECTED] said: > hm, that means everytime i update fai i also need to create a new mirror No. It only means that some packages in your mirror have dependencies, that can not be fullfiled, or that they do not match version numbers that are available in the official mirror (used during debootstrap). -- regards Thomas
Re: "E: Broken packages" with 2.8
> Your mirror seems not to be up to date or not completly in sync. > I have now problems createing a new nfsroot today with a brand new > mirror. > There are two locations whe you reference the mirror. > One is $FAI_DEBOOTSTRAP and the other is /etc/fai/sources/list. Seems > that the cfengine package is an older version. hm, that means everytime i update fai i also need to create a new mirror (i've created a local debian-mirror)? am i right that a workaround would be to change $FAI_DEBOOTSTRAP to my local debian mirror instead of the internet-mirror? thanks and regards mat.
Re: "E: Broken packages" with 2.8
> On Wed, 11 May 2005 16:56:21 +0200 (CEST), [EMAIL PROTECTED] said: > The following packages have unmet dependencies: > cfengine: Depends: perl5 > dpkg-dev: Depends: perl5 > Depends: perl-modules but it is not going to be installed > libnet-perl: Depends: perl (>= 5.6.0-16) but it is not going to be > installed > E: Broken packages Your mirror seems not to be up to date or not completly in sync. I have now problems createing a new nfsroot today with a brand new mirror. There are two locations whe you reference the mirror. One is $FAI_DEBOOTSTRAP and the other is /etc/fai/sources/list. Seems that the cfengine package is an older version. Here's my output from make-fai-nfsroot: . . Unpacking cfengine (from .../cfengine_1.6.5-1_i386.deb) ... . . > In my make-fai-nfsroot.conf-file I got : > FAI_DEBOOTSTRAP="sarge ftp://ftp.de.debian.org/debian"; That's correct. > This is the server where make-fai-nfsroot gets its files from, right? No this is where debootstrap get its files from. When adding additional packages, the URIs from /etc/fai/sources.list are used. Both need to be in sync, so the dependencies will match. > i tried to add "perl" and "perl-base" to "packages" in You do not need this. -- regards Thomas
Re: "E: Broken packages" with 2.8
> Call make-fai-nfsroot -v and see which package is broken. gets me the following output: The following packages have unmet dependencies: cfengine: Depends: perl5 dpkg-dev: Depends: perl5 Depends: perl-modules but it is not going to be installed libnet-perl: Depends: perl (>= 5.6.0-16) but it is not going to be installed E: Broken packages In my make-fai-nfsroot.conf-file I got : FAI_DEBOOTSTRAP="sarge ftp://ftp.de.debian.org/debian"; This is the server where make-fai-nfsroot gets its files from, right? i tried to add "perl" and "perl-base" to "packages" in make-fai-nfsroot.conf. a new make-fai-nfsroot ended in this error message: The following packages have unmet dependencies: perl: Depends: perl-base (= 5.8.4-6) but 5.8.4-8 is to be installed E: Broken packages well, at least it's less error-lines than before :) do you have any ideas what to do now? btw: meanwhile, i updated to 2.8.1 again, since the error appears in both-version, i'd rather fix it with the newer one. thanks in advance and regards mat.
Re: "E: Broken packages" with 2.8
> On Wed, 11 May 2005 02:35:05 +0200 (CEST), [EMAIL PROTECTED] said: > 2.6.5. it seems that there are really broken packages somewhere. Call make-fai-nfsroot -v and see which package is broken. -- regards Thomas
Re: "E: Broken packages" with 2.8
On Wed, May 11, 2005 at 02:35:05AM +0200, [EMAIL PROTECTED] wrote: > Am Montag, 9. Mai 2005 21:14 schrieb Steffen Grunewald: > > On Mon, May 09, 2005 at 06:31:35PM +0200, Holger Levsen wrote: > > > Hi Matthias, > > > > > > On Monday 09 May 2005 17:41, you wrote: > > > > recently I updated from FAI 2.6.5 to 2.8 in order to check out new > > > > features. Installation via aptitude from the sarge-mirrors worked > > > > without a problem. but when I start "fai-setup", it ends with the > > > > following message: > > > > > > iirc this was fixed in 2.8.1 - i'm not sure (*) where to get 2.8.1 now, > > > as 2.8.2 was just uploaded. Both, 2.8.1 and 2.8.2 are mainly bugfix > > > releases, targeted for sarge. > > > > AFAICT the sourceforge repositories keep all old versions (at least back to > > 2004 which should be sufficient for you). If you don't succeed, I might > > still have it on one of my harddisks -> PM. > > hi there! > > I downloaded the package (2.8.1) from sourceforge, but I'm still getting > this error-message... > the very bad thing is that this problem still occurs, if i downgrade to > 2.6.5. it seems that there are really broken packages somewhere. > any ideas? Only the request to make it possible to read some day the solution in the archive in the logically order. Please reply below the text. > thanks in advance > mat. TIA Geert. signature.asc Description: Digital signature
Re: "E: Broken packages" with 2.8
hi there! I downloaded the package (2.8.1) from sourceforge, but I'm still getting this error-message... the very bad thing is that this problem still occurs, if i downgrade to 2.6.5. it seems that there are really broken packages somewhere. any ideas? thanks in advance mat. Am Montag, 9. Mai 2005 21:14 schrieb Steffen Grunewald: > On Mon, May 09, 2005 at 06:31:35PM +0200, Holger Levsen wrote: > > Hi Matthias, > > > > On Monday 09 May 2005 17:41, you wrote: > > > recently I updated from FAI 2.6.5 to 2.8 in order to check out new > > > features. Installation via aptitude from the sarge-mirrors worked > > > without a problem. but when I start "fai-setup", it ends with the > > > following message: > > > > iirc this was fixed in 2.8.1 - i'm not sure (*) where to get 2.8.1 now, > > as 2.8.2 was just uploaded. Both, 2.8.1 and 2.8.2 are mainly bugfix > > releases, targeted for sarge. > > AFAICT the sourceforge repositories keep all old versions (at least back to > 2004 which should be sufficient for you). If you don't succeed, I might > still have it on one of my harddisks -> PM. > > Cheers, Steffen
Re: "E: Broken packages" with 2.8
On Mon, May 09, 2005 at 06:31:35PM +0200, Holger Levsen wrote:
> Hi Matthias,
>
> On Monday 09 May 2005 17:41, you wrote:
> > recently I updated from FAI 2.6.5 to 2.8 in order to check out new
> > features. Installation via aptitude from the sarge-mirrors worked without a
> > problem. but when I start "fai-setup", it ends with the following message:
>
> iirc this was fixed in 2.8.1 - i'm not sure (*) where to get 2.8.1 now, as
> 2.8.2 was just uploaded. Both, 2.8.1 and 2.8.2 are mainly bugfix releases,
> targeted for sarge.
>
AFAICT the sourceforge repositories keep all old versions (at least back to
2004 which should be sufficient for you). If you don't succeed, I might
still have it on one of my harddisks -> PM.
Cheers, Steffen
--
Steffen Grunewald * MPI fuer Gravitationsphysik (Albert-Einstein-Institut)
SciencePark Golm, Am Mühlenberg 1, D-14476 Potsdam * http://www.aei.mpg.de
* e-mail: steffen.grunewald(*)aei.mpg.de * +49-331-567-{fon:7233,fax:7298}
No Word/PPT mails - http://www.gnu.org/philosophy/no-word-attachments.html
Re: "E: Broken packages" with 2.8
Hi Matthias, On Monday 09 May 2005 17:41, you wrote: > recently I updated from FAI 2.6.5 to 2.8 in order to check out new > features. Installation via aptitude from the sarge-mirrors worked without a > problem. but when I start "fai-setup", it ends with the following message: iirc this was fixed in 2.8.1 - i'm not sure (*) where to get 2.8.1 now, as 2.8.2 was just uploaded. Both, 2.8.1 and 2.8.2 are mainly bugfix releases, targeted for sarge. regards, Holger (*) you can get the last >1000 days of debian-unstable from snapshot.debian.net pgp0IfHi1XfUw.pgp Description: PGP signature
"E: Broken packages" with 2.8
hi there! recently I updated from FAI 2.6.5 to 2.8 in order to check out new features. Installation via aptitude from the sarge-mirrors worked without a problem. but when I start "fai-setup", it ends with the following message: [...] Creating base.tgz ,,/etc/fai/sources.list" -> ,,/usr/lib/fai/nfsroot/etc/apt/sources.list" Upgrading /usr/lib/fai/nfsroot Adding additional packages to /usr/lib/fai/nfsroot: module-init-tools dhcp3-client ssh file rdate hwinfo portmap bootpc rsync wget rsh-client less dump reiserfsprogs usbutils ext2resize hdparm smartmontools parted raidtools2 lvm2 dnsutils ntpdate dosfstools cfengine cvs jove xfsprogs xfsdump sysutils dialog discover mdetect libnet-perl netcat libapt-pkg-perl grub lilo read-edid kudzu hwtools dmidecode E: Broken packages linuxserver:~# any ideas? thanks in advance! mat.
