https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254120
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|emulat...@freebsd.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248659
--- Comment #24 from Sreehari S ---
Yeah I can confirm that disabling hardware p-states is *not* an ideal solution
to this problem, but it is all we can do until we figure out what difference
FreeBSD's hardware P-state handling has that
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248659
Sreehari S changed:
What|Removed |Added
CC||sreeharisreed...@gmail.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254120
Bug ID: 254120
Summary: Linuxulator: getcwd returns ENOMEM instead of ERANGE
Product: Base System
Version: Unspecified
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254091
--- Comment #9 from Ed Maste ---
I posted a possible first step in https://reviews.freebsd.org/D29123
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254112
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|emulat...@freebsd.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254091
--- Comment #8 from Ed Maste ---
As far as I can tell there is no compatible way to specify no backup extension
(between GNU and current FreeBSD sed), but we could have FreeBSD sed handle
both -i and -i '' (assuming that there's no
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254110
--- Comment #4 from Kyle Evans ---
(In reply to Bob Bishop from comment #3)
Right, but we've never done what our docs say and neither has anyone else, so
we risk breaking grep invocations that rely on GNU or legacy bsdgrep behavior.
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254110
--- Comment #3 from Bob Bishop ---
(In reply to Kyle Evans from comment #2)
gnugrep reports it as an error and the respective man pages describe the
different behaviours accurately so I don't think there's much danger of POLA
violation.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253724
--- Comment #9 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=bdd61b6914f1f961b5f414b2d5cc623a5a829b89
commit bdd61b6914f1f961b5f414b2d5cc623a5a829b89
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254110
Kyle Evans changed:
What|Removed |Added
CC||b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254092
--- Comment #1 from Ed Maste ---
Looks like a reasonable addition to me.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254091
Kyle Evans changed:
What|Removed |Added
CC||kev...@freebsd.org
--- Comment #7
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254114
Bernhard Froehlich changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254114
--- Comment #1 from Bernhard Froehlich ---
Created attachment 223075
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223075=edit
info
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254114
Bug ID: 254114
Summary: if_wg(4): panic on second ifconfig wg0 up
Product: Base System
Version: Unspecified
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254112
--- Comment #1 from JavaShin ---
https://us.images.linuxcontainers.org/images/
Opensuse Tumbleweed And ArchLinux Tested Happens The Same Glibc Version 2.33
On Debian Sid Works Fine Like CentOS C7.
(*) Continue
- mkdir /compat/distro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254112
Bug ID: 254112
Summary: Linuxulator: glibc's 2.33 with glibc-hwcaps distros
breaks compat
Product: Base System
Version: Unspecified
Hardware: Any
OS:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254110
--- Comment #1 from Bob Bishop ---
cf. bug #254091
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254110
Bug ID: 254110
Summary: grep/bsdgrep(1) -C/--context doesn't behave as
advertised
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254103
--- Comment #1 from dave ---
FreeBSD server 12.2-RELEASE-p4 FreeBSD 12.2-RELEASE-p4 GENERIC i386
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254103
Bug ID: 254103
Summary: periodic.conf doesn't read rc.conf parameters
correctly
Product: Base System
Version: 12.2-RELEASE
Hardware: amd64
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254102
Bug ID: 254102
Summary: fstyp: Sync HAMMER1/2 support with the latest
DragonFly BSD
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254091
--- Comment #6 from Tobias Kortkamp ---
(In reply to Li-Wen Hsu from comment #5)
Yes, of course. Tests and a lot of other scripts too. But I think
preemptively working on that might be a waste of time unless multiple
people think this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254091
--- Comment #5 from Li-Wen Hsu ---
(In reply to Tobias Kortkamp from comment #4)
No, that build is what in the -CURRENT now. If there are tests about -i
running, then the current sed behavior matches the tests. So if we change
(fix) the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254101
Bug ID: 254101
Summary: release/release.sh: Release products aren't updated at
2nd or later build
Product: Base System
Version: CURRENT
Hardware: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254091
--- Comment #4 from Tobias Kortkamp ---
(In reply to Li-Wen Hsu from comment #3)
I'm confused. Is that build with the patch applied? That can't be right.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254091
--- Comment #3 from Li-Wen Hsu ---
(In reply to Tobias Kortkamp from comment #2)
Hmm, there is no usr.bin/sed test failing currently:
https://ci.freebsd.org/job/FreeBSD-main-amd64-test/17760/testReport/usr.bin.sed/
So we might need to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254091
--- Comment #2 from Tobias Kortkamp ---
(In reply to Li-Wen Hsu from comment #1)
What test should be added? There are test cases for -i in the test suite
already AFAICT. Obviously all of them are broken now because of the behavior
change
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254091
Li-Wen Hsu changed:
What|Removed |Added
CC||lw...@freebsd.org
--- Comment #1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254098
RodrigoC changed:
What|Removed |Added
Summary|Selected keymap on |Selected keymap on
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254098
Bug ID: 254098
Summary: Selected keymap on bsdinstall is not added in rc.conf
on new installation
Product: Base System
Version: 13.0-STABLE
Hardware: amd64
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254092
Bug ID: 254092
Summary: libc: Please implement get_current_dir_name()
Product: Base System
Version: Unspecified
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241697
Andre Albsmeier changed:
What|Removed |Added
CC||m...@fbsd2.e4m.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254091
Bug ID: 254091
Summary: sed: Please fix -i behavior
Product: Base System
Version: Unspecified
Hardware: Any
OS: Any
Status: New
Severity: Affects
36 matches
Mail list logo
