Bug#932523: marked as done (kfreebsd-10: Don't build against flex-old)

2023-07-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Jul 2023 16:47:41 + with message-id and subject line Bug#1041056: Removed package(s) from unstable has caused the Debian Bug report #932523, regarding kfreebsd-10: Don't build against flex-old to be marked as done. This means that you claim that the proble

Bug#978513: marked as done (kfreebsd-10: non-standard gcc/g++ used for build (gcc-9))

2023-07-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Jul 2023 16:47:41 + with message-id and subject line Bug#1041056: Removed package(s) from unstable has caused the Debian Bug report #978513, regarding kfreebsd-10: non-standard gcc/g++ used for build (gcc-9) to be marked as done. This means that you claim that the

Bug#827070: marked as done (kfreebsd-10: please use LDADD instead of LDFLAGS for aicasm)

2023-07-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Jul 2023 16:47:41 + with message-id and subject line Bug#1041056: Removed package(s) from unstable has caused the Debian Bug report #827070, regarding kfreebsd-10: please use LDADD instead of LDFLAGS for aicasm to be marked as done. This means that you claim that

Bug#819754: marked as done (kfreebsd-10: GCC build: stack protector panic on boot)

2023-07-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Jul 2023 16:47:41 + with message-id and subject line Bug#1041056: Removed package(s) from unstable has caused the Debian Bug report #819754, regarding kfreebsd-10: GCC build: stack protector panic on boot to be marked as done. This means that you claim that the

Bug#818743: marked as done (kfreebsd-10: Increase ARG_MAX to match the one from Linux)

2023-07-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Jul 2023 16:47:41 + with message-id and subject line Bug#1041056: Removed package(s) from unstable has caused the Debian Bug report #818743, regarding kfreebsd-10: Increase ARG_MAX to match the one from Linux to be marked as done. This means that you claim that the

Bug#788174: marked as done (kfreebsd-10: installer rescue mode grub entry)

2023-07-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Jul 2023 16:47:41 + with message-id and subject line Bug#1041056: Removed package(s) from unstable has caused the Debian Bug report #788174, regarding kfreebsd-10: installer rescue mode grub entry to be marked as done. This means that you claim that the problem has

Bug#778367: marked as done (kfreebsd-10: CVE-2014-7250 resource consumption issue)

2023-07-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Jul 2023 16:47:41 + with message-id and subject line Bug#1041056: Removed package(s) from unstable has caused the Debian Bug report #778367, regarding kfreebsd-10: CVE-2014-7250 resource consumption issue to be marked as done. This means that you claim that the

Bug#646997: marked as done (kfreebsd-10: lock order reversal (bufwait vs dirhash) in ufs_direnter)

2023-07-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Jul 2023 16:47:41 + with message-id and subject line Bug#1041056: Removed package(s) from unstable has caused the Debian Bug report #646997, regarding kfreebsd-10: lock order reversal (bufwait vs dirhash) in ufs_direnter to be marked as done. This means that you

Bug#1041056: RM: kfreebsd-10 -- RoQA; useless, unmaintained, has RC bug

2023-07-14 Thread Aurelien Jarno
doesn't make sense to keep the kfreebsd-10 package in the archive. The package is basically unmaintained, the lastest upload was more than 3 years ago and there is an RC bug for more than 2 years. Thanks Aurelien [1] https://lists.debian.org/debian-devel/2023/07/msg00176.html

Bug#978513: kfreebsd-10: non-standard gcc/g++ used for build (gcc-9)

2020-12-28 Thread Matthias Klose
Package: kfreebsd-10 Severity: important Tags: sid bullseye User: debian-...@lists.debian.org Usertags: non-standard-compiler, gcc-9, gcc-9-legacy This package builds with a non standard compiler version; please check if this package can be built with the default version of gcc/g++, or with gcc

kfreebsd-10 is marked for autoremoval from testing

2020-08-26 Thread Debian testing autoremoval watch
kfreebsd-10 10.3~svn300087+ds1-1 is marked for autoremoval from testing on 2020-09-07 It (build-)depends on packages with these RC bugs: 957230: freebsd-buildutils: ftbfs with GCC-10 https://bugs.debian.org/957230 964661: freebsd-glue: FTBFS: dpkg-gensymbols: error: some symbols or patterns

kfreebsd-10 is marked for autoremoval from testing

2020-08-06 Thread Debian testing autoremoval watch
kfreebsd-10 10.3~svn300087+ds1-1 is marked for autoremoval from testing on 2020-08-28 It (build-)depends on packages with these RC bugs: 957230: freebsd-buildutils: ftbfs with GCC-10 https://bugs.debian.org/957230 964661: freebsd-glue: FTBFS: dpkg-gensymbols: error: some symbols or patterns

kfreebsd-10 is marked for autoremoval from testing

2020-07-16 Thread Debian testing autoremoval watch
kfreebsd-10 10.3~svn300087+ds1-1 is marked for autoremoval from testing on 2020-08-22 It (build-)depends on packages with these RC bugs: 964661: freebsd-glue: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below 964698: freebsd-libs

kfreebsd-10 is marked for autoremoval from testing

