Bug#642468: kfreebsd-8|9 does not provide any method to use non-free firmware blobs
Hi Petr, thanks for your howto! On Freitag, 23. September 2011, Petr Salinger wrote: > Here is the recipe for building own kernel with bce whats bce? cheers, Holger -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201109231532.38912.hol...@layer-acht.org
Bug#544758: FTBFS on Debian kfreebsd
package: olsrd severity: important User: debian-bsd@lists.debian.org Usertags: kfreebsd x-debbugs-cc: debian-bsd@lists.debian.org, olsr-...@lists.olsr.org Hi, filing this bug to track this somewhere else than in my inbox :) olsrd fails to build from source on kfreebsd-i386 and -amd64, see https://buildd.debian.org/fetch.cgi?pkg=olsrd;ver=0.5.6-r5-1;arch=kfreebsd-amd64;stamp=1249389872 https://buildd.debian.org/fetch.cgi?pkg=olsrd;ver=0.5.6-r5-1;arch=kfreebsd-i386;stamp=1249389730 (also scroll down to see the patches which are not enough ;) On Sonntag, 23. August 2009, Henning Rogge wrote: > Am Dienstag 18 August 2009 20:17:01 schrieb Henning Rogge: > > I will just download a Debian BSD image and install it in a virtual > > machine. ;) > Did not help, I don't get it running... There is now a debian-installer for Debian kfreebsd available, get it at http://temp.aurel32.net/d-i-kfreebsd/ Also see http://wiki.debian.org/Debian_GNU/kFreeBSD > If anyone from the debian side wants to work on this I would be happy to > support him. cool! regards, Holger Patches tried so far: diff -r 44dbc4c82b0b make/guess_os.sh --- a/make/guess_os.sh Sun Aug 16 18:26:04 2009 +0200 +++ b/make/guess_os.sh Mon Aug 17 19:33:30 2009 +0200 @@ -10,6 +10,7 @@ case "$arch" in linux) arch=linux ;; freebsd*) arch=fbsd ;; + gnu/kfreebsd*) arch=fbsd ;; netbsd*)arch=nbsd ;; openbsd*) arch=obsd ;; darwin*)arch=osx ;; --- a/make/Makefile.fbsdSun Aug 16 18:26:04 2009 +0200 +++ b/make/Makefile.fbsdTue Aug 18 11:14:18 2009 +0200 @@ -15,6 +15,7 @@ LIBS = CPPFLAGS +=-DOLSRD_GLOBAL_CONF_FILE=\"$(CFGFILE)\" +CPPFLAGS +=-D__FreeBSD__ ifdef NO_80211 CPPFLAGS +=-DFBSD_NO_80211=1 signature.asc Description: This is a digitally signed message part.
Re: Bug#629504: general: Error during compiling kernel module at generating file vnode_if.h.
reassign 629504 kfreebsd-source-8.1 thanks On Dienstag, 7. Juni 2011, Cimini Mario wrote: > Package: general > Severity: minor > > > Warning: Object directory not changed from original > /usr/src/kfreebsd-source-8.1/sys/fs/puffs/puffs awk -f > @/tools/vnode_if.awk @/kern/vnode_if.src -p > awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -q > awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -h > cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc > -I. -I@ -I@/contrib/altq -finline-limit=8000 --param > inline-unit-growth=100 --param large-function-growth=1000 -fno-common -g > -I/usr/src/kfreebsd-source-8.1/sys/fs/puffs/puffs > -I/usr/src/kfreebsd-source-8.1/sys/fs/puffs/puffs/../putter -DPUFFSDEBUG > -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 > -mno-sse3 -ffreestanding -std=iso9899:1999 -c puffs_msgif.c In file > included from @/sys/vnode.h:563, > from puffs_msgif.c:44: > ../vnode_if.h:13: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:22: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:33: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:44: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:59: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:70: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:85: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:97: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:114: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:125: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:140: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:152: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:169: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:182: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:201: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:213: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:230: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:242: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:259: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:271: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:288: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:299: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:314: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:325: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:340: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:349: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:360: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:372: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:389: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:401: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:418: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:432: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:453: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:465: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:482: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:492: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:505: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:515: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:528: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:539: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:554: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:565: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:580: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:591: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:606: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:620: error: expected ‘)’ before ‘WILLRELE’ > ../vnode_if.h:641: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:653: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:670: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:681: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:696: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:709: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:728: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:742: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:763: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:774: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:789: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:799: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:812: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:822: error: expected ‘)’ before ‘struct’ > ../vnode_if.h:835: error: expected specifier-qualifier-list before ‘IN’ > ../vnode_if.h:847: error: expected ‘)’ before ‘
Re: howto boot+preseed kfreebsd in qemu (was Re: netcfg: installation on kfreebsd maybe broken?
Hi Steve, On Freitag, 8. Februar 2013, Steven Chamberlain wrote: > I'd like to share a recipe that works for an extracted netboot.tar.gz: > > $ qemu-system-x86_64 -m 512 -enable-kvm -net nic -net > user,bootfile=grub2pxe,tftp=. -serial stdio -boot n -drive > if=ide,bus=0,file=/dev/sdX,cache=writeback -no-reboot thanks! with that I can surely make an installation work! > I usually remove the font.pf2 file (forcing GRUB to run in text-mode) > and patch the grub.cfg like the attached. This automatically starts a > pre-seeded install, and the d-i syslog gets conveniently redirected to > qemu's stdout. nice. though I'd actually prefer to boot the mini.iso unmodified and still get pre-seeding, is that somehow possible? > The preseed.cfg can probably be the same as a Linux one. If you specify > a partman-auto/disk it should probably be /dev/ada0 (first IDE whole > disk on kfreebsd-9) or /dev/ad0 (on kfreebsd-8). > > Here's one I've had some success with: > http://pyro.eu.org/f/x-Lru4G5SieJVqMaRj71vQ.cfg thanks! I've now finally booted d-i on debian kfreebsd once+twice \o/ ;-) > It can be adapted easily to boot a mini.iso instead, but then it is > harder to tweak the grub.cfg. can you show me how to do this? :-) cheers, Holger
Re: howto boot+preseed kfreebsd in qemu
Hi Steven, sorry, was busy with other stuff... On Samstag, 9. Februar 2013, Steven Chamberlain wrote: > You'd need to get past the GRUB menu firstly; it's configured never to > time out. Can Jenkins send keystrokes? (e.g. cursor down, enter) yes, I could do this with jenkins (with xdotool) but I do have to, after having looked at my options, I think I want to go for testing isos first, simply because I test other Debian installations from isos too. (And there's a iso for every type of d-i test I do, but not a netboot.tar.gz...) For that I will still have to patch the grub.cfg. > > can you show me how to do this? :-) > Well, I've managed it before by patching debian-installer.git's > build/boot/kfreebsd/grub-kfreebsd-cdrom.cfg file and rebuilding, but > maybe that's cheating? Otherwise some kind of loop mount and patching > grub.cfg in the ISO. (With the same changes as my previous patch). I'd like to mount the iso file, copy the files somewhere, patch them and mount from that "cd", I just don't know how to do this... basically my question is: how do I tell qemu to launch grub with that cfg? cheers, Holger
Re: Bug#710959: System intermittently hangs
control: reassign -1 src:kfreebsd-9 # probably not right but better than base thanks On Montag, 3. Juni 2013, Thomas Schweikle wrote: > Package: base > Severity: normal > > Dear Maintainer, > > -- System Information: > Debian Release: jessie/sid > APT prefers unstable > APT policy: (500, 'unstable'), (500, 'stable') > Architecture: kfreebsd-amd64 (x86_64) > > Kernel: kFreeBSD 8.3-1-amd64 > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > How to reproduce: > - Install Debian kfreebsd-amd64 into a VM (VMware, VirtualBox, KVM) > - Upgrade to "unstable" > - Restart the system > > The system will boot as expected, but logging in using ssh or directly on > console you will notice your keypresses not shown immediately. After some > time they will show up, again not showing, then showing again. None of the > keys you typed ist lost, but you are forced to wait for some seconds until > the system reacts on any of them. > > Unsure if this is something with screen output, interrupts, or kernel > related. Since I see it with any available kernel (kfreebsd-image-8.3-1, > kfreebsd-image-9.0-2) I suppose it to be some I/O-problem. I do not see it > with "stable"- or "testing"-releases. signature.asc Description: This is a digitally signed message part.
Re: Bits from the Release Team (Jessie freeze info)
Hi, On Mittwoch, 23. Oktober 2013, Stewart Smith wrote: > Jenkins can have slaves on remote hosts, via SSH. It runs a small java > app there, so as long as the arch has a JVM then you're pretty right. that JVM is not even needed, just schedule jobs via ssh and be done. cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: Bug#756464: upgrade-reports: [kfreebsd] dist-upgrade to jessie removes the kernel
reassign 756464 freebsd-net-tools thanks Hi Dan, thanks for your bug report, reassigning accordingly. cheers, Holger On Mittwoch, 30. Juli 2014, Dan Greene wrote: > Package: upgrade-reports > Severity: critical > Justification: breaks the whole system > > Dear Maintainer, > > When dist-upgrading a system to jessie, or running dist-upgrade on a > freshly installed system (using the alpha 1 release of the installer), > apt-get removes the kernel. This results in there being no kernel > installed, and you can't exactly boot the system without a kernel, hence > the severity. > > Using aptitude reveals that freebsd-net-tools Breaks: kfreebsd-image-9 > > To reproduce: > Install Debian GNU/kFreeBSD jessie from tha alpha 1 netinstall cd. > Run apt-get dist-upgrade > Reboot > > and you will be stuck with a grub prompt. > > In case it matters, this bug was found running under a virtual machine > (KVM). > > -- System Information: > Debian Release: jessie/sid > APT prefers testing-updates > APT policy: (500, 'testing-updates'), (500, 'testing') > Architecture: kfreebsd-amd64 (x86_64) > > Kernel: kFreeBSD 9.2-1-amd64 > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash signature.asc Description: This is a digitally signed message part.
Re: jenkins.d.n for kfreebsd, PXE boot, text-mode d-i
Hi Steven, On Montag, 1. September 2014, Steven Chamberlain wrote: > I've been looking for a way to automate kfreebsd d-i testing, but found > a solution that will also give Jenkins some test coverage of text-mode > d-i (whereas it only tests GUI installer at the moment I think?) and the > PXE boot images (instead of just CD ISOs). So it would be really nice > if we could enable this. Please let me know if this is possible. absolutly! I'm excited to see you working on getting bsd tests working on jenkins.d.n - and improving the d-i tests too! > I've attached, because I think it was clearer this way, diffs from > existing files to the new shellscript and preseed file I've created, that: actually, git branches would have been even better :-) Next time, please! ;) git branches and splitted commits will also allow me to take some bits of your work while asking you to polish some others. So you and me can both see progress too instead of endless discussions only :) regarding d-i-installation-pxe.sh per se: I agree d-i-installation.sh is a hack, but what you did is making the hack worse, by copying parts of it into a very similar script, instead of a.) enhancing the existing script to do what you need too or b.) splitting that script into two/three scripts by using functions properly. > * currently supports only GRUB2 (which is used for kfreebsd and hurd > only - the other PXE boot images are syslinux; should be able to add > support for that later) thats fine (given the above) - I'm just not sure I think its sensible to have PXE+CD jobs _now_. Once they are working I think its a good idea to add more and more tests, but as long as thats not the case it just eats ressources. > * currently supports only kfreebsd (the hurd PXE boot image for sid > doesn't boot at the moment anyway) fine as long as we dont create said jobs. > * given a netboot.tar.gz instead of an ISO file, extracts it in the > working directory > > * edits the grub.cfg - which is not that much of a hack, because it's > what a site sysadmin must do to define preseed parameters anyway > > * sends kernel messages and d-i syslog to the virtual serial port log > > * only needs a guest VM with 256 MiB memory to run, and 2 GiB disk thats rather a low mem and low disk scenario... > * doesn't need to run in sudo - I'm wondering why the script I based > this on, was doing that? the whole script isnt run with sudo, just single commands are. > * should (when we've fix the d-i bugs) test-boot the installed system, > but that's untested yet, and I also haven't implemented save_logs yet > (it would maybe need root privileges on the host to be able to mount the > UFS partition, e.g. `mount -o ro,loop,ufstype=44bsd,offset=$n`) using sudo to mount this is no problem > I could use some help to write the Jenkins jobfile; I don't have an > installation of Jenkins to try this on but have dry-run this script and > preseed file in isolation, they seem to work already. I think it be best if you could modify the existing debian kfreebsd jobs, instead of creating new ones. > Thanks! likewise :-) Feel free to come by on irc and/or open a bug against qa.debian.org so we can properly track this! cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: [Packaging] Bug#767102: munin-plugins-core: df* plugins report warnings for special filesystems on kFreeBSD
Hi Steven, On Mittwoch, 29. Oktober 2014, Steven Chamberlain wrote: > And I guess because /proc/mounts is trying to emulate Linux, it pretends > that /sys is sysfs - I guess some applications expect that: > http://svnweb.freebsd.org/base/releng/10.1/sys/compat/linprocfs/linprocfs.c > ?view=annotate&sortby=file#l365 > > But /proc/mounts still identifies /proc itself as linprocfs. If it > didn't, then it would be ambiguous and even more confusing. the best way to find out is to debug+fix the plugins, which is really easy: apt-get install munin munin-node while $problems ; do munin-run df vi /etc/munin/plugins/df done (Note that /etc/munin/plugins/df is a link to /usr so unless you replace the link with a copy your fixes will get overwritten on upgrades.) cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: [Pkg-anonymity-tools] Bug#768140: torsocks: FTBFS on kfreebsd-*
Hi, On Montag, 10. November 2014, intrigeri wrote: > [...] I'm sorry I can't > really give you folks more time, as the window to get fixes for > important bugs into Jessie closes early in December. not wanting to interfere with intrigeris plans (which I think are sensible!), but this doesn't really mean your hard deadline for fixing the FTBFS on kfreebsd is this friday. FTBFS on kfreebsd is still an important bug, so if there is a fix, there could still another upload for that fix before 5th of December. It's just less work for a few people if the patch would be ready this Friday :) And it's also more certain to get it in this friday than in another upload... cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: Plan B for kfreebsd
Hi Steven, On Montag, 10. November 2014, Steven Chamberlain wrote: > So - while I disagree with the release team's decision - being an > unofficial release doesn't have to be a bad thing for us. It actually > gives us freedom to make improvements as we see fit. And it could be a > lot of fun. I think that's probably the best way to see this, kudos! ;-) On Dienstag, 11. November 2014, Steven Chamberlain wrote: > * random/cool stuff: > - place to run c-i testing, QA tools I'm happy to continue to run kfreebsd related jobs on jenkins.d.n and also to add new jobs! likewise for piuparts.d.o, once that can cope with more than one arch... about https://jenkins.debian.net/view/g-i-installation/job/g-i- installation_debian_sid_daily_kfreebsd/ (and jessie and wheezy) - I guess I should remove the wheezy job - I will need to fix the missing preseed file - whats the status of kfreebsd d-i .iso? which should jenkins test? cheers, Holger, not subscribed to -bsd@l.d.o signature.asc Description: This is a digitally signed message part.
jenkins kfreebsd jobs (Re: Plan B for kfreebsd)
Hi, On Dienstag, 11. November 2014, Holger Levsen wrote: > about https://jenkins.debian.net/view/g-i-installation/job/g-i- > installation_debian_sid_daily_kfreebsd/ (and jessie and wheezy) > > - I will need to fix the missing preseed file done that, now it hangs like in https://jenkins.debian.net/view/g-i-installation/job/g-i- installation_debian_sid_daily_kfreebsd/428/console this is probably not the right way to boot the kfreebsd iso, which is it? + sudo qemu-system-x86_64 -display vnc=localhost:11 -enable-kvm -cpu host - cdrom /var/lib/jenkins/jobs/g-i- installation_debian_sid_daily_kfreebsd/workspace/debian-testing-kfreebsd- amd64-netinst.iso -boot d -drive file=/dev/jenkins01/debian_sid_daily_kfreebsd,index=0,media=disk,cache=unsafe -m 1024 -net nic,vlan=0 -net user,vlan=0,host=10.0.2.1,dhcpstart=10.0.2.2,dns=10.0.2.254 --append 'auto=true mirror/suite=sid priority=critical locale=en_US keymap=us url=http://10.0.2.1//d-i-preseed-cfgs/debian_sid_daily_kfreebsd_preseed.cfg video=vesa:ywrap,mtrr vga=788 -- quiet' > cheers, > Holger, not subscribed to -bsd@l.d.o signature.asc Description: This is a digitally signed message part.
Re: jenkins kfreebsd jobs (Re: Plan B for kfreebsd)
Hi Steven, On Dienstag, 11. November 2014, Steven Chamberlain wrote: > Thanks for your help with this. Automated d-i testing was > probably the first thing I wanted to do as we begin to put an > unofficial release together. yay! > To automatically boot an .iso, we'd need to edit the grub.cfg inside of > it somehow. > The easiest alternative - something I emailed to you a while ago but I > didn't really get finished right, I remembered this but was surprised to find no traces of that in bin/g- i-installation.sh in the jenins repo... > - is to extract a PXE netboot installer > tarball, edit the boot parameters in the grub.cfg, and TFTP boot it > (with Qemu's internal DHCP+TFTP sevices). That kinda resembles what a > large-scale deployment on real hardware might do. > > I'll look into one or both options later this evening and get back to > you, with a Git pull request ideally. cool! I've also decided to keep the wheezy job, I think it shold work and then it's a nice reference... > Thanks again, you/kfreebsd are/is much welcome! cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: jenkins kfreebsd jobs (Re: Plan B for kfreebsd)
Hi, On Dienstag, 11. November 2014, Steven Chamberlain wrote: > You gave me feedback but I didn't come back to you yet with the changes > you suggested... ah :) > I started over, amending the existing g-i-installation.sh instead of > trying to create a separate one; I've put it in a kfreebsd branch, > split into small commits, here: > https://git.steven.hosting.pyro.eu.org/jenkins.debian.net.git ok, cool! I want to review that more awake... > I admit I haven't tested it! ... but I guess I will merge it happily, as it will just affect kfreebsd jobs ;) (So I will come back to this tomorrow...) > I guess it might not work initially. that's totally fine, really. if it works in 2 weeks i'll be super happy. and also in 4 :-) > But > it is based on the previous work, which I'd roughly tested in isolation > without Jenkins. *nods* > I didn't look into a job for this yet, but if you already have one, the > only change needed should be to supply the URL of a netboot.tar.gz > instead of an .iso; for example > http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/netboot-10/netboot. > tar.gz there are some in job-cfg/g-i-installation.yaml > > you/kfreebsd are/is much welcome! > > Really, thanks; and to everyone else who is helping. Initially it felt > a bit like kfreebsd, and myself personally, being shoved out of the > project. But now seeing so many people being supportive it does seem > viable and welcomed to keep this alive as a part of Debian. yay! I've been very very glad to read this! I surely hope kfreebsd will be properly part of Debian 9/stretch again! (and so also be early re-added to stretch once jessie is out...) cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: jenkins kfreebsd jobs (Re: Plan B for kfreebsd)
Hi, failed with: + sudo qemu-system-x86_64 -display vnc=localhost:1 -enable-kvm -cpu host - cdrom /var/lib/jenkins/jobs/g-i- installation_debian_sid_daily_kfreebsd/workspace/debian-testing-kfreebsd- amd64-netinst.iso -boot d -drive file=/dev/jenkins01/debian_sid_daily_kfreebsd,index=0,media=disk,cache=unsafe -m 1024 -net nic,vlan=0 -net user,vlan=0,host=10.0.2.1,dhcpstart=10.0.2.2,dns=10.0.2.254 --append 'auto=true mirror/suite=sid priority=critical locale=en_US keymap=us url=http://10.0.2.1//d-i-preseed-cfgs/debian_sid_daily_kfreebsd_preseed.cfg video=vesa:ywrap,mtrr vga=788 -- quiet' -append only allowed with -kernel option cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: jenkins kfreebsd jobs (Re: Plan B for kfreebsd)
Hi Steven, I've merged your patches now and pushed and deployed them and just triggered https://jenkins.debian.net/job/g-i-installation_debian_sid_daily_kfreebsd/429/ - I'm curious how it goes :-) (forgot to press send on this one... sorry for the noise) cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: jenkins kfreebsd jobs (Re: Plan B for kfreebsd)
Hi Steven, On Mittwoch, 12. November 2014, Steven Chamberlain wrote: > Thanks for committing, and the test-run; I can see much better now how > it's supposed to work. yay! https://jenkins.debian.net/view/g-i-installation/job/g-i- installation_debian_sid_daily_kfreebsd/431/screenshot/ also looks much better now :-)) > Again, committed changes to kfreebsd branch at: > https://git.steven.hosting.pyro.eu.org/jenkins.debian.net.git/ > https://git.steven.hosting.pyro.eu.org/?p=jenkins.debian.net.git;a=shortlog > ;h=refs/heads/kfreebsd merged them all and then fixed a trivial syntax error you introduced :) thanks a lot! cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: jenkins kfreebsd jobs (Re: Plan B for kfreebsd)
Hi, https://jenkins.debian.net/view/g-i-installation/job/g-i- installation_debian_sid_daily_kfreebsd/431/screenshot/ fails again, because it cannot download the preseed file, despite it's there. At first I thought QEMU_NET_OPTS is probably not set, but it is, so hmmm. Maybe the video will give more clues... cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: jenkins kfreebsd jobs (Re: Plan B for kfreebsd)
Hi, On Mittwoch, 12. November 2014, Steven Chamberlain wrote: > Sorry! np, really... > Future idea would be to split out some functions so that I > can at least dry-run them from a basic shell without Jenkins... I'll shortly replace g-i-i.sh with something based on libvirt-cucumber+sakuli, so I'd suggest not to invest too much work in g-i-i.sh anymore... > > cannot download the preseed file, despite it's there. At first I thought > > QEMU_NET_OPTS is probably not set, but it is, so hmmm. Maybe the video > > will give more clues... in the video there is no IP address to be seen. em0 gets a link, but thats all. > d-i syslog should be going to Qemu's virtual serial port. Would you > prefer that I either add: > > -serial stdio, so that d-i syslog messages appear inline in Jenkins > console output (there will be many of them, but they are helpful) > > or > > -serial file, to write those separately as an artifact whatever you prefer really. I tend to somewhat prefer the latter... optionally output that at the end of the job... cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: jenkins kfreebsd jobs (Re: Plan B for kfreebsd)
Hi, On Mittwoch, 12. November 2014, Samuel Thibault wrote: > > Maybe hurd also could redirect syslog there to help debug the issue > > you're seeing. > Indeed. actually, all installs can probably benefit from this :) > There is: console=com0, it'd only redirect the kernel messages though > (which can however be useful to get the out of the vga console output, > and in a safe place) [...] > Yes, it'd be com0 for GNU/Hurd. patches, please. cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: jenkins kfreebsd jobs (Re: Plan B for kfreebsd)
Hi, On Mittwoch, 12. November 2014, Steven Chamberlain wrote: > Holger Levsen wrote: > > in the video there is no IP address to be seen. em0 gets a link, but > > thats all. > Later 'network autoconfiguration succeeded', so DHCP probably worked; > the IP address isn't usually mentioned within the GUI installer, but > the d-i syslog will probably explain what the problem is. ok, cool. > Okay I've tried to log serial console output as an artifact, if you > could pull again please: > https://git.steven.hosting.pyro.eu.org/jenkins.debian.net.git/?h=adc905d26d > 93381495a47ece2259207009f0da5e merged+pushed, thanks. Will trigger new builds once jenkins.d.n is up again, there are currently some disturbances in the cloud... cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: jenkins kfreebsd jobs (Re: Plan B for kfreebsd)
Hi, https://jenkins.debian.net/view/g-i-installation/job/g-i-installation_debian_sid_daily_kfreebsd/432/artifact/results/serial.log is there now and it shows how the right IP is received. I don't understand why getting the preseed file then fails... cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: jenkins kfreebsd jobs (Re: Plan B for kfreebsd)
Hi Steven, On Donnerstag, 13. November 2014, Steven Chamberlain wrote: > I think we're missing some data from the end of the serial.log; > probably due to some buffering, and qemu being sent SIGKILL. > > Please consider this change to use SIGINT for up to 10 seconds, > then SIGKILL only if it's still running after that: > https://git.steven.hosting.pyro.eu.org/jenkins.debian.net.git/?h=894584fca2 > 66789c8f40b4c0cad60b7909385523 did you make this never returns false? The script will immidiatly end in that case, iirc... cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: jenkins kfreebsd jobs (Re: Plan B for kfreebsd)
Hi, On Freitag, 14. November 2014, Steven Chamberlain wrote: > Are you thinking of "-e" (exit on error)? yes > g-i-installation.sh doesn't > seem to run in that mode, actually it ignores some failing commands > already during cleanup steps. yes, but during cleanup +e is explicitly set, I think. Oh, well, I suppose I should either merge and see how it fails or read the code myself before merging... ;-) cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: jenkins kfreebsd jobs (Re: Plan B for kfreebsd)
Hi Steven, On Freitag, 14. November 2014, Steven Chamberlain wrote: > Aha yes it does "set +e" inside that function. But code before and > after it does ignore + have to handle fatal errors itself. > > The code I added shouldn't return false, except maybe a race between > 'ps' and 'kill' (if the process goes away in that time); but seems > unlikely with the 'sleep 1' after each iteration. ok, cool, thanks for checking! +merged+pushed+deployed+job triggered :) cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: jenkins kfreebsd jobs (Re: Plan B for kfreebsd)
Hi Steven, On Freitag, 14. November 2014, Steven Chamberlain wrote: > After I started at the error message long enough, it finally hit me, > and it's kind of amusing. If you could please fix my silly mistake: hehe, I know that feeling... :-) merged + triggered etc.. - thanks! cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: tasksel desktop preseed issues (was: Re: Failure: g-i-installation_debian_sid_daily_hurd_lxde/71)
On Freitag, 14. November 2014, Steven Chamberlain wrote: > Firstly could someone please tell me what display manager this is? > https://jenkins.debian.net/view/g-i-installation/job/g-i-installation_debia > n_sid_daily_hurd_lxde/70/artifact/results//snapshot_008244.png xdm signature.asc Description: This is a digitally signed message part.
Re: tasksel desktop preseed issues (was: Re: Failure: g-i-installation_debian_sid_daily_hurd_lxde/71)
Hi, On Samstag, 15. November 2014, Samuel Thibault wrote: > See the preseed file: we force the use of xdm, I guess because lightdm > doesn't work yet. do "git blame" on that line, it's an ancient choice... probably better now to not force any specific dm and just choose a de. Holger signature.asc Description: This is a digitally signed message part.
Re: [Stretch] Status for architecture qualification
On Sun, Jun 05, 2016 at 01:26:39PM +0200, John Paul Adrian Glaubitz wrote: > ppc64: > > This architecture is basically on par with the release architectures. We have > over > 11.000 packages installed [...] > sparc64: > We are close to 11.000 installed packages. I'm not sure whether you are talking about source or binary packages but sid/amd64 has over 24000 source packages and over 5 binary packages, so I would call the above "on par". Or what am I missing? -- cheers, Holger signature.asc Description: Digital signature
Re: [Stretch] Status for architecture qualification
thanks to everyone explaining arch:any to me :) -- cheers, Holger signature.asc Description: Digital signature
Debian Buster release to partially drop non-systemd support
On Sat, Oct 13, 2018 at 06:01:43AM +0100, Ben Hutchings wrote: > > Has policy changed regarding support for multiple inits, or is it just that > > no one is maintaining the shim and sysvinit-core? > > The latter. systemd-shim has been orphaned for over 2 years, and has > RC bugs. sysvinit currently has two maintainers, but they've only > ever made one upload (over a year ago). It seems that these facts are either largely ignored or unknown and I wonder if some noise should be made so that interested people can pick up the work now and not only complain later. Please reply to debian-devel@lists.d.o if you have to, but probably replying to those RC bugs is more effective. Also please avoid cc:ing me. -- cheers, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
Re: Debian Buster release to partially drop non-systemd support
On Fri, Oct 19, 2018 at 11:35:54AM +0200, Martin Steigerwald wrote: > A minority? Yes. But a sizable one. It doesn't matter how many people use it, if noone is willing to maintain it. *If* people are maintaining it, it also doesnt matter how many people are using it :) *Someone* needs to do the work. We are all volunteers. Be the change you want to see in the world. -- cheers, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
Re: Hurd-i386 and kfreebsd-{i386,amd64} removal
On Sat, Apr 13, 2019 at 09:31:46AM +0200, Samuel Thibault wrote: > Samuel Thibault, le sam. 13 avril 2019 00:11:15 +0200, a ecrit: > > Joerg Jaspert, le ven. 12 avril 2019 23:30:31 +0200, a ecrit: > > > It seems to exist there, so probably someone who can upload there and > > > is interested in hurd-i386 goes and uploads stuff. > > Within a two-week timeframe only? > (while everybody is supposed to be busy fixing RC bugs) would 6 weeks work be better for you? I can see how the ftpteam doesnt want to delay this *after* the Buster release, but maybe they can agree on giving you a bit more time, so you can a.) still do the move and b.) not neglect polishing buster for https://wiki.debian.org/accessibility -- tschau, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
