Custom Search
|
Date: November 30, 2006
From: "Lorraine Krueger" <assistantupload@xxxxxxxxxxx>
Become RICH with MAKU Company Name: MAKEUP LIMITED (OTC BB:MAKU.OB) Symbol: MAKU Price: $0.47 5-day Target: $2 Current Market: Very Bullish YOU MAKE MAKU! CATCH YOUR CHANGE! DON'T SLEEP ON THE 30TH NOV! For getting better profit tell about this letter to post it on forums you know. It will cause blast of activity and increasing of the price.
Date: November 29, 2006
From: "Nicola Collins" <00nicolc@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
i am looking for Ian Miller, aka Besok, and would really like to contact him, but he has his e-mail protected. how can i contact him through your website? Nikki Collins
Date: November 29, 2006
From: Konstantinos Koukopoulos <kouk@xxxxxxxxxx>
In-reply-to:
<456CC8CE.3080300@xxxxxxxxxxx>
References:
<200611281616.55919.kouk@xxxxxxxxxx> <Pine.LNX.4.62.0611282029180.12821@xxxxxxxxxxxxxxxx> <456CC8CE.3080300@xxxxxxxxxxx>
On Wed 29 Nov 2006 01:39, Aurelien Jarno wrote: > Petr Salinger a écrit : > > Hi. > > > >> I was about to report this in the BTS but I'm a bit confused about which > >> package is responsible. The problem is that in kfreebsd-kernel-headers > >> (=0.22) and the kfreebsd-5 source, <sys/syslimits.h> has conflicting > >> definitions of ARG_MAX. In kfreebsd-kernel-headers the value is 262144 > >> while in the kernel package there is the patch 905_grow_arg_max.diff > >> which raises ARG_MAX to 131072. Both are pretty high but I know of at > >> least one case where this is a problem: > >> kdepim is FTBFS again because when dh_fixperms runs for kdepim-doc it > >> fails with "xargs: chown: Argument list too long". > >> > >> So, this is the problem, but what is the solution? I'm a bit mixed up on > >> which source packages are responsible in this case. > > > > Some history: > > > > Plain FreeBSD 5.x have had limit 64 KB, it have been too low, > > so it have been raised in kfreebsd-5 package to 128 KB. > > > > Plain FreeBSD 6.x have limit 256 KB in general, 64 KB for arm and > > powerpc. It is again adjusted in kfreebsd-6 package, > > the limit is 256 KB in general, 128 KB for arm and powerpc. > > > > Current kfreebsd-kernel-headers is based on kfreebsd-6, > > so on both i386 and amd64 it is 256 KB. > > > > IMHO reasonable long term solutions are > > > > a) raise limit in kfreebsd-5 package to match limits in kfreebsd-6, > > build it, upload it, install on buildd machine > > > > b) install on buildd machine a kfreebsd-6 package > > and declare kfreebsd-5 deprecated > > > > Short term solution for kdepim is to requeue it > > on a buildd running 6.x kernel with enough memory. > > I have implemented b), because the only buildd that was running a 6.x > kernel has no swap and is not able to build kdepim... > > I have requeued all packages, so kdepim should be built now. Thanks Petr and Aurelien! Kostas
Date: November 28, 2006
From: Aurelien Jarno <aurelien@xxxxxxxxxxx>
In-reply-to:
<Pine.LNX.4.62.0611282029180.12821@xxxxxxxxxxxxxxxx>
References:
<200611281616.55919.kouk@xxxxxxxxxx> <Pine.LNX.4.62.0611282029180.12821@xxxxxxxxxxxxxxxx>
Petr Salinger a écrit : > Hi. > >> I was about to report this in the BTS but I'm a bit confused about which >> package is responsible. The problem is that in kfreebsd-kernel-headers >> (=0.22) >> and the kfreebsd-5 source, <sys/syslimits.h> has conflicting definitions of >> ARG_MAX. In kfreebsd-kernel-headers the value is 262144 while in the kernel >> package there is the patch 905_grow_arg_max.diff which raises ARG_MAX to >> 131072. Both are pretty high but I know of at least one case where this is a >> problem: >> kdepim is FTBFS again because when dh_fixperms runs for kdepim-doc it fails >> with "xargs: chown: Argument list too long". >> >> So, this is the problem, but what is the solution? I'm a bit mixed up on >> which >> source packages are responsible in this case. > > Some history: > > Plain FreeBSD 5.x have had limit 64 KB, it have been too low, > so it have been raised in kfreebsd-5 package to 128 KB. > > Plain FreeBSD 6.x have limit 256 KB in general, 64 KB for arm and powerpc. > It is again adjusted in kfreebsd-6 package, > the limit is 256 KB in general, 128 KB for arm and powerpc. > > Current kfreebsd-kernel-headers is based on kfreebsd-6, > so on both i386 and amd64 it is 256 KB. > > IMHO reasonable long term solutions are > > a) raise limit in kfreebsd-5 package to match limits in kfreebsd-6, > build it, upload it, install on buildd machine > > b) install on buildd machine a kfreebsd-6 package > and declare kfreebsd-5 deprecated > > Short term solution for kdepim is to requeue it > on a buildd running 6.x kernel with enough memory. I have implemented b), because the only buildd that was running a 6.x kernel has no swap and is not able to build kdepim... I have requeued all packages, so kdepim should be built now. Bye, Aurelien -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian developer | Electrical Engineer `. `' aurel32@xxxxxxxxxx | aurelien@xxxxxxxxxxx `- people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to debian-bsd-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
Date: November 28, 2006
From: Petr Salinger <Petr.Salinger@xxxxxxxxx>
In-reply-to:
<200611281616.55919.kouk@xxxxxxxxxx>
References:
<200611281616.55919.kouk@xxxxxxxxxx>
Hi.
I was about to report this in the BTS but I'm a bit confused about which package is responsible. The problem is that in kfreebsd-kernel-headers (=0.22) and the kfreebsd-5 source, <sys/syslimits.h> has conflicting definitions of ARG_MAX. In kfreebsd-kernel-headers the value is 262144 while in the kernel package there is the patch 905_grow_arg_max.diff which raises ARG_MAX to 131072. Both are pretty high but I know of at least one case where this is a problem: kdepim is FTBFS again because when dh_fixperms runs for kdepim-doc it fails with "xargs: chown: Argument list too long". So, this is the problem, but what is the solution? I'm a bit mixed up on which source packages are responsible in this case.
Some history: Plain FreeBSD 5.x have had limit 64 KB, it have been too low, so it have been raised in kfreebsd-5 package to 128 KB. Plain FreeBSD 6.x have limit 256 KB in general, 64 KB for arm and powerpc. It is again adjusted in kfreebsd-6 package, the limit is 256 KB in general, 128 KB for arm and powerpc. Current kfreebsd-kernel-headers is based on kfreebsd-6, so on both i386 and amd64 it is 256 KB. IMHO reasonable long term solutions are a) raise limit in kfreebsd-5 package to match limits in kfreebsd-6, build it, upload it, install on buildd machine b) install on buildd machine a kfreebsd-6 package and declare kfreebsd-5 deprecated Short term solution for kdepim is to requeue it on a buildd running 6.x kernel with enough memory. Petr
Date: November 28, 2006
From: Konstantinos Koukopoulos <kouk@xxxxxxxxxx>
Hello, I was about to report this in the BTS but I'm a bit confused about which package is responsible. The problem is that in kfreebsd-kernel-headers (=0.22) and the kfreebsd-5 source, <sys/syslimits.h> has conflicting definitions of ARG_MAX. In kfreebsd-kernel-headers the value is 262144 while in the kernel package there is the patch 905_grow_arg_max.diff which raises ARG_MAX to 131072. Both are pretty high but I know of at least one case where this is a problem: kdepim is FTBFS again because when dh_fixperms runs for kdepim-doc it fails with "xargs: chown: Argument list too long". So, this is the problem, but what is the solution? I'm a bit mixed up on which source packages are responsible in this case. Thanks, Kostas
Date: November 27, 2006
From: Petr Salinger <Petr.Salinger@xxxxxxxxx>
In-reply-to:
<20061123104600.0acc84a7.h_p_f_n@xxxxxxxxxxxx>
References:
<20061123104600.0acc84a7.h_p_f_n@xxxxxxxxxxxx>
Hi,
I did'nt find valgrind package for kfreebsd. And saw this about the program: %valgrind: i386 amd64 powerpc # Needs ported (asm, arch knwldge) Can anyone say something about valgrind on kfreebsd?
The GNU/kFreeBSD uses the same kernel syscalls as plain FreeBSD. Plain FreeBSD variant is not supported by upstream, see http://valgrind.org/info/platforms.html I would say FreeBSD support is prerequisite for GNU/kFreeBSD support here. Petr
Date: November 25, 2006
From: Frans Pop <elendil@xxxxxxxxx>
We are ready to make the switch to 2.6.18 for Debian Installer. For most architectures the 2.6.18-6 (ABI -3) should now be available in unstable. Please update the kernel udebs for your architecture ASAP. Cheers, FJP
pgpjj6iVCkym9.pgp
Description: PGP signature
Date: November 25, 2006
From: martin <martin.gustafsson@xxxxxxxxxxxxx>
In-reply-to:
<1164405661.4938.6.camel@martin-laptop
>
References:
<1164405661.4938.6.camel@martin-laptop
>
I changed the setting for mouse to "/dev/psm0" and "auto". Now it works. Next thing. I am not allowed to start X as a user. I guess I can chmod some files, but suspect there is a proper way of giving user access to X. Martin
Date: November 24, 2006
From: martin <martin.gustafsson@xxxxxxxxxxxxx>
Hello again, I have encountered another trouble with my install. When I start X, xorg says the mouse protocol ExplorerPS/2 is not supported on this platform and dies. This is what I use in Debian/linux. If I switch to protocol Microsoft, everything else but the mouse works. Any suggestions what to do? Martin
Date: November 23, 2006
From: Herbert P Fortes Neto <h_p_f_n@xxxxxxxxxxxx>
Hi, I did'nt find valgrind package for kfreebsd. And saw this about the program: %valgrind: i386 amd64 powerpc # Needs ported (asm, arch knwldge) Can anyone say something about valgrind on kfreebsd? Thanks. [] -- Herbert Parentes Fortes Neto (hpfn) Linux user number 416100 Debian GNU/kFreeBSD (qemu) 0x9834F79E -- http://pgp.mit.edu/
pgpBSe2jnbeIw.pgp
Description: PGP signature
Date: November 22, 2006
From: Petr Salinger <Petr.Salinger@xxxxxxxxx>
In-reply-to:
<1164215786.4571.6.camel@localhost
>
References:
<1164215786.4571.6.camel@localhost
>
On Wed, 22 Nov 2006, martin wrote:
Hello, I've just installed debian/bsd and managed to get the network going after editing /etc/network/interfaces and /etc/init.d/networking restart. However, after an apt-get update/upgrade and reboot I can not get the network working again. If I for example ping a remote ftp-server I get the resonse: ping: sendto: No route to host I connect to the internet through a router and DSL-modem.
Please try to verify whether you have ifconfig and route binaries,
which package they are come from.
dpkg -S /sbin/ifconfig
dpkg -S /sbin/route
They used to be in freebsd-hackedutils, but now route should be
in net-tools, ifconfig should move soon.
You can also try to downgrade freebsd-hackedutils to some older version.
Hopefully you will find some in /var/cache/apt/archives/
Hope it helps
Petr
Date: November 22, 2006
From: martin <martin.gustafsson@xxxxxxxxxxxxx>
Hello, I've just installed debian/bsd and managed to get the network going after editing /etc/network/interfaces and /etc/init.d/networking restart. However, after an apt-get update/upgrade and reboot I can not get the network working again. If I for example ping a remote ftp-server I get the resonse: ping: sendto: No route to host I connect to the internet through a router and DSL-modem. Martin
Date: November 22, 2006
From: Lois Mcknight <jimvvmv@xxxxxxxxxx>
sexx passwordds. http://qpnn8ecjeri.com
Date: November 21, 2006
From: Herbert P Fortes Neto <h_p_f_n@xxxxxxxxxxxx>
In-reply-to:
<Pine.LNX.4.62.0611211406150.693@xxxxxxxxxxxxxxxx>
References:
<20061121094952.9df239fa.h_p_f_n@xxxxxxxxxxxx> <Pine.LNX.4.62.0611211406150.693@xxxxxxxxxxxxxxxx>
*On Tue, 21 Nov 2006 14:10:37 +0100 (CET) *Petr Salinger <Petr.Salinger@xxxxxxxxx> wrote: > > Can i disable this warning? > > WARNING: WITNESS option enabled, expect reduced performance. > > > This was not happeing on first boots. > > The kernel installed: > > kfreebsd-image-7.0-1-486 > > I would suggest to use kfreebsd-image-6-686 (or kfreebsd-image-6-486). > The kfreebsd-image-7.0-1-486 is only (old) snapshot of FREEBSD-CURRENT. > > Petr Great! :) Thanks!!! [] -- Herbert Parentes Fortes Neto (hpfn) Linux user number 416100 Debian GNU/kFreeBSD (qemu) 0x9834F79E -- http://pgp.mit.edu/
pgp6Oo2kLjnp4.pgp
Description: PGP signature
Date: November 21, 2006
From: Petr Salinger <Petr.Salinger@xxxxxxxxx>
In-reply-to:
<20061121094952.9df239fa.h_p_f_n@xxxxxxxxxxxx>
References:
<20061121094952.9df239fa.h_p_f_n@xxxxxxxxxxxx>
Can i disable this warning? WARNING: WITNESS option enabled, expect reduced performance.
This was not happeing on first boots. The kernel installed: kfreebsd-image-7.0-1-486
I would suggest to use kfreebsd-image-6-686 (or kfreebsd-image-6-486). The kfreebsd-image-7.0-1-486 is only (old) snapshot of FREEBSD-CURRENT. Petr
Date: November 21, 2006
From: Herbert P Fortes Neto <h_p_f_n@xxxxxxxxxxxx>
Hi, I installed kfreebsd to make some tests with packages from sid. I'm using it with qemu. Can i disable this warning? WARNING: WITNESS option enabled, expect reduced performance. I tried to disable it, editing a file in /boot but i got a promtp: GDB: no debug ports present KDB: debugger backend: ddb KDB: enter: Boot flags requested debug ... ... db> Than i say 'continue' and: WARNING: WITNESS option enabled,... This was not happeing on first boots. The kernel installed: kfreebsd-image-7.0-1-486 Thanks -- Herbert Parentes Fortes Neto (hpfn) Linux user number 416100 Debian GNU/kFreeBSD (qemu) 0x9834F79E -- http://pgp.mit.edu/
pgpb8i7SJOAk6.pgp
Description: PGP signature
Date: November 18, 2006
From: Debian testing watch <noreply@xxxxxxxxxxxxxxxxxxx>
FYI: The status of the kfreebsd-5 source package in Debian's testing distribution has changed. Previous version: 5.4-19 Current version: 5.4-20 -- This email is automatically generated; henning@xxxxxxxxxxx is responsible. See http://people.debian.org/~henning/trille/ for more information.
Date: November 18, 2006
From: Petr Salinger <Petr.Salinger@xxxxxxxxx>
In-reply-to:
<200611181440.06606.kouk@xxxxxxxxxx>
References:
<200611181325.37214.kouk@xxxxxxxxxx> <Pine.LNX.4.62.0611181300340.20124@xxxxxxxxxxxxxxxx> <200611181440.06606.kouk@xxxxxxxxxx>
Look at r1727 on http://svn.debian.org/wsvn/glibc-bsd/?op=log&rev=0&sc=0&isdir=1I see. Well I suppose we should be doing different things then, maybe I'll focus on the packages with no bug in BTS. Btw darkice's build-deps need the same fix for kfreebsd-amd64 and hurd-i386 as it did for kfreebsd-i386. Should I reopen the bug and add this information?
No, please open new one, with text (mainly subject) like in #361455 - #361495. It allows me to exclude kfreebsd-amd64 only bugs during update of NOTES.BTW, please use severity important for bugs with ***tested*** patches/updated dependencies. There is higher probability
they will not be overlooked.
Thanks for your help.
Petr
Date: November 18, 2006
From: Konstantinos Koukopoulos <kouk@xxxxxxxxxx>
In-reply-to:
<Pine.LNX.4.62.0611181300340.20124@xxxxxxxxxxxxxxxx>
References:
<200611181325.37214.kouk@xxxxxxxxxx> <Pine.LNX.4.62.0611181300340.20124@xxxxxxxxxxxxxxxx>
On Sat 18 Nov 2006 14:07, Petr Salinger wrote: > Hi. > > > While going through some of the packages in NOTES [1] I noticed that the > > darkice package is FTBFS again after being claimed fixed. It used to be > > FTBFS because of bad build-deps but now it is something different: > > from the build log [2]: > > It looks like we are currently doing the same thing :-( > > Look at r1727 on > http://svn.debian.org/wsvn/glibc-bsd/?op=log&rev=0&sc=0&isdir=1 I see. Well I suppose we should be doing different things then, maybe I'll focus on the packages with no bug in BTS. Btw darkice's build-deps need the same fix for kfreebsd-amd64 and hurd-i386 as it did for kfreebsd-i386. Should I reopen the bug and add this information? Kostas Koukopoulos
Date: November 18, 2006
From: Petr Salinger <Petr.Salinger@xxxxxxxxx>
In-reply-to:
<200611181325.37214.kouk@xxxxxxxxxx>
References:
<200611181325.37214.kouk@xxxxxxxxxx>
Hi.
While going through some of the packages in NOTES [1] I noticed that the darkice package is FTBFS again after being claimed fixed. It used to be FTBFS because of bad build-deps but now it is something different: from the build log [2]:
It looks like we are currently doing the same thing :-( Look at r1727 on http://svn.debian.org/wsvn/glibc-bsd/?op=log&rev=0&sc=0&isdir=1 My working copy of "claimed fixed" is currently: allegro4.1_4.1.15-6+kbsd BTS darkice_0.16-1+kbsd kfreebsd-kernel-headers dictd_1.10.2-3+cfg fixed, should not be in unreleased gamin_0.1.7-3+kbsd BTS glew_1.3.4-3+kbsd BTS gnome-applets_2.10.1-5+kbsd gst-plugins-base0.10_0.10.10-1+kbsd fixed with new cdparanoia gtk-engines_0.12-8.1+libtool kaquarium_1.0-beta-5+libtool+b1 BTS kde-style-lipstik_2.2.1-1+libtool kdeedu_3.5.1-1+kbsd libapache-mod-encoding_0.0.20021209-6.1+libtool BTS libgtkhtml2_2.6.3-1+libtool+b1 fixed libibtk_0.0.14-10+libtool BTS ocamlgsl_0.3.5-3+kbsd pyopengl_2.0.1.09-1.1+kbsd realtimebattle_1.0.6-2+cfg ? showimg_0.9.4.1-3+libtool+b1 ? build-dep koffice-dev sidplay_2.0.9-2+kbsd+b1 BTS, pending solfege_3.0.2-1+kbsd fixed tktable_2.9-1+kbsd fixed in tktable2.9, tktable scheduled for removal totem_1.4.5-1+kbsd BTS, pending xdb_1.2.0-7.libtool.1 BTS BTS = an updated fix is again in BTS fixed = it is really fixed, needs "just" rebuild Petr
Date: November 18, 2006
From: Konstantinos Koukopoulos <kouk@xxxxxxxxxx>
Hello all, While going through some of the packages in NOTES [1] I noticed that the darkice package is FTBFS again after being claimed fixed. It used to be FTBFS because of bad build-deps but now it is something different: from the build log [2]: g++ -DHAVE_CONFIG_H -I. -I. -I. -O2 -pedantic -Wall -g -Wall -O2 -c -o OssDspSource.o `test -f 'OssDspSource.cpp' || echo './'`OssDspSource.cpp /usr/include/sys/ioctl.h:42: error: declaration of 'int ioctl(int, long unsigned int, ...) throw ()' throws different exceptions /usr/include/sys/ioccom.h:66: error: from previous declaration 'int ioctl(int, long unsigned int, ...)' make[3]: *** [OssDspSource.o] Error 1 <sys/ioctl.h>, which belongs to glibc, includes <bits/ioctls.h> which in turn includes <sys/ioccom.h> belonging to kfreebsd-kernel-headers. It seems that these two header files are in conflict. Any ideas why? [1] http://glibc-bsd.alioth.debian.org/NOTES [2] http://experimental.ftbfs.de/fetch.php?&pkg=darkice&ver=0.17.1-3&arch=kfreebsd-i386&stamp=1162652787&file=log&as=raw
Date: November 17, 2006
From: "easily organize" <rqvgjvcuzp@xxxxxxxx>
7655881 1318872 358156 3 8600103 2550384 5 3 3 2 4 0 8 8 2 7 5 7 8 0 6 0 0 1 0 4 7 6 2 4 7 678580 6 5 0 7 7228174 0 6 0 1 3 533726632 5 4 3 3 2 6 3 2 4 6 7 600 4 0 1 8 7 7787604 3 3 1 6 374 2646784 3261407
Date: November 17, 2006
From: "poetry" <lfwihrdfr@xxxxxxxxxxxx>
5227553 8123821 414236 0 5273545 8675565 3 7 5 5 7 7 5 7 1 7 6 4 6 7 0 3 5 7 2 7 7 2 3 1 5 704544 1 7 7 3 1715616 5 0 0 0 8 823506216 0 5 0 3 8 6 3 5 8 6 1 864 5 3 6 1 8 3800132 8 2 3 8 230 4633246 8400105
Date: November 15, 2006
From: Konstantinos Koukopoulos <kouk@xxxxxxxxxx>
In-reply-to:
<20061115120344.GA27249@xxxxxxxxxxxxxxxx>
References:
<52888.195.134.100.30.1163503022.squirrel@xxxxxxxxxxxxxx> <Pine.LNX.4.62.0611141404350.1361@xxxxxxxxxxxxxxxx> <20061115120344.GA27249@xxxxxxxxxxxxxxxx>
On Wed 15 Nov 2006 14:03, Guillem Jover wrote: > On Tue, 2006-11-14 at 14:21:03 +0100, Petr Salinger wrote: > > > Attached is an updated version of the patch for 3.5.5-2. It follows the > > > advice in PORTING [3] about using wildcards like 'linux-any' in > > > build-depends. > > > > Unfortunately, the support for linux-any is currently only in dpkg :-( > > The "WARNING: please note that this functionality is still not supported > > by debhelper" is still valid, > > debhelper has support for few months now: > > debhelper (5.0.36) unstable; urgency=low > [...] > * Patch from Guillem Jover to make --same-arch handling code support > the new form of architecture wildcarding which allows use of things > like "linux-any" and "any-i386" in the Architecture field. Closes: > #371082 [...] > -- Joey Hess <joeyh@xxxxxxxxxx> Fri, 9 Jun 2006 14:57:19 -0400 > > But sbuild and other tools do not, so it's not going to work for now. OK, so tommorow I'll file the patches with the build-depends that Aurelien suggested in his previous message. Thanks for the replies, Best regards, Kostas Koukopoulos
Date: November 15, 2006
From: "Ron" <RonHearn@xxxxxxx>
Requested material regarding our Knowledge Based Degree Program (KBDP)
In order to receive either a BA, BS, BS-MBA from our school we require:
1. Comprehension in the degree of interest.
Or
2. Experience within the workplace related to the degree of interest.
By calling one of our school counselors we can further answer more questions
and qualify you over the phone.
Daytime/Evening Number: 1-773-509-4920
Hope we have answered any questions you may have had;
Ron Hearn
Academic Resource Center
Theodosius School of Knowledge
Date: November 15, 2006
From: Guillem Jover <guillem@xxxxxxxxxx>
In-reply-to:
<Pine.LNX.4.62.0611141404350.1361@xxxxxxxxxxxxxxxx>
References:
<52888.195.134.100.30.1163503022.squirrel@xxxxxxxxxxxxxx> <Pine.LNX.4.62.0611141404350.1361@xxxxxxxxxxxxxxxx>
On Tue, 2006-11-14 at 14:21:03 +0100, Petr Salinger wrote:
> > Attached is an updated version of the patch for 3.5.5-2. It follows the
> > advice in PORTING [3] about using wildcards like 'linux-any' in
> > build-depends.
>
> Unfortunately, the support for linux-any is currently only in dpkg :-(
> The "WARNING: please note that this functionality is still not supported
> by debhelper" is still valid,
debhelper has support for few months now:
debhelper (5.0.36) unstable; urgency=low
[...]
* Patch from Guillem Jover to make --same-arch handling code support
the new form of architecture wildcarding which allows use of things
like "linux-any" and "any-i386" in the Architecture field. Closes: #371082
[...]
-- Joey Hess <joeyh@xxxxxxxxxx> Fri, 9 Jun 2006 14:57:19 -0400
But sbuild and other tools do not, so it's not going to work for now.
I should get my act together and finish this...
regards,
guillem
Date: November 15, 2006
From: provintech@xxxxxxxxxxxxxx
Your Service inquiry has been received.
We will answer you within 24 Hours.
For a faster assistance to your question(s),
you may call at.
Local (713)270-1712 or toll free 1(800)876-8902
Fax: (713) 270-6143
E mail info@xxxxxxxxxxxxxx
Thanks again!
Date: November 15, 2006
From: Sven Luther <sven.luther@xxxxxxxxxx>
In-reply-to:
<20061115001426.GA19311@xxxxxxxxxxxxx>
References:
<20061102131240.GA10951@xxxxxxxxxxxxx> <20061107170733.GA27942@xxxxxxxxxxxxx> <20061107190826.GD22273@aragorn
> <20061107191445.GA1921@xxxxxxxxxxxxx> <20061115001426.GA19311@xxxxxxxxxxxxx>
On Wed, Nov 15, 2006 at 12:14:27AM +0000, Colin Watson wrote: > On Tue, Nov 07, 2006 at 08:14:45PM +0100, Sven Luther wrote: > > On Tue, Nov 07, 2006 at 08:08:26PM +0100, Robert Millan wrote: > > > I'm sorry. Please feel free to disable the patch; I'm thinking it was > > > not a > > > good idea to apply it in the package before it was merged upstream (as it > > > was > > > about to, last time I visited this). > > > > > > Apologises for the hassle. > > > > No problem, i am happy we found it before the release though. > > > > Will you be able to work out a better/cleaner patch ? And work with us to > > merge it upstream ? > > I filed a bug with the correct fix for this problem two months ago: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386973 > > I highly recommend applying that instead. He, nice. I will test this one, and see if it doesn't cause the breakage. Friendly, Sven Luther
Date: November 15, 2006
From: Colin Watson <cjwatson@xxxxxxxxxx>
In-reply-to:
<20061107191445.GA1921@xxxxxxxxxxxxx>
References:
<20061102131240.GA10951@xxxxxxxxxxxxx> <20061107170733.GA27942@xxxxxxxxxxxxx> <20061107190826.GD22273@aragorn
> <20061107191445.GA1921@xxxxxxxxxxxxx>
On Tue, Nov 07, 2006 at 08:14:45PM +0100, Sven Luther wrote: > On Tue, Nov 07, 2006 at 08:08:26PM +0100, Robert Millan wrote: > > I'm sorry. Please feel free to disable the patch; I'm thinking it was not a > > good idea to apply it in the package before it was merged upstream (as it > > was > > about to, last time I visited this). > > > > Apologises for the hassle. > > No problem, i am happy we found it before the release though. > > Will you be able to work out a better/cleaner patch ? And work with us to > merge it upstream ? I filed a bug with the correct fix for this problem two months ago: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386973 I highly recommend applying that instead. Cheers, -- Colin Watson [cjwatson@xxxxxxxxxx]
Date: November 14, 2006
From: Aurelien Jarno <aurelien@xxxxxxxxxxx>
In-reply-to:
<52888.195.134.100.30.1163503022.squirrel@xxxxxxxxxxxxxx>
References:
<52888.195.134.100.30.1163503022.squirrel@xxxxxxxxxxxxxx>
Konstantinos Koukopoulos a écrit : > Hello, > > I noticed that the kdenetwork in unstable (3.5.5-2) is not building [1] > because it build-depends on the linux-specific package libiw-dev. The > patch that is online in the patches directory [2] corrects this and some > other things but is outdated (it's for kdenetwork-3.4.2 while > kdenetwork-3.5.1 has been built for kfreebsd). Nothing has been filed in > BTS as far as I can tell and in kdenetwork-3.5.5 the same issues exist > (bad build-depends and architecture in debian/control as well as an > incorrect arch check in a header). > Most of the time the reason why it has not been done is a lack of manpower. Thanks for your help. Aurelien -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian developer | Electrical Engineer `. `' aurel32@xxxxxxxxxx | aurelien@xxxxxxxxxxx `- people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to debian-bsd-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
Date: November 14, 2006
From: Petr Salinger <Petr.Salinger@xxxxxxxxx>
In-reply-to:
<52888.195.134.100.30.1163503022.squirrel@xxxxxxxxxxxxxx>
References:
<52888.195.134.100.30.1163503022.squirrel@xxxxxxxxxxxxxx>
Attached is an updated version of the patch for 3.5.5-2. It follows the advice in PORTING [3] about using wildcards like 'linux-any' in build-depends.
Unfortunately, the support for linux-any is currently only in dpkg :-(The "WARNING: please note that this functionality is still not supported by debhelper" is still valid, so please use rather
Architecture: i386 ia64 alpha amd64 arm hppa m32r m68k mips mipsel powerpc ppc64 s390 s390x sh3 sh3eb sh4 sh4eb sparc libiw-dev [!hurd-i386 !kfreebsd-i386 !kfreebsd-amd64]
I will also file a bug against kdenetwork including this patch
There a few packages in unreleased without submit in BTS, see http://glibc-bsd.alioth.debian.org/NOTES. Please, after filling bug(s), add also kfreebsd tag by mail to "request@xxxxxxxxxxxxxxx" with body like user glibc-bsd-devel@xxxxxxxxxxxxxxxxxxxxxxx usertag 341837 + kfreebsd usertag 341629 + kfreebsd Thanks Petr
Date: November 14, 2006
From: "Konstantinos Koukopoulos" <kouk@xxxxxxxxxx>
In-reply-to:
<52888.195.134.100.30.1163503022.squirrel@xxxxxxxxxxxxxx>
References:
<52888.195.134.100.30.1163503022.squirrel@xxxxxxxxxxxxxx>
Kostas Koukopoulos wrote: > Hello, > > I noticed that the kdenetwork in unstable (3.5.5-2) is not building [1] > because it build-depends on the linux-specific package libiw-dev. The > patch that is online in the patches directory [2] corrects this and some > other things but is outdated (it's for kdenetwork-3.4.2 while > kdenetwork-3.5.1 has been built for kfreebsd). Nothing has been filed in > BTS as far as I can tell and in kdenetwork-3.5.5 the same issues exist > (bad build-depends and architecture in debian/control as well as an > incorrect arch check in a header). the same goes for kdepim (which depends on libbluetooth-dev). -- To UNSUBSCRIBE, email to debian-bsd-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
Date: November 14, 2006
From: "Konstantinos Koukopoulos" <kouk@xxxxxxxxxx>
Hello, I noticed that the kdenetwork in unstable (3.5.5-2) is not building [1] because it build-depends on the linux-specific package libiw-dev. The patch that is online in the patches directory [2] corrects this and some other things but is outdated (it's for kdenetwork-3.4.2 while kdenetwork-3.5.1 has been built for kfreebsd). Nothing has been filed in BTS as far as I can tell and in kdenetwork-3.5.5 the same issues exist (bad build-depends and architecture in debian/control as well as an incorrect arch check in a header). Attached is an updated version of the patch for 3.5.5-2. It follows the advice in PORTING [3] about using wildcards like 'linux-any' in build-depends. I will also file a bug against kdenetwork including this patch, unless there is a reason that I am unaware of. Regards, Kostas Koukopoulos [1] http://experimental.ftbfs.de/fetch.php?&pkg=kdenetwork&ver=4%3A3.5.5-2&arch=kfreebsd-i386&stamp=1162628884&file=log&as=raw [2] http://glibc-bsd.alioth.debian.org/patches/kdenetwork.diff [3] http://glibc-bsd.alioth.debian.org/porting/PORTING
kdenetwork.diff
Description: Text Data
Date: November 08, 2006
From: Robert Millan <rmh@xxxxxxxxxxx>
In-reply-to:
<20061108072628.GA2466@xxxxxxxxxxxxx>
References:
<20061102131240.GA10951@xxxxxxxxxxxxx> <20061107170733.GA27942@xxxxxxxxxxxxx> <20061107190826.GD22273@aragorn
> <20061107191445.GA1921@xxxxxxxxxxxxx> <20061108064835.GA7742@aragorn
> <20061108072628.GA2466@xxxxxxxxxxxxx>
On Wed, Nov 08, 2006 at 08:26:29AM +0100, Sven Luther wrote: > On Wed, Nov 08, 2006 at 07:48:35AM +0100, Robert Millan wrote: > > On Tue, Nov 07, 2006 at 08:14:45PM +0100, Sven Luther wrote: > > > On Tue, Nov 07, 2006 at 08:08:26PM +0100, Robert Millan wrote: > > > > > > > > I'm sorry. Please feel free to disable the patch; I'm thinking it was > > > > not a > > > > good idea to apply it in the package before it was merged upstream (as > > > > it was > > > > about to, last time I visited this). > > > > > > > > Apologises for the hassle. > > > > > > No problem, i am happy we found it before the release though. > > > > > > Will you be able to work out a better/cleaner patch ? And work with us to > > > merge it upstream ? > > > > The patch isn't mine; I grabbed it from upstream while it was in the > > process of > > being merged. Its author was already working with upstream for a merge at > > that > > time, and I sent him my input to ensure the patch works on GNU/kFreeBSD as > > well > > as FreeBSD. > > Who is upstream about this ? Viktor Vasilev <viktor.vasilev@xxxxxxxxxxxxxxxxxxxx> (for details check #363381). -- Robert Millan My spam trap is honeypot@xxxxxxxxxxxx Note: this address is only intended for spam harvesters. Writing to it will get you added to my black list.
Date: November 08, 2006
From: Sven Luther <sven.luther@xxxxxxxxxx>
In-reply-to:
<20061108064835.GA7742@aragorn
>
References:
<20061102131240.GA10951@xxxxxxxxxxxxx> <20061107170733.GA27942@xxxxxxxxxxxxx> <20061107190826.GD22273@aragorn
> <20061107191445.GA1921@xxxxxxxxxxxxx> <20061108064835.GA7742@aragorn
>
On Wed, Nov 08, 2006 at 07:48:35AM +0100, Robert Millan wrote: > On Tue, Nov 07, 2006 at 08:14:45PM +0100, Sven Luther wrote: > > On Tue, Nov 07, 2006 at 08:08:26PM +0100, Robert Millan wrote: > > > > > > I'm sorry. Please feel free to disable the patch; I'm thinking it was > > > not a > > > good idea to apply it in the package before it was merged upstream (as it > > > was > > > about to, last time I visited this). > > > > > > Apologises for the hassle. > > > > No problem, i am happy we found it before the release though. > > > > Will you be able to work out a better/cleaner patch ? And work with us to > > merge it upstream ? > > The patch isn't mine; I grabbed it from upstream while it was in the process > of > being merged. Its author was already working with upstream for a merge at > that > time, and I sent him my input to ensure the patch works on GNU/kFreeBSD as > well > as FreeBSD. Who is upstream about this ? > For the debian side, I think it's safer to pull it from upstream when it's > time > to. I don't want to risk having further problems. Well, i reviewed and applied the freebsd only part of it, which seems pretty safe, and it was in debian since may anyway, so ... Upload will go to unstable today. Friendly, Sven Luther
Date: November 08, 2006
From: Robert Millan <rmh@xxxxxxxxxxx>
In-reply-to:
<87velrxdee.fsf_-_@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
References:
<20061102131240.GA10951@xxxxxxxxxxxxx> <20061107170733.GA27942@xxxxxxxxxxxxx> <20061107190826.GD22273@aragorn
> <20061107191445.GA1921@xxxxxxxxxxxxx> <87velrxdee.fsf_-_@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
On Tue, Nov 07, 2006 at 05:30:49PM -0200, Otavio Salvador wrote: > [ I've dropped the non-related mail addresses from the CC line ] > > Sven Luther <sven.luther@xxxxxxxxxx> writes: > > > On Tue, Nov 07, 2006 at 08:08:26PM +0100, Robert Millan wrote: > >> > >> I'm sorry. Please feel free to disable the patch; I'm thinking it was not > >> a > >> good idea to apply it in the package before it was merged upstream (as it > >> was > >> about to, last time I visited this). > >> > >> Apologises for the hassle. > > > > No problem, i am happy we found it before the release though. > > > > Will you be able to work out a better/cleaner patch ? And work with us to > > merge it upstream ? > > Robert and Sven, > > I would like to start a separated branch for it on darcs (parted is > moving to darcs just after 1.8 release but we already have the > repository available for hacking on the 2.0 basis) and then make it > available on upstream version on 2.0 or even on 1.8.x release > depending how deeply are the changes. > > Robert, would you mind if I provide you the repository for us start to > work on that? Hi Otavio, Quoting myself (from the mail I sent 1 min ago): > The patch isn't mine; I grabbed it from upstream while it was in the process > of > being merged. Its author was already working with upstream for a merge at > that > time, and I sent him my input to ensure the patch works on GNU/kFreeBSD as > well > as FreeBSD. > > For the debian side, I think it's safer to pull it from upstream when it's > time > to. I don't want to risk having further problems. -- Robert Millan My spam trap is honeypot@xxxxxxxxxxxx Note: this address is only intended for spam harvesters. Writing to it will get you added to my black list.
Date: November 08, 2006
From: Robert Millan <rmh@xxxxxxxxxxx>
In-reply-to:
<20061107191445.GA1921@xxxxxxxxxxxxx>
References:
<20061102131240.GA10951@xxxxxxxxxxxxx> <20061107170733.GA27942@xxxxxxxxxxxxx> <20061107190826.GD22273@aragorn
> <20061107191445.GA1921@xxxxxxxxxxxxx>
On Tue, Nov 07, 2006 at 08:14:45PM +0100, Sven Luther wrote: > On Tue, Nov 07, 2006 at 08:08:26PM +0100, Robert Millan wrote: > > > > I'm sorry. Please feel free to disable the patch; I'm thinking it was not a > > good idea to apply it in the package before it was merged upstream (as it > > was > > about to, last time I visited this). > > > > Apologises for the hassle. > > No problem, i am happy we found it before the release though. > > Will you be able to work out a better/cleaner patch ? And work with us to > merge it upstream ? The patch isn't mine; I grabbed it from upstream while it was in the process of being merged. Its author was already working with upstream for a merge at that time, and I sent him my input to ensure the patch works on GNU/kFreeBSD as well as FreeBSD. For the debian side, I think it's safer to pull it from upstream when it's time to. I don't want to risk having further problems. -- Robert Millan My spam trap is honeypot@xxxxxxxxxxxx Note: this address is only intended for spam harvesters. Writing to it will get you added to my black list.
Date: November 08, 2006
From: Williams Chester <winningclaimsdept@xxxxxxxxxxx>
Hurray!!!
2006 WINNING NOTICE
FROM: THELOTTERY COORDINATOR,
INTERNATIONAL PROMOTIONS/PRIZE AWARD DEPARTMENT
Dear Recipient,
RESULTS FOR SEPTEMBER 2006 CATEGORY "A" DRAWS
Congratulations to you as we bring to your notice, the results of The Category
"A" draws of TRIPPLE WINS INTERNATIONAL GAMES.
We are happy to inform you that you have emerged a winner under the SEPTEMBER
JUNE LUCKY DRAWS First Category, which is part of our promotional draws.
The draws were held prior to your notification.
Participants were selected through a computer ballot system drawn from
4,000,000names/email addresses of individuals and companies from Africa,
America, Asia, Australia, Canada, Europe, Middle East, and New Zealand as part
of our International Promotions Program.
You/Your Company, attached to ticket number IL252/03/78 with serial number
IL25278NL drew the lucky numbers 10, 11, 19,20,23,1 (6), and consequently won
in the Category "A. You have therefore been awarded a lump sum pay out Fifteen
Million Euros (15,000,000.00) in cash, which is the winning payout for Category
“winners.
CONGRATULATIONS!
Please contact the claims agent email address below as soon as possible for the
processing of your prize money. For due processing and remittance of your prize
money to a designated account of your choice.
NOTE: For easy reference and identification find below your reference numbers.
Note that you are to forward this email to the Mrs. Cherry Rings
(Claims Agent) for your prize claim processing.
REFERENCE NUMBER: JU/03/357856256/NL
Congratulations once again from all our staff and
Thank you for being part of our promotions program.
Sincerely,
Williams Chester
UKLOTTERY PROMOTION
FINANCIAL UNIT DIRECTOR/CONTROLLER
FIRST SECURITIES AND TRIPPLE WINS INTERNATIONAL GAMES,
UNITED KINGDOM BEDFORD HILL,
BALLAM SW 12
ENGLAND.
Claims Agent Contact
Mrs. Cherry Rings
CONTACT EMAIL ADDRESS: winningclaimsdept@xxxxxxxxxxx
Phone number: +44-702-408-3788
N.B.ANY BREACH OF CONFIDENTIALITY ON THE PART OF THE
WINNERS WILL RESULT TO DISQUALIFICATION. PLEASE DO NOT REPLY TO THIS MAIL BOX,
YOU ARE TO CONTACT YOURS CLAIMS AGENT FOR FURTHER PRIZE CLAIM
PROCEDURE.
--
To UNSUBSCRIBE, email to debian-bsd-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
Date: November 07, 2006
From: Otavio Salvador <otavio@xxxxxxxxxx>
In-reply-to:
<20061107191445.GA1921@xxxxxxxxxxxxx> (Sven Luther's message of "Tue, 7 Nov 2006 20:14:45 +0100")
References:
<20061102131240.GA10951@xxxxxxxxxxxxx> <20061107170733.GA27942@xxxxxxxxxxxxx> <20061107190826.GD22273@aragorn
> <20061107191445.GA1921@xxxxxxxxxxxxx>
[ I've dropped the non-related mail addresses from the CC line ]
Sven Luther <sven.luther@xxxxxxxxxx> writes:
> On Tue, Nov 07, 2006 at 08:08:26PM +0100, Robert Millan wrote:
>>
>> I'm sorry. Please feel free to disable the patch; I'm thinking it was not a
>> good idea to apply it in the package before it was merged upstream (as it was
>> about to, last time I visited this).
>>
>> Apologises for the hassle.
>
> No problem, i am happy we found it before the release though.
>
> Will you be able to work out a better/cleaner patch ? And work with us to
> merge it upstream ?
Robert and Sven,
I would like to start a separated branch for it on darcs (parted is
moving to darcs just after 1.8 release but we already have the
repository available for hacking on the 2.0 basis) and then make it
available on upstream version on 2.0 or even on 1.8.x release
depending how deeply are the changes.
Robert, would you mind if I provide you the repository for us start to
work on that?
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: otavio@xxxxxxxxxx UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://www.freedom.ind.br/otavio
---------------------------------------------
"Microsoft gives you Windows ... Linux gives
you the whole house."
Date: November 07, 2006
From: Sven Luther <sven.luther@xxxxxxxxxx>
In-reply-to:
<20061107190826.GD22273@aragorn
>
References:
<20061102131240.GA10951@xxxxxxxxxxxxx> <20061107170733.GA27942@xxxxxxxxxxxxx> <20061107190826.GD22273@aragorn
>
On Tue, Nov 07, 2006 at 08:08:26PM +0100, Robert Millan wrote: > > I'm sorry. Please feel free to disable the patch; I'm thinking it was not a > good idea to apply it in the package before it was merged upstream (as it was > about to, last time I visited this). > > Apologises for the hassle. No problem, i am happy we found it before the release though. Will you be able to work out a better/cleaner patch ? And work with us to merge it upstream ? Friendly, Sven Luther
Date: November 07, 2006
From: Robert Millan <rmh@xxxxxxxxxxx>
In-reply-to:
<20061107170733.GA27942@xxxxxxxxxxxxx>
References:
<20061102131240.GA10951@xxxxxxxxxxxxx> <20061107170733.GA27942@xxxxxxxxxxxxx>
I'm sorry. Please feel free to disable the patch; I'm thinking it was not a
good idea to apply it in the package before it was merged upstream (as it was
about to, last time I visited this).
Apologises for the hassle.
On Tue, Nov 07, 2006 at 06:07:34PM +0100, Sven Luther wrote:
> reopen 363381
> # kfreebsd support patch broke parted in a RC way.
> thanks
>
> Hi Robert, debian-release, debian-boot folk.
>
> The patch in 363381, and particularly this hunk :
>
> diff -urNad parted-1.7.0~/parted/table.c parted-1.7.0/parted/table.c
> --- parted-1.7.0~/parted/table.c 2006-05-19 03:54:01.000000000 -0300
> +++ parted-1.7.0/parted/table.c 2006-05-19 03:54:36.000000000 -0300
> @@ -197,7 +215,11 @@
> len += wcslen(COLSUFFIX);
>
> newsize = (wcslen(*s) + len + 1) * sizeof(wchar_t);
> + oldsize = (wcslen(*s) + 1) * sizeof(wchar_t);
> +
> + temps = *s;
> *s = realloc (*s, newsize);
> + memcpy(*s, temps, oldsize);
>
> for (i = 0; i < ncols; ++i)
> {
>
> Caused the bug in #392767: [mac] parted is unable to reread partition tables
> created by d-i/partman, which was visible on s390 and x86 also accordying to
> Bastian Blank, and thus caused parted to randomly not show the partition table
> on a print command, thus breaking the lvm/raid support, which used
> command-line parted in order to detect lvm/raid partitions.
>
> The problem seems related to the ENABLE_NLS case, and the use of wide-chars,
> which the memcpy trick failed to copy over properly, leaving garbage in the
> string to be outputed.
>
> I remember (but am not anymore 100% sure, so a reply from frans/joeyh would
> be nice), that frans told me last week or so, that an upload of parted was ok
> with regard to d-i RC1, since parted is not in the image, and not migrated to
> testing, but i would like confirmation on this, and also advice from the
> debian-release folk, thus posting here.
>
> I propose to upload parted 1.7.1-3, which includes the two following changes :
>
> parted (1.7.1-3) unstable; urgency=low
>
> * parted-print-name.dpatch : Fix bug in parted print, when there are no
> extended partitions, but partition names.
> * disabled kfreebsd-gnu.dpatch, which added kfreebsd support, because the
> the patch caused parted to have trouble in a d-i environment to print
> the
> partition table, thus causing tools relying on parted -s print to find
> information about the partition table to break, like the one checking
> for
> RAID partitions in d-i. (Closes: #392767)
>
> -- Sven Luther <luther@xxxxxxxxxx> Tue, 7 Nov 2006 17:45:28 +0100
>
> #392767 being one of the two parted related RC bugs still open, but the other
> patch is also nice to have, since it allows to have partitions actually named
> something else than primary, which may (or not) break some tools also.
>
> Robert, we will upload a parted version without kfreebsd support, but it would
> be nice if you could revisit the patch, and clean up this problem. Maybe
> documenting the hacks like the one above a bit better, and/or adding *BSD
> specific #ifdefs to limit this kind of problems would be nice.
>
> Special thanks go to Bastian Blank, who helped me in the last step of
> investigating this issue, and finding the responsible patch.
>
> Friendly,
>
> Sven Luther
>
--
Robert Millan
My spam trap is honeypot@xxxxxxxxxxxx Note: this address is only intended for
spam harvesters. Writing to it will get you added to my black list.
Date: November 07, 2006
From: Debian Installer <installer@xxxxxxxxxxxxxxxxxxxxx>
Accepted: kfreebsd-5_5.4-20.diff.gz to pool/main/k/kfreebsd-5/kfreebsd-5_5.4-20.diff.gz kfreebsd-5_5.4-20.dsc to pool/main/k/kfreebsd-5/kfreebsd-5_5.4-20.dsc kfreebsd-source-5.4_5.4-20_all.deb to pool/main/k/kfreebsd-5/kfreebsd-source-5.4_5.4-20_all.deb Override entries for your package: kfreebsd-5_5.4-20.dsc - source devel kfreebsd-source-5.4_5.4-20_all.deb - optional devel Announcing to debian-devel-changes@xxxxxxxxxxxxxxxx Thank you for your contribution to Debian.
Date: November 07, 2006
From: Archive Administrator <dak@xxxxxxxxxxxxxxxxxxxxx>
kfreebsd-5_5.4-20_amd64.changes uploaded successfully to localhost
along with the files:
kfreebsd-5_5.4-20.dsc
kfreebsd-5_5.4-20.diff.gz
kfreebsd-source-5.4_5.4-20_all.deb
Greetings,
Your Debian queue daemon
Date: November 05, 2006
From: Joshua Cummings <jrac@xxxxxx>
In-reply-to:
<20061104215046.55141.qmail@xxxxxxxxxxxxxxxxxxxxxxx>
References:
<20061104215046.55141.qmail@xxxxxxxxxxxxxxxxxxxxxxx>
On Sat, 2006-11-04 at 13:50 -0800, Hannu Virtanen wrote: > 1) > What is the proper way to get > the Net working? > You can simply edit the /etc/network/interfaces file and run /etc/init.d/networking restart. Just remember kFreeBSD uses a different interface name for different drivers/cards. Be sure to replace the existing one with yours. A quick ifconfig -a should help you find the name. > 2) > What is the package I would need to > get 'dselect' command (for installing > packages) working? > IIRC dselect should be installed by default, but if not, apt-get install dselect should work. > > 3) > Where can I find instructions > for general configuring > debian-bsd? Not sure exactly what you're after, but configuring the basics of a Debian GNU/kFreeBSD system is almost the same as a Debian GNU/Linux system, as long as you're not dealing with anything FreeBSD specific. My GNU/kFreeBSD box has been out of action for a while, so this is all from memory, but hopefully I'm not too rusty to forget the basics. ;) -- Joshua
Date: November 04, 2006
From: Hannu Virtanen <hannu_markus_virtanen@xxxxxxxxx>
In-reply-to:
<20061104091451.90127.qmail@xxxxxxxxxxxxxxxxxxxxxxx>
References:
<20061104091451.90127.qmail@xxxxxxxxxxxxxxxxxxxxxxx>
I tried to install debian-bsd on a hd
and using the same machine as used for debian/linux.
I could not boot it.
I tried several ways of installing
the boot loader,
first without doing anything for the boot loader
(there was the grub) and finally trying
to install BSD bootloader...
....
Date: November 04, 2006
From: Hannu Virtanen <hannu_markus_virtanen@xxxxxxxxx>
In-reply-to:
<Pine.LNX.4.62.0611031553380.7329@xxxxxxxxxxxxxxxx>
References:
<Pine.LNX.4.62.0611031553380.7329@xxxxxxxxxxxxxxxx>