2020-04-01 Thread Debian testing autoremoval watch
kfreebsd-10 10.3~svn300087-6 is marked for autoremoval from testing on 2020-04-11 It is affected by these RC bugs: 944170: kfreebsd-10: non-standard gcc/g++ used for build (gcc-8)

Re: Bug#955210: kernel-wedge: regression causes kfreebsd-10 FTBFS

2020-03-29 Thread Steven Chamberlain
Hi! Ben Hutchings wrote: > Sorry about that. I knew this was a relatively risky change, but > thought I had test cases covering everything. No problem. The refactoring is much appreciated, and it is understandable when regressions happen somewhere in this labyrinth of sh/bash/perl. > Would you

Re: Bug#955210: kernel-wedge: regression causes kfreebsd-10 FTBFS

2020-03-28 Thread Ben Hutchings
On Sat, 2020-03-28 at 13:41 +, Steven Chamberlain wrote: [...] > kfreebsd-10 FTBFS, due to probably this change in kernel-wedge: > https://salsa.debian.org/installer-team/kernel-wedge/-/commit/3827f1ee9f53540b104c592a8a2695f78d8629ed [...] On Sat, 2020-03-28 at 18:29 +,

Re: Bug#955210: kernel-wedge: regression causes kfreebsd-10 FTBFS

2020-03-28 Thread Steven Chamberlain
tags -1 + patch thanks From 03477bf089926f7a599bbe89f67df53080b69bfa Mon Sep 17 00:00:00 2001 From: Steven Chamberlain Date: Sat, 28 Mar 2020 18:12:35 + Subject: [PATCH] preprocess: If source directory is a symlink, follow it Closes: #955210 --- commands/preprocess | 9 + debian/chan

Bug#955210: kernel-wedge: regression causes kfreebsd-10 FTBFS

2020-03-28 Thread Steven Chamberlain
Package: kernel-wedge Version: 2.102 Severity: important X-Debbugs-Cc: debian-bsd@lists.debian.org Hi, kfreebsd-10 FTBFS, due to probably this change in kernel-wedge: https://salsa.debian.org/installer-team/kernel-wedge/-/commit/3827f1ee9f53540b104c592a8a2695f78d8629ed The kfreebsd-10 build

Bug#944170: marked as done (kfreebsd-10: non-standard gcc/g++ used for build (gcc-8))

2020-03-27 Thread Debian Bug Tracking System
Your message dated Fri, 27 Mar 2020 22:50:49 + with message-id and subject line Bug#944170: fixed in kfreebsd-10 10.3~svn300087-6 has caused the Debian Bug report #944170, regarding kfreebsd-10: non-standard gcc/g++ used for build (gcc-8) to be marked as done. This means that you claim that

kfreebsd-10 is marked for autoremoval from testing

2020-03-26 Thread Debian testing autoremoval watch
kfreebsd-10 10.3~svn300087-5 is marked for autoremoval from testing on 2020-04-10 It is affected by these RC bugs: 944170: kfreebsd-10: non-standard gcc/g++ used for build (gcc-8)

Processed: Re: kfreebsd-10: non-standard gcc/g++ used for build (gcc-8)

2020-03-26 Thread Debian Bug Tracking System
Processing control commands: > block 954831 with -1 Bug #954831 [ftp.debian.org] RM: gcc-8 -- ROM; superseded by gcc-9 954831 was not blocked by any bugs. 954831 was not blocking any bugs. Added blocking bug(s) of 954831: 944170 > severity -1 serious Bug #944170 [kfreebsd-10] kfreebsd-1

Bug#944170: kfreebsd-10: non-standard gcc/g++ used for build (gcc-8)

2020-03-26 Thread Emilio Pozuelo Monfort
Control: block 954831 with -1 Control: severity -1 serious On Tue, 05 Nov 2019 13:22:46 + Matthias Klose wrote: > Package: kfreebsd-10 > Severity: important > Tags: sid bullseye > User: debian-...@lists.debian.org > Usertags: non-standard-compiler, gcc-8, gcc-8-legacy &g

Bug#944170: kfreebsd-10: non-standard gcc/g++ used for build (gcc-8)

2019-11-05 Thread Matthias Klose
Package: kfreebsd-10 Severity: important Tags: sid bullseye User: debian-...@lists.debian.org Usertags: non-standard-compiler, gcc-8, gcc-8-legacy This package builds with a non standard compiler version; please check if this package can be built with the default version of gcc/g++, or with gcc-9

Bug#932523: kfreebsd-10: Don't build against flex-old

2019-07-20 Thread Tommi Vainikainen
Source: kfreebsd-10 Severity: normal Tags: patch Hi, as a maintainer of flex-old package I'm considering requesting removing it as obsolete and unmaintained version of flex. kfreebsd-10 Build-Depends on flex-old as alternative to current flex. Please build the package only against current

Bug#892398: marked as done (kfreebsd-10: build-depends on GCC 6)

2019-01-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Jan 2019 15:35:52 + with message-id and subject line Bug#892398: fixed in kfreebsd-10 10.3~svn300087-4 has caused the Debian Bug report #892398, regarding kfreebsd-10: build-depends on GCC 6 to be marked as done. This means that you claim that the problem has been

Processed: [bts-link] source package kfreebsd-10

