Re: libstdc++6-udeb package (Re: RFC: auto-load of D-I drivers in GNU/kFreeBSD)
On Sun, Mar 11, 2012 at 08:07:46PM +0100, Robert Millan wrote: > El 5 de març de 2012 21:51, Robert Millan ha escrit: > > 1- Add libstdc++6-udeb package (needed by devd). > Oh, I wasn't aware that libstdc++ udeb had already been proposed, and > it seems to be a controversial topic... Reducing libstdc++ with mklibs is tricky, so only the unreduced lib can be included into the boot image. C++ is controversial, because the output is usually rather large. Bastian -- Klingon phaser attack from front! 100% Damage to life support -- 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/20120311202753.ga20...@wavehammer.waldi.eu.org
Re: libstdc++6-udeb package (Re: RFC: auto-load of D-I drivers in GNU/kFreeBSD)
On Sun, Mar 11, 2012 at 05:37:35PM -0300, Otavio Salvador wrote: > On Sun, Mar 11, 2012 at 17:27, Bastian Blank wrote: > > Reducing libstdc++ with mklibs is tricky, so only the unreduced lib can > > be included into the boot image. C++ is controversial, because the > > output is usually rather large. > IIRC you stared working on a reduced stdc++ library, didn't you? I used it for some years with the tuxbox project. But it needs patches to gcc. Bastian -- We'll pivot at warp 2 and bring all tubes to bear, Mr. Sulu! -- 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/20120311212140.ga21...@wavehammer.waldi.eu.org
Bug#459747: kfreebsd-7 - FTBFS: failure: cannot read files list file: No such file or directory
Package: kfreebsd-7 Version: 7.0~cvs20080107-1 Severity: serious There was an error while trying to autobuild your package: > Automatic build of kfreebsd-7_7.0~cvs20080107-1 on lxdebian.bfinv.de by > sbuild/s390 98 [...] > /usr/bin/fakeroot debian/rules binary-arch > # We have nothing to do > dpkg-genchanges -B -ms390 Build Daemon > >../kfreebsd-7_7.0~cvs20080107-1_s390.changes > dpkg-genchanges: arch-specific upload - not including arch-independent > packages > dpkg-genchanges: failure: cannot read files list file: No such file or > directory > dpkg-buildpackage: failure: dpkg-genchanges gave error exit status 2 > ** > Build finished at 20080107-1500 > FAILED [dpkg-buildpackage died] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [busybox on kbsd] patches ported to 1.14
On Tue, Sep 29, 2009 at 10:07:02PM -0300, Otavio Salvador wrote: > I'd suggest getting it commited in the package and uploaded to sid; > Bastian, do you object? Well, there is a 1.15.1 already as stable. Bastian -- I'm a soldier, not a diplomat. I can only tell the truth. -- Kirk, "Errand of Mercy", stardate 3198.9 -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#559695: kfreebsd-8 - Incomplete licensing information
Package: kfreebsd-8 Version: 8.0-1 Severity: serious The licensing information in the copyright file of the kfreebsd-8 package are incomplete and missleading. It refers to /usr/share/common-licenses/BSD, which is a 3-clause license. Also it lists licenses of sources that are not actually included in the source package. I found at least 4 different BSD-style licenses, one 2-clause, one 3-clause and two 4-clause licenses. Examples: - xen/reboot.c: 4-clause with the following advertising clause: This product includes software developed by Christian Limpach. - nfsclient/bootp_subr.c: 4-clause with the following advertising clause: This product includes software developed by the University of California, Lawrence Berkeley Laboratory and its contributors. - amd64/amd64/amd64_mem.c: 2-clause. - dev/aic7xxx/ahc_isa.c: 3-clause; kind off I think. Bastian -- War is never imperative. -- McCoy, "Balance of Terror", stardate 1709.2 -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Preparing (lib)gnome-keyring for the freeze.
On Sat, Aug 02, 2014 at 08:47:54AM +0200, Andreas Henriksson wrote: > There has been discussions about the use of mlock(all) and we have > over the past year not been able to reach a consensus. I don't > feel comfortable making the descision to rip out security features > on my own as proposed by porters and noone has been willing to take > the discussion upstream. Why do you think this is related to the use of mlock? A quick check in the source shows that an error in mlock is not fatal. Also building on Linux with a locked memory limit of 0 does not trigger this error. But several lines below this warning in the build-log is the simple statement: | Build killed with signal TERM after 150 minutes of inactivity So you found yourself a dead lock. Did you ever try to run this on a kfreebsd-* porter machine? You completely forgot to actually mention what you tried and what you observed yourself. > If for some reason (a) is not possible, please tell me and I'll implement > (b). I would propose (c): understand the problem. Anyway, I did that for you. The problem lies within build/tap-driver, aka the tool that executes the tests. In some cases it misses EOF on stderr of the executed test program, I'm however not sure why. > For more background, see: > https://packages.qa.debian.org/libg/libgnome-keyring.html > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628383 > https://packages.qa.debian.org/g/gnome-keyring.html > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750883 This misses a link to the build-log: https://buildd.debian.org/status/fetch.php?pkg=gnome-keyring&arch=kfreebsd-i386&ver=3.12.0-2&stamp=1398611094 As this is a simple bug, this is off-topic on debian-release. Bastian -- Earth -- mother of the most beautiful women in the universe. -- Apollo, "Who Mourns for Adonais?" stardate 3468.1 -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140802111814.ga29...@mail.waldi.eu.org
Re: Bug#757985: kfreebsd: hang with ENOSPC after a few components are loaded
On Wed, Aug 20, 2014 at 01:19:52AM +0100, Steven Chamberlain wrote: > On 14/08/14 18:15, Cyril Brulebois wrote: > > [...] If a > > single extra udeb (or udeb size increase, which happens from time to > > time) is going to break kfreebsd-*, it seems to me that their status > > is far too brittle. > The fixed-size d-i initrds had to be carefully sized for kfreebsd wheezy. Please move d-i to an unfixed size filesystem. Even freebsd have some sort of tmpfs. > And/or we could maybe lose some unnecessary udebs. I mentioned > partman-iscsi as an example to start with (I also didn't understand > how/why that was being included in the image at all?) but there are > probably other and larger candidates. Sorry, not in this stage of the Jessie development. Bastian -- Only a fool fights in a burning house. -- Kank the Klingon, "Day of the Dove", stardate unknown -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140820064719.ga10...@mail.waldi.eu.org
Re: Archiving the attic folders from d-i for ports
On Fri, Apr 27, 2018 at 05:37:25AM +0200, John Paul Adrian Glaubitz wrote: > Since there are still some repositories that we need for debian-ports > in the attic, I was wondering whether we should take care of the > attic stuff and move it over to salsa or github. Could you show a list? Just migrate them the same way. >Still, I think we should > archive everything. The complete content of alioth is going to be archived, so this is covered. Bastian -- We do not colonize. We conquer. We rule. There is no other way for us. -- Rojan, "By Any Other Name", stardate 4657.5
Re: Debian Buster release to partially drop non-systemd support
On Tue, Oct 16, 2018 at 07:20:24PM +0200, Adam Borowski wrote: > On Tue, Oct 16, 2018 at 05:54:34PM +0200, Petter Reinholdtsen wrote: > > Absolutely. And the sysvinit boot system have lots of unsolved problems > > we never got around to figuring out, related to disk and other device > > setup. The main cause is the fact that the linux kernel is no longer > > predicatble and sequencial, but asynchonous. No amount of wishful > > thinking is going to bring is back to a world where static sequencing of > > boot events is going to handle all the interdependencies. > Systemd fails to solve them as well -- while introducing a lot of unsolved > problems on its own, such as degraded RAID problems (no, it's not possible > do to that in an event-driven way, you need a static sequence in at least > some cases). But in the case of degraded RAID the system _is_ already broken. How does a non-event-driven solution work for it? Bastian -- I have never understood the female capacity to avoid a direct answer to any question. -- Spock, "This Side of Paradise", stardate 3417.3