2018-06-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package kfreebsd-10 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l..

Bug#892398: kfreebsd-10: build-depends on GCC 6

2018-03-08 Thread pochu
Source: kfreebsd-10 Severity: serious Tags: sid buster User: debian-...@lists.debian.org Usertags: gcc-6-rm Hi, kfreebsd-10 build-depends on GCC 6. We now have GCC 7 (default) and GCC 8 in the archive, so please make your package build with a newer compiler (preferably the default one) again

Bug#868929: kfreebsd-10: FTBFS: ../../../compat/ia32/ia32_genassym.c:1:0: error: code model kernel does not support PIC mode

2017-08-17 Thread Adrian Bunk
Control: severity -1 serious On Wed, Aug 16, 2017 at 11:28:47PM +0100, Steven Chamberlain wrote: > severity 868929 important > thanks > > (linux-)amd64 is not in this package's Architectures: field, therefore > FTBFS on that arch cannot be a RC bug? (Though I'd be interested in > fixing it somed

Processed: Re: Bug#868929: kfreebsd-10: FTBFS: ../../../compat/ia32/ia32_genassym.c:1:0: error: code model kernel does not support PIC mode

2017-08-17 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #868929 [src:kfreebsd-10] kfreebsd-10: FTBFS: ../../../compat/ia32/ia32_genassym.c:1:0: error: code model kernel does not support PIC mode Severity set to 'serious' from 'important' -- 868929: https://bugs.debian.or

Bug#868929: kfreebsd-10: FTBFS: ../../../compat/ia32/ia32_genassym.c:1:0: error: code model kernel does not support PIC mode

2017-08-16 Thread Steven Chamberlain
severity 868929 important thanks (linux-)amd64 is not in this package's Architectures: field, therefore FTBFS on that arch cannot be a RC bug? (Though I'd be interested in fixing it someday). Regards, -- Steven Chamberlain ste...@pyro.eu.org signature.asc Description: Digital signature

Processed: Re: Bug#868929: kfreebsd-10: FTBFS: ../../../compat/ia32/ia32_genassym.c:1:0: error: code model kernel does not support PIC mode

2017-08-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 868929 important Bug #868929 [src:kfreebsd-10] kfreebsd-10: FTBFS: ../../../compat/ia32/ia32_genassym.c:1:0: error: code model kernel does not support PIC mode Severity set to 'important' from 'serious' >

kfreebsd-10 is marked for autoremoval from testing

2017-08-15 Thread Debian testing autoremoval watch
kfreebsd-10 10.3~svn300087-3 is marked for autoremoval from testing on 2017-08-17 It is affected by these RC bugs: 868929: kfreebsd-10: FTBFS: ../../../compat/ia32/ia32_genassym.c:1:0: error: code model kernel does not support PIC mode

kfreebsd-10 is marked for autoremoval from testing

2017-07-26 Thread Debian testing autoremoval watch
kfreebsd-10 10.3~svn300087-3 is marked for autoremoval from testing on 2017-08-17 It is affected by these RC bugs: 868929: kfreebsd-10: FTBFS: ../../../compat/ia32/ia32_genassym.c:1:0: error: code model kernel does not support PIC mode

Bug#868929: kfreebsd-10: FTBFS: ../../../compat/ia32/ia32_genassym.c:1:0: error: code model kernel does not support PIC mode

2017-07-19 Thread Lucas Nussbaum
Source: kfreebsd-10 Version: 10.3~svn300087-3 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170719 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

kfreebsd-10 is marked for autoremoval from testing

2017-01-27 Thread Debian testing autoremoval watch
kfreebsd-10 10.3~svn300087-2 is marked for autoremoval from testing on 2017-02-18 It is affected by these RC bugs: 852006: kfreebsd-10: non-standard gcc/g++ used for build (gcc-5)

Bug#852006: marked as done (kfreebsd-10: non-standard gcc/g++ used for build (gcc-5))

2017-01-20 Thread Debian Bug Tracking System
Your message dated Fri, 20 Jan 2017 18:18:52 + with message-id and subject line Bug#852006: fixed in kfreebsd-10 10.3~svn300087-3 has caused the Debian Bug report #852006, regarding kfreebsd-10: non-standard gcc/g++ used for build (gcc-5) to be marked as done. This means that you claim that

Bug#852006: kfreebsd-10: non-standard gcc/g++ used for build (gcc-5)

2017-01-20 Thread Matthias Klose
Package: src:kfreebsd-10 Version: 10.3~svn300087-2 Severity: serious Tags: sid stretch User: debian-...@lists.debian.org Usertags: non-standard-compiler, gcc-5, gcc-5-legacy This package builds with a non standard compiler version; please check if this package can be built with the default version

kfreebsd-10 is marked for autoremoval from testing

2017-01-19 Thread Debian testing autoremoval watch
kfreebsd-10 10.3~svn300087-1 is marked for autoremoval from testing on 2017-01-24 It is affected by these RC bugs: 835950: kfreebsd-10: non-standard gcc/g++ used for build (gcc-5)

Bug#827072: marked as done (kfreebsd-10: use notify-reboot-required)

2017-01-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Jan 2017 15:07:52 + with message-id and subject line Bug#827072: fixed in kfreebsd-10 10.3~svn300087-2 has caused the Debian Bug report #827072, regarding kfreebsd-10: use notify-reboot-required to be marked as done. This means that you claim that the problem has

Bug#835950: marked as done (kfreebsd-10: non-standard gcc/g++ used for build (gcc-5))

2017-01-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Jan 2017 15:07:52 + with message-id and subject line Bug#835950: fixed in kfreebsd-10 10.3~svn300087-2 has caused the Debian Bug report #835950, regarding kfreebsd-10: non-standard gcc/g++ used for build (gcc-5) to be marked as done. This means that you claim that

Processed: Re: Bug#811278: kfreebsd-10: CVE-2016-1880: Linux compatibility layer incorrect futex handling [SA-16:02]

2017-01-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # fixed in 10.3 branch since r293897 > fixed 811278 kfreebsd-10/10.3~svn296373-1 Bug #811278 {Done: Steven Chamberlain } [src:kfreebsd-10] kfreebsd-10: CVE-2016-1880: Linux compatibility layer incorrect futex handling [SA-16:03] Marked as

kfreebsd-10 is marked for autoremoval from testing

2016-12-30 Thread Debian testing autoremoval watch
kfreebsd-10 10.3~svn300087-1 is marked for autoremoval from testing on 2017-01-14 It is affected by these RC bugs: 811278: kfreebsd-10: CVE-2016-1880: Linux compatibility layer incorrect futex handling [SA-16:03] 811279: kfreebsd-10: CVE-2016-1881: Linux compatibility layer setgroups(2) system

Processed: Re: Bug#837289: kfreebsd-10: FTBFS: objcopy:linux32_vdso.so: Invalid bfd target

2016-10-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 837289 important Bug #837289 [src:kfreebsd-10] kfreebsd-10: FTBFS: objcopy:linux32_vdso.so: Invalid bfd target Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact

Bug#837289: kfreebsd-10: FTBFS: objcopy:linux32_vdso.so: Invalid bfd target

2016-10-27 Thread Steven Chamberlain
severity 837289 important thanks Hi, Lucas Nussbaum wrote: > Severity: serious > Justification: FTBFS on amd64 This package's Architecture: fields do not include [linux-]amd64, so I think this is not release-critical. It is desirable though that we can fix it to become possible (again) to build

Bug#835950: kfreebsd-10: non-standard gcc/g++ used for build (gcc-5)

2016-08-29 Thread Matthias Klose
Package: kfreebsd-10 Version: 10.3~svn300087-1 Severity: important Tags: sid stretch User: debian-...@lists.debian.org Usertags: non-standard-compiler, gcc-5, gcc-5-legacy This package builds with a non standard compiler version; please check if this package can be built with the default version

Bug#827072: kfreebsd-10: use notify-reboot-required

2016-06-11 Thread Steven Chamberlain
Control: tags -1 + pending Hi, Jon Boden wrote: > notify-reboot-required is the Ubuntu way packages tell the user that a > reboot is required (usually after an upgrade). Patch applied in SVN, thanks! Debian has this too (update-notifier-common) but I'm not sure if it is typically installed. If

Processed: Re: Bug#827072: kfreebsd-10: use notify-reboot-required

2016-06-11 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + pending Bug #827072 [kfreebsd-10] kfreebsd-10: use notify-reboot-required Added tag(s) pending. -- 827072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827072 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#827072: kfreebsd-10: use notify-reboot-required

2016-06-11 Thread Jon Boden
Package: kfreebsd-10 Version: 10.3~svn300087-1 Tags: patch Hi If it's not too much noise, could you merge this small patch? https://bazaar.launchpad.net/~ubuntubsd/ubuntubsd/kfreebsd-10/diff/692?context=3 notify-reboot-required is the Ubuntu way packages tell the user that a reboo

Bug#827070: kfreebsd-10: please use LDADD instead of LDFLAGS for aicasm

2016-06-11 Thread Jon Boden
Package: kfreebsd-10 Version: 10.3~svn300087-1 Tags: patch Hi When building kfreebsd-10 on ubuntuBSD, at least with current toolchain (and possibly on Debian eventually), it fails with linker errors because the -lbsd -ldb flags are not with the rest of the flags (-ll) and for some reason the

Bug#824604: marked as done (kfreebsd-10: CVE-2016-1886: Buffer overflow in keyboard driver)

2016-05-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 May 2016 00:19:59 + with message-id and subject line Bug#824604: fixed in kfreebsd-10 10.1~svn274115-4+kbsd8u4 has caused the Debian Bug report #824604, regarding kfreebsd-10: CVE-2016-1886: Buffer overflow in keyboard driver to be marked as done. This means that

Bug#824605: marked as done (kfreebsd-10: CVE-2016-1887: Incorrect argument handling in sendmsg(2))

2016-05-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 May 2016 00:19:59 + with message-id and subject line Bug#824605: fixed in kfreebsd-10 10.1~svn274115-4+kbsd8u4 has caused the Debian Bug report #824605, regarding kfreebsd-10: CVE-2016-1887: Incorrect argument handling in sendmsg(2) to be marked as done. This means

Bug#824604: kfreebsd-10: CVE-2016-1886: Buffer overflow in keyboard driver

2016-05-17 Thread Steven Chamberlain
Package: src:kfreebsd-10 Version: 10.1~svn274115-4+kbsd8u3 Severity: grave Tags: security https://security.FreeBSD.org/advisories/FreeBSD-SA-16:18.atkbd.asc Incorrect signedness comparison in the ioctl(2) handler allows a malicious local user to overwrite a portion of the kernel memory. This aff

Bug#824605: kfreebsd-10: CVE-2016-1887: Incorrect argument handling in sendmsg(2)

2016-05-17 Thread Steven Chamberlain
Package: src:kfreebsd-10 Version: 10.1~svn274115-4+kbsd8u3 Severity: grave Tags: security https://security.FreeBSD.org/advisories/FreeBSD-SA-16:19.sendmsg.asc Incorrect argument handling in the socket code allows malicious local user to overwrite large portion of the kernel memory. This affects

Bug#813727: kfreebsd-10: update clang version

2016-05-17 Thread Mattia Rizzolo
control: close -1 10.3~svn296998-2 On Tue, May 17, 2016 at 04:33:15PM +0100, Steven Chamberlain wrote: > Hi, > > Mattia Rizzolo wrote: > > you may have stopped using it during the build, but you still have the > > build-dep. > > The package in sid still uses clang; the one in experimental has >

Processed: Re: Bug#813727: kfreebsd-10: update clang version

2016-05-17 Thread Debian Bug Tracking System
Processing control commands: > close -1 10.3~svn296998-2 Bug #813727 [src:kfreebsd-10] kfreebsd-10: update clang version Ignoring request to alter fixed versions of bug #813727 to the same values previously set Bug #813727 [src:kfreebsd-10] kfreebsd-10: update clang version Marked Bug as d

Processed: Re: Processed: Re: kfreebsd-10: update clang version

2016-05-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # in experimental > fixed 813727 kfreebsd-10/10.3~svn296998-2 Bug #813727 [src:kfreebsd-10] kfreebsd-10: update clang version Marked as fixed in versions kfreebsd-10/10.3~svn296998-2. > thanks Stopping processing here. Please contact

Bug#813727: kfreebsd-10: update clang version

2016-05-17 Thread Steven Chamberlain
Hi, Mattia Rizzolo wrote: > you may have stopped using it during the build, but you still have the > build-dep. The package in sid still uses clang; the one in experimental has switched to GCC and I hope to get that into sid within a week or so. Regards, -- Steven Chamberlain ste...@pyro.eu.or

Bug#813727: kfreebsd-10: update clang version

2016-05-17 Thread Mattia Rizzolo
control: reopen -1 you may have stopped using it during the build, but you still have the build-dep. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' :

Processed: Re: kfreebsd-10: update clang version

2016-05-17 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #813727 {Done: Steven Chamberlain } [src:kfreebsd-10] kfreebsd-10: update clang version 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bu

Bug#820151: marked as done (kfreebsd-10: non-DFSG mode (for ubuntuBSD))

2016-04-10 Thread Debian Bug Tracking System
Your message dated Sun, 10 Apr 2016 16:24:00 + with message-id and subject line Bug#820151: fixed in kfreebsd-10 10.3~svn297264-1~debug1 has caused the Debian Bug report #820151, regarding kfreebsd-10: non-DFSG mode (for ubuntuBSD) to be marked as done. This means that you claim that the

Bug#820151: kfreebsd-10: non-DFSG mode (for ubuntuBSD)

2016-04-09 Thread Steven Chamberlain
you like a patch to do that? I've committed my take on this as SVN r5987 of svn://anonscm.debian.org/glibc-bsd/trunk/kfreebsd-10 This is our experimental 10.3 branch, however. I'm still testing it. It will likely go into sid in the next couple of weeks. > > I'm considering to

Processed: Re: Bug#820151: kfreebsd-10: non-DFSG mode (for ubuntuBSD)

2016-04-09 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + pending Bug #820151 [kfreebsd-10] kfreebsd-10: non-DFSG mode (for ubuntuBSD) Added tag(s) pending. -- 820151: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820151 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Re: Bug#820151: kfreebsd-10: non-DFSG mode (for ubuntuBSD)

2016-04-09 Thread Adam Wilson
On Sat, 9 Apr 2016 12:48:28 +0200 Jon Boden wrote: > > Hi Steven > > On Sat, Apr 09, 2016 at 01:15:33AM +0100, Steven Chamberlain wrote: > > My first thought is to use the Version field; that already > > determines what SVN revision is checked out from which branch. If > > it contained someth

Bug#820151: kfreebsd-10: non-DFSG mode (for ubuntuBSD)

2016-04-09 Thread Jon Boden
Hi Steven On Sat, Apr 09, 2016 at 01:15:33AM +0100, Steven Chamberlain wrote: > My first thought is to use the Version field; that already determines > what SVN revision is checked out from which branch. If it contained > something like "+nonfree", get-orig-source could retain the non-free > st

Bug#820151: kfreebsd-10: non-DFSG mode (for ubuntuBSD)

2016-04-09 Thread Jon Boden
On Sat, Apr 09, 2016 at 01:09:03AM +0200, Guillem Jover wrote: > > + lsb-release, > > You don't need this, see below… > > > Standards-Version: 3.9.2 > > > > Package: kfreebsd-source-@version@ > > Index: debian/rules > > === > > -

Bug#820151: kfreebsd-10: non-DFSG mode (for ubuntuBSD)

2016-04-08 Thread Steven Chamberlain
Hi, Guillem Jover wrote: > On Tue, 2016-04-05 at 23:17:08 +0200, Jon Boden wrote: > > This patch has no effect on Debian but it enables "non-DFSG mode" when > > compiling kfreebsd-10 on ubuntuBSD. Please could you apply it to make > > it easier for us to resync

Bug#820151: kfreebsd-10: non-DFSG mode (for ubuntuBSD)

2016-04-08 Thread Guillem Jover
Hi! On Tue, 2016-04-05 at 23:17:08 +0200, Jon Boden wrote: > Package: kfreebsd-10 > Version: 10.1~svn274115-4+kbsd8u3 > Severity: wishlist > Tags: patch > This patch has no effect on Debian but it enables "non-DFSG mode" when > compiling kfreebsd-10 on ubuntuBSD.

Bug#820151: kfreebsd-10: non-DFSG mode (for ubuntuBSD)

2016-04-05 Thread Jon Boden
Package: kfreebsd-10 Version: 10.1~svn274115-4+kbsd8u3 Severity: wishlist Tags: patch Hi This patch has no effect on Debian but it enables "non-DFSG mode" when compiling kfreebsd-10 on ubuntuBSD. Please could you apply it to make it easier for us to resync with kfreebsd-10? It als

Bug#813727: marked as done (kfreebsd-10: update clang version)

2016-04-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Apr 2016 19:00:36 + with message-id and subject line Bug#813727: fixed in kfreebsd-10 10.3~svn296998-2 has caused the Debian Bug report #813727, regarding kfreebsd-10: update clang version to be marked as done. This means that you claim that the problem has been

Bug#819754: kfreebsd-10: GCC build: stack protector panic on boot

2016-04-01 Thread Steven Chamberlain
Package: src:kfreebsd-10 Version: 10.3~svn296998-1 Severity: normal Hi, When compiled with GCC (rather than upstream default compiler Clang), WITH_SSP (Stack Smashing Protection), kfreebsd-10 panics on boot. The panic is in taskqueue_start_threads, just before it would start zfskern I think

Bug#818743: kfreebsd-10: Increase ARG_MAX to match the one from Linux

2016-03-21 Thread Jakub Wilk
* Steven Chamberlain , 2016-03-20, 13:40: I haven't seen this problem with Debian libreoffice builds (yet). Possibly relevant commit: https://anonscm.debian.org/cgit/pkg-openoffice/libreoffice.git/commit/?id=0cfc2774303b -- Jakub Wilk

Bug#818777: marked as done (kfreebsd-10: non-standard gcc/g++ used for build (gcc-4.9))

2016-03-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Mar 2016 23:25:31 + with message-id and subject line Bug#818777: fixed in kfreebsd-10 10.3~svn296998-1 has caused the Debian Bug report #818777, regarding kfreebsd-10: non-standard gcc/g++ used for build (gcc-4.9) to be marked as done. This means that you claim

Bug#818426: marked as done (kfreebsd-10: CVE-2016-1885: incorrect argument validation in sysarch(2))

2016-03-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Mar 2016 23:25:31 + with message-id and subject line Bug#818426: fixed in kfreebsd-10 10.3~svn296998-1 has caused the Debian Bug report #818426, regarding kfreebsd-10: CVE-2016-1885: incorrect argument validation in sysarch(2) to be marked as done. This means that

Bug#818777: kfreebsd-10: non-standard gcc/g++ used for build (gcc-4.9)

2016-03-20 Thread Steven Chamberlain
tags 818777 + pending thanks Fix pending in SVN r5955, which will go into experimental first and then sid within a few weeks. Not really an issue anyway since Clang is used instead of GCC on the arches that really exist at the moment. Regards, -- Steven Chamberlain ste...@pyro.eu.org signatur

Processed: Re: Bug#818777: kfreebsd-10: non-standard gcc/g++ used for build (gcc-4.9)

2016-03-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 818777 + pending Bug #818777 [kfreebsd-10] kfreebsd-10: non-standard gcc/g++ used for build (gcc-4.9) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 818777: http://bugs.debian.o

Bug#818777: kfreebsd-10: non-standard gcc/g++ used for build (gcc-4.9)

2016-03-20 Thread Matthias Klose
Package: kfreebsd-10 Version: 10.1~svn274115-10 Severity: important Tags: sid stretch User: debian-...@lists.debian.org Usertags: non-standard-compiler, gcc-4.9, gcc-4.9-legacy This package builds with a non standard compiler version; please check if this package can be built with the default

Bug#818743: kfreebsd-10: Increase ARG_MAX to match the one from Linux

2016-03-20 Thread Steven Chamberlain
forwarded 818743 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208154 tags 818743 + moreinfo severity 818743 wishlist thanks Hi, Jon Boden wrote: > ARG_MAX is too small for building LibreOffice (errors out with > "Argument list too long"). [...] > I suggest increasing it to match with the Lin

Processed: Re: Bug#818743: kfreebsd-10: Increase ARG_MAX to match the one from Linux

2016-03-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 818743 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208154 Bug #818743 [kfreebsd-10] kfreebsd-10: Increase ARG_MAX to match the one from Linux Set Bug forwarded-to-address to 'https://bugs.freebsd.org/bugzilla/show_bu

Bug#818743: kfreebsd-10: Increase ARG_MAX to match the one from Linux

2016-03-20 Thread Jon Boden
Package: kfreebsd-10 Version: 10.3~svn296373-2 ARG_MAX is too small for building LibreOffice (errors out with "Argument list too long"). This was found when attempting to build LibreOffice on ubuntuBSD. I suggest increasing it to match with the Linux value: $ getconf ARG_MAX 2097152

Bug#818426: kfreebsd-10: CVE-2016-1885: incorrect argument validation in sysarch(2)

2016-03-19 Thread Steven Chamberlain
kfreebsd-10, and also kfreebsd-9 in wheezy. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 10.1-0-amd64 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.

Bug#818423: marked as done (kfreebsd-10: CVE-2016-1883: Linux compatibility layer issetugid(2) system call vulnerability)

2016-03-19 Thread Debian Bug Tracking System
Your message dated Thu, 17 Mar 2016 03:59:34 + with message-id and subject line Bug#818423: fixed in kfreebsd-10 10.1~svn274115-4+kbsd8u3 has caused the Debian Bug report #818423, regarding kfreebsd-10: CVE-2016-1883: Linux compatibility layer issetugid(2) system call vulnerability to be

Bug#818423: kfreebsd-10: CVE-2016-1883: Linux compatibility layer issetugid(2) system call vulnerability

2016-03-19 Thread Steven Chamberlain
ebian GNU/kFreeBSD unless the system administrator has enabled it. https://security.FreeBSD.org/advisories/FreeBSD-SA-16:10.linux.asc This affects kfreebsd-10, and also kfreebsd-9 in wheezy. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unst

Bug#818426: marked as done (kfreebsd-10: CVE-2016-1885: incorrect argument validation in sysarch(2))

2016-03-19 Thread Debian Bug Tracking System
Your message dated Thu, 17 Mar 2016 03:59:34 + with message-id and subject line Bug#818426: fixed in kfreebsd-10 10.1~svn274115-4+kbsd8u3 has caused the Debian Bug report #818426, regarding kfreebsd-10: CVE-2016-1885: incorrect argument validation in sysarch(2) to be marked as done. This

Processed: Re: Bug#818426: kfreebsd-10: CVE-2016-1885: incorrect argument validation in sysarch(2)

2016-03-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 818426 - patch + security Bug #818426 [src:kfreebsd-10] kfreebsd-10: CVE-2016-1885: incorrect argument validation in sysarch(2) Removed tag(s) patch. Bug #818426 [src:kfreebsd-10] kfreebsd-10: CVE-2016-1885: incorrect argument validat

kfreebsd-10 is marked for autoremoval from testing

2016-02-14 Thread Debian testing autoremoval watch
kfreebsd-10 10.1~svn274115-10 is marked for autoremoval from testing on 2016-02-15 It is affected by these RC bugs: 811277: kfreebsd-10: CVE-2016-1879: SCTP ICMPv6 error message vulnerability [SA-16:01] 811278: kfreebsd-10: CVE-2016-1880: Linux compatibility layer incorrect futex handling [SA

Processed: Re: Bug#813727: kfreebsd-10: update clang version

2016-02-08 Thread Debian Bug Tracking System
Processing control commands: > block -1 by 806241 Bug #813727 [src:kfreebsd-10] kfreebsd-10: update clang version 813727 was not blocked by any bugs. 813727 was blocking: 812778 Added blocking bug(s) of 813727: 806241 -- 813727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813727 Debian

Re: Bug#813727: kfreebsd-10: update clang version

2016-02-08 Thread Steven Chamberlain
Control: block -1 by 806241 Hi, Esa Peuha wrote: > Currently freebsd-10 build-depends on clang-3.5 which is going to be > removed (see bug #812778), so please update to a newer version. kfreebsd-10 should build okay with clang-3.6, except that bug #806241 prevents us from switching yet.

Processed: kfreebsd-10: update clang version

2016-02-04 Thread Debian Bug Tracking System
Processing control commands: > block 812778 by -1 Bug #812778 [ftp.debian.org] RM: llvm-toolchain-3.5 -- ROM; Old version 812778 was not blocked by any bugs. 812778 was not blocking any bugs. Added blocking bug(s) of 812778: 813727 -- 812778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=8127

Bug#813727: kfreebsd-10: update clang version

2016-02-04 Thread Esa Peuha
Source: kfreebsd-10 Control: block 812778 by -1 Currently freebsd-10 build-depends on clang-3.5 which is going to be removed (see bug #812778), so please update to a newer version.

kfreebsd-10 is marked for autoremoval from testing

2016-01-24 Thread Debian testing autoremoval watch
kfreebsd-10 10.1~svn274115-10 is marked for autoremoval from testing on 2016-02-15 It is affected by these RC bugs: 811277: kfreebsd-10: CVE-2016-1879: SCTP ICMPv6 error message vulnerability [SA-16:01] 811280: kfreebsd-10: CVE-2016-1882: TCP MD5 signature denial of service [SA-16:05] 811278

Bug#811279: marked as done (kfreebsd-10: CVE-2016-1881: Linux compatibility layer setgroups(2) system call vulnerability [SA-16:04])

2016-01-18 Thread Debian Bug Tracking System
Your message dated Tue, 19 Jan 2016 01:34:20 + with message-id and subject line Bug#811279: fixed in kfreebsd-10 10.1~svn274115-4+kbsd8u2 has caused the Debian Bug report #811279, regarding kfreebsd-10: CVE-2016-1881: Linux compatibility layer setgroups(2) system call vulnerability [SA-16:04

Bug#811282: marked as done (kfreebsd-10: Invalid TCP checksums with pf(4) [EN-16:02])

2016-01-18 Thread Debian Bug Tracking System
Your message dated Tue, 19 Jan 2016 01:34:20 + with message-id and subject line Bug#811282: fixed in kfreebsd-10 10.1~svn274115-4+kbsd8u2 has caused the Debian Bug report #811282, regarding kfreebsd-10: Invalid TCP checksums with pf(4) [EN-16:02] to be marked as done. This means that you

Bug#811280: marked as done (kfreebsd-10: CVE-2016-1882: TCP MD5 signature denial of service [SA-16:05])

2016-01-18 Thread Debian Bug Tracking System
Your message dated Tue, 19 Jan 2016 01:34:20 + with message-id and subject line Bug#811280: fixed in kfreebsd-10 10.1~svn274115-4+kbsd8u2 has caused the Debian Bug report #811280, regarding kfreebsd-10: CVE-2016-1882: TCP MD5 signature denial of service [SA-16:05] to be marked as done. This

Bug#811277: marked as done (kfreebsd-10: CVE-2016-1879: SCTP ICMPv6 error message vulnerability [SA-16:01])

2016-01-18 Thread Debian Bug Tracking System
Your message dated Tue, 19 Jan 2016 01:34:20 + with message-id and subject line Bug#811277: fixed in kfreebsd-10 10.1~svn274115-4+kbsd8u2 has caused the Debian Bug report #811277, regarding kfreebsd-10: CVE-2016-1879: SCTP ICMPv6 error message vulnerability [SA-16:01] to be marked as done

Bug#811278: marked as done (kfreebsd-10: CVE-2016-1880: Linux compatibility layer incorrect futex handling [SA-16:03])

2016-01-18 Thread Debian Bug Tracking System
Your message dated Tue, 19 Jan 2016 01:34:20 + with message-id and subject line Bug#811278: fixed in kfreebsd-10 10.1~svn274115-4+kbsd8u2 has caused the Debian Bug report #811278, regarding kfreebsd-10: CVE-2016-1880: Linux compatibility layer incorrect futex handling [SA-16:03] to be marked

Processed: Re: Bug#811281: kfreebsd-10: filemon and bmake meta-mode stability issues [EN-16:01]

2016-01-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 811281 kfreebsd-10/10.1~svn274115-4+kbsd8u1 Bug #811281 {Done: Steven Chamberlain } [src:kfreebsd-10] kfreebsd-10: filemon and bmake meta-mode stability issues [EN-16:01] No longer marked as found in versions kfreebsd-10/10.1~svn274

Bug#811281: marked as done (kfreebsd-10: filemon and bmake meta-mode stability issues [EN-16:01])

2016-01-17 Thread Debian Bug Tracking System
Your message dated Mon, 18 Jan 2016 02:23:10 + with message-id <20160118022309.gd17...@pyro.eu.org> and subject line Re: Bug#811281: kfreebsd-10: filemon and bmake meta-mode stability issues [EN-16:01] has caused the Debian Bug report #811281, regarding kfreebsd-10: filemon and bmak

Processed: Re: Bug#811278: kfreebsd-10: CVE-2016-1880: Linux compatibility layer incorrect futex handling [SA-16:03]

2016-01-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 811278 kfreebsd-10: CVE-2016-1880: Linux compatibility layer > incorrect futex handling [SA-16:03] Bug #811278 [src:kfreebsd-10] kfreebsd-10: CVE-2016-1880: Linux compatibility layer incorrect futex handling [SA-16:02] Changed Bug

Bug#811282: kfreebsd-10: Invalid TCP checksums with pf(4) [EN-16:02]

2016-01-17 Thread Steven Chamberlain
g TCP checksum on outgoing packets, when used with certain NICs, likely causing connection problems or reduced performance: https://www.freebsd.org/security/advisories/FreeBSD-EN-16:02.pf.asc This affects kfreebsd-10, and kfreebsd-9 in wheezy.

Processed: kfreebsd-10: Invalid TCP checksums with pf(4) [EN-16:02]

2016-01-17 Thread Debian Bug Tracking System
Processing control commands: > found -1 10.1~svn274115-10 Bug #811282 [src:kfreebsd-10] kfreebsd-10: Invalid TCP checksums with pf(4) [EN-16:02] Marked as found in versions kfreebsd-10/10.1~svn274115-10. -- 811282: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811282 Debian Bug Track

  1   2   3   4   >