Control: reopen -1
Hi,
looks like this didn't work:
> https://buildd.debian.org/status/fetch.php?pkg=qt6-multimedia=powerpc=6.4.2-11=1705003199=0
Reopening the bug therefore.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`-GPG: 62FF 8A75 84E0
Source: freebsd-buildutils
Version: 10.3~svn296373-7.1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=freebsd-
buildutils=amd64=10.3%7Esvn296373-7.1%2Bb1=1710975960=0
create.c:233:12: error: implicit declaration of function ‘MD5File’
Source: graphviz
Version: 2.42.2-9
X-Debbugs-Cc: t...@mirbsd.de, debian-po...@lists.debian.org
librsvg has become extremely unportable, and so only a subset of
architectures have it:
amd64 arm64 armel armhf i386 mips64el ppc64el riscv64 s390x
loong64 powerpc ppc64 sparc64
Please whitelist the
On 3/14/24 06:53, Thorsten Glaser wrote:
Dixi quod…
Is there a chance your team could fork the old python-cryptography
source package (3.4.8-2) and do something like:
Apparently, pyopenssl needs to also be forked as it wraps the above
and, between 21.0.0-1 and 22.1.0-1, it began requiring
Dixi quod…
>Is there a chance your team could fork the old python-cryptography
>source package (3.4.8-2) and do something like:
Apparently, pyopenssl needs to also be forked as it wraps the above
and, between 21.0.0-1 and 22.1.0-1, it began requiring the rust
version of python-cryptography ☹
Source: fsverity-utils
Version: 1.5-1.1
Severity: important
Justification: RC for Debian-Ports
X-Debbugs-Cc: t...@mirbsd.de, debian-po...@lists.debian.org
Recent versions of fsverity-utils (larger than 1.4-1~exp1 anyway)
have a Build-Depends-Arch on pandoc; however, pandoc is an extremely
Jérémy Lal dixit:
>Anyone had experience with the version 3.3 to 38.0 migration ?
>Maybe the API didn't change that much.
We cannot go past 3.4 because newer versions (starting at 38)
have a hard dependency on rust stuff.
bye,
//mirabilos
--
Solange man keine schmutzigen Tricks macht, und ich
Le lun. 11 mars 2024 à 21:53, Thorsten Glaser a écrit :
> Jérémy Lal dixit:
>
> >While I'm very much concerned about architectures and compatibility,
> >it seems that for python-cryptography, it's a sinking boat:
> >The end of a very discussion dates from february, 2021 - 3 years ago:
>
Jérémy Lal dixit:
>While I'm very much concerned about architectures and compatibility,
>it seems that for python-cryptography, it's a sinking boat:
>The end of a very discussion dates from february, 2021 - 3 years ago:
>https://github.com/pyca/cryptography/issues/5771#issuecomment-775990406
Le lun. 11 mars 2024 à 20:17, Thorsten Glaser a écrit :
> Hi,
>
> we have still the situation that the current python-cryptography,
> having rather heavy rust ecosystem dependencies, cannot be built
> on some debian-ports architectures.
>
> This situation is not likely to go away:
>
> • some
Hi,
we have still the situation that the current python-cryptography,
having rather heavy rust ecosystem dependencies, cannot be built
on some debian-ports architectures.
This situation is not likely to go away:
• some ports are unlikely to meet the dependencies soon
• new ports won’t meet them
Source: freebsd-libs
Version: 10.3~svn296373-10
Tags: patch trixie sid
User: helm...@debian.org
Usertags: dep17m2
Hi,
we want to finalize the /usr-merge transition by moving all aliased
files from / to /usr via DEP17 to avoid negative consequences arising
from aliasing effects. Multiple packages
Package: libfreebsd-glue-0
Version: 0.2.22+nmu1
Tags: patch
User: helm...@debian.org
Usertags: dep17m2
Hi,
we want to finalize the /usr-merge transition by moving all aliased
files from / to /usr via DEP17 to avoid any negative effects arising
from aliasing. libfreebsd-glue-0 is involved,
Source: freebsd-buildutils
Version: 10.3~svn296373-7.1
Severity: wishlist
Tags: ftbfs patch
User: debian-loonga...@lists.debian.org
Usertags: loong64
Dear maintainers,
I have added e_machine judgment for loongarch in
src/usr.bin/elfdump/elfdump.c.
Reference,
/* Legal values for e_machine
Source: freebsd-glue
Severity: normal
X-Debbugs-Cc: zhan...@loongson.cn
Dear Maintainer,
Please modify gcc version for build, thanks!
I think the gcc version should not be fixed, but should be greater
than a certain version, unless the required features only exist on a
specific
Source: freebsd-glue
Version: 0.2.22+nmu1
Severity: wishlist
Tags: patch ftbfs
User: debian-loonga...@lists.debian.org
Usertags: loong64
Dear maintainers,
Compiling the freebsd-glue with a dependency on gcc-9, the build
dependency is not satisfied in several architectures such as riscv64,
Source: gtk4,librsvg
Severity: important
Tags: upstream help
X-Debbugs-Cc: debian-s...@lists.debian.org, debian-po...@lists.debian.org
gtk4 had a recent test failure regression on s390x and other big-endian
architectures like ppc64 (#1057782). I sent this upstream to
That's so cool Khush, I will try to build FreeBSD on Linux my self following
your tips ... I wish both projects grow a lot, from my personal point of view,
FreeBSD, Linux and also OpenBSD are the best operating systems in the world.
Best regards,
⢀⣴⠾⠻⢶⣦⠀ Carlos Saltos
⣾⠁⢠⠒⠀⣿⡁
On 19 Nov 2023, at 12:21, khush patil wrote:
>
> Hi Team,
>
> I have successfully freebsd on linux using llvm
>
> MAKEOBJDIRPREFIX=/home/kp/build tools/build/make.py --debug TARGET=amd64
> TARGET\_ARCH=amd64 --cross-bindir=/usr/lib/llvm-14/bin
>
> MAKEOBJDIRPREFIX=/home/kp/build
Hi Team,
I have successfully freebsd on linux using llvm
MAKEOBJDIRPREFIX=/home/kp/build tools/build/make.py --debug TARGET=amd64
TARGET\_ARCH=amd64 --cross-bindir=/usr/lib/llvm-14/bin
MAKEOBJDIRPREFIX=/home/kp/build tools/build/make.py -j 2 TARGET=amd64
TARGET\_ARCH=amd64 buildworld
Your message dated Sat, 7 Oct 2023 17:13:41 +0300
with message-id
and subject line kFreeBSD has been removed from Debian ports
has caused the Debian Bug report #736716,
regarding freebsd-manpages: Should be installed by default on kfreebsd-any
to be marked as done.
This means that you claim that
Control: tag -1 wontfix
> The crash also happens with libperl5.18 (5.18.0-1) on unstable/kfreebsd-amd64.
It's clear that not enough people care about kfreebsd and it's
practically dead. Let's close that bug before I have to reassign it to
the next PG major version yet again.
Christoph
Your message dated Tue, 8 Aug 2023 14:23:54 +0200
with message-id
and subject line Re: Bug#966370: bsdmainutils: 12.1.3 removal of lorder breaks
rdeps
has caused the Debian Bug report #964698,
regarding freebsd-libs: FTBFS: dpkg-gensymbols: error: some symbols or patterns
disappeared in the
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 07 Aug 2023 00:36:34 +0200
Source: freebsd-buildutils
Architecture: source
Version: 10.3~svn296373-7.1
Distribution: unstable
Urgency: medium
Maintainer: GNU/kFreeBSD
Your message dated Tue, 08 Aug 2023 02:48:56 +
with message-id
and subject line Bug#957230: fixed in freebsd-buildutils 10.3~svn296373-7.1
has caused the Debian Bug report #957230,
regarding freebsd-buildutils: ftbfs with GCC-10
to be marked as done.
This means that you claim that the
Your message dated Tue, 08 Aug 2023 02:48:56 +
with message-id
and subject line Bug#964527: fixed in freebsd-buildutils 10.3~svn296373-7.1
has caused the Debian Bug report #964527,
regarding freebsd-buildutils: replace transitional bsdmainutils dependency
to be marked as done.
This means
Your message dated Tue, 08 Aug 2023 02:48:56 +
with message-id
and subject line Bug#932512: fixed in freebsd-buildutils 10.3~svn296373-7.1
has caused the Debian Bug report #932512,
regarding freebsd-buildutils: Don't build against flex-old
to be marked as done.
This means that you claim that
freebsd-buildutils_10.3~svn296373-7.1_source.changes uploaded successfully to
localhost
along with the files:
freebsd-buildutils_10.3~svn296373-7.1.dsc
freebsd-buildutils_10.3~svn296373-7.1.debian.tar.xz
freebsd-buildutils_10.3~svn296373-7.1_source.buildinfo
Greetings,
Your Debian
Am 07.08.23 um 02:40 schrieb Bastian Germann:
I am uploading a NMU to fix this. The debdiff is attached.
Now with the correct debdiff. I mixed up the BTS addresses.diff -Nru freebsd-buildutils-10.3~svn296373/debian/changelog
freebsd-buildutils-10.3~svn296373/debian/changelog
---
I am uploading a NMU to fix this. The debdiff is attached.diff -Nru freebsd-glue-0.2.22/debian/changelog
freebsd-glue-0.2.22+nmu1/debian/changelog
--- freebsd-glue-0.2.22/debian/changelog2016-03-05 16:44:54.0
+0100
+++ freebsd-glue-0.2.22+nmu1/debian/changelog 2023-08-07
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 07 Aug 2023 01:20:16 +0200
Source: freebsd-glue
Architecture: source
Version: 0.2.22+nmu1
Distribution: unstable
Urgency: medium
Maintainer: GNU/kFreeBSD Maintainers
freebsd-glue_0.2.22+nmu1_source.changes uploaded successfully to localhost
along with the files:
freebsd-glue_0.2.22+nmu1.dsc
freebsd-glue_0.2.22+nmu1.tar.xz
freebsd-glue_0.2.22+nmu1_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Your message dated Mon, 07 Aug 2023 00:48:56 +
with message-id
and subject line Bug#964661: fixed in freebsd-glue 0.2.22+nmu1
has caused the Debian Bug report #964661,
regarding freebsd-glue: FTBFS: dpkg-gensymbols: error: some symbols or patterns
disappeared in the symbols file: see diff
I am uploading a NMU to fix this. The debdiff is attached.diff -Nru freebsd-glue-0.2.22/debian/changelog
freebsd-glue-0.2.22+nmu1/debian/changelog
--- freebsd-glue-0.2.22/debian/changelog2016-03-05 16:44:54.0
+0100
+++ freebsd-glue-0.2.22+nmu1/debian/changelog 2023-08-07
Version: 10.3~svn300087+ds1-1+rm
Dear submitter,
as the package kfreebsd-10 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
kfreebsd-10 | 10.3~svn300087+ds1-1 | source
kfreebsd-source-10.3 | 10.3~svn300087+ds1-1 | all
--- Reason ---
RoQA; useless, unmaintained, has RC bug
Version: 11.0~svn295083-1~debug2+rm
Dear submitter,
as the package kfreebsd-11 has just been removed from the Debian archive
experimental we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see
We believe that the bug you reported is now fixed; the following
package(s) have been removed from experimental:
kfreebsd-11 | 11.0~svn265310-1 | source
kfreebsd-11 | 11.0~svn295083-1~debug2 | source
kfreebsd-image-11-486 | 11.0~svn265310-1 | i386
kfreebsd-image-11-686 | 11.0~svn265310-1 | i386
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 problem has
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 #877903,
regarding CVE-2017-15037
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
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
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 #842272,
regarding should flush timestamps early enough
to be marked as done.
This means that you claim that the problem has been
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
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 #823983,
regarding kfreebsd-10.3: hangs at boot mounting root ZFS pool
to be marked as done.
This means that you claim that the
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
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
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
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 #785196,
regarding kfreebsd-image-10-amd64: Console has no output in qemu -display curses
to be marked as done.
This means that you
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 #779001,
regarding kfreebsd-image-10.1-0-amd64: virtio-balloon does not work/VM
allocates complete memory on start up
to be marked as
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 #758084,
regarding kfreebsd-image-amd64 lacks support for i210 ethernet
to be marked as done.
This means that you claim that the
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
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 #729746,
regarding MAXLOGNAME increased (17 -> 32)
to be marked as done.
This means that you claim that the problem has been dealt
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 #705126,
regarding kfreebsd-9: maxproc limit exceeded, caused by sshd
to be marked as done.
This means that you claim that the
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 #684072,
regarding CVE-2011-2393
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
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
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 #644798,
regarding Interface naming in linprocfs
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Fri, 28 Jul 2023 16:46:28 +
with message-id
and subject line Bug#1041057: Removed package(s) from experimental
has caused the Debian Bug report #924390,
regarding kfreebsd mount missing libbsd.so.0 -> it is not installed.
to be marked as done.
This means that you claim
On Jul 22 2023, Rene Engelhard wrote:
> Hi,
>
> Am 22.07.23 um 16:09 schrieb Andreas Schwab:
>> On Jul 22 2023, Rene Engelhard wrote:
>>
>>> Am 22.07.23 um 15:53 schrieb Andreas Schwab:
On Jul 22 2023, Rene Engelhard wrote:
> Does opensuse have some public git/$VCS?
On Sat, Jul 22, 2023 at 8:10 AM Rene Engelhard wrote:
>
> Am 22.07.23 um 14:02 schrieb Andreas Schwab:
> > On Jun 18 2023, Rene Engelhard wrote:
> >
> >> For riscv64 I already pointed that out in the thread starting at
> >> https://lists.debian.org/debian-riscv/2023/06/msg0.html, but for the
Hi,
Am 22.07.23 um 16:09 schrieb Andreas Schwab:
On Jul 22 2023, Rene Engelhard wrote:
Am 22.07.23 um 15:53 schrieb Andreas Schwab:
On Jul 22 2023, Rene Engelhard wrote:
Does opensuse have some public git/$VCS?
On Jul 22 2023, Rene Engelhard wrote:
> Am 22.07.23 um 15:53 schrieb Andreas Schwab:
>> On Jul 22 2023, Rene Engelhard wrote:
>>
>>> Does opensuse have some public git/$VCS?
>> https://build.opensuse.org/package/live_build_log/openSUSE:Factory:RISCV/libreoffice/standard/riscv64
>
> Thanks...
>
>
On Jul 22 2023, Rene Engelhard wrote:
> Does opensuse have some public git/$VCS?
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:RISCV/libreoffice/standard/riscv64
> (Though I would more bet of some system evironment thingy)
Perhaps it is a matter of using a good java. Have
Am 22.07.23 um 15:53 schrieb Andreas Schwab:
On Jul 22 2023, Rene Engelhard wrote:
Does opensuse have some public git/$VCS?
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:RISCV/libreoffice/standard/riscv64
Thanks...
But maybe I am too blind.
I don't see the actual
Hi,
Am 22.07.23 um 15:07 schrieb Andreas Schwab:
Which gives the smoketest test failure here I pointed out (again) in my
other mail.
$ find /usr/lib64/libreoffice/ -name "*smoke*"
/usr/lib64/libreoffice/program/classes/smoketest.jar
How can I run that?
You can't from that, ttbomk. You miss
Hi,
Am 22.07.23 um 15:02 schrieb Andreas Schwab:
On Jul 22 2023, Rene Engelhard wrote:
https://lists.debian.org/debian-riscv/2023/07/msg00014.html is for manual
thing. And the IRC log shows that even libreoffice-lightproof-en etc don't
appear as bundled extensions.
$ unopkg list --bundled
On Jul 22 2023, Rene Engelhard wrote:
> Hi,
>
> Am 22.07.23 um 14:28 schrieb Andreas Schwab:
>> On Jul 22 2023, Rene Engelhard wrote:
>>
>>> Yes. _basically_. (Only with -O0 or maybe -Os as upstreams makefile says,
>>> though)
>> On openSUSE Factory, libreoffice is built with the usual compiler
On Jul 22 2023, Rene Engelhard wrote:
> https://lists.debian.org/debian-riscv/2023/07/msg00014.html is for manual
> thing. And the IRC log shows that even libreoffice-lightproof-en etc don't
> appear as bundled extensions.
$ unopkg list --bundled
All deployed bundled extensions:
Identifier:
On Jul 22 2023, Rene Engelhard wrote:
> And that includes LibreOffice-bundled extensions like the
> english,hungarian,russian grammar checker for example. Ot external finnish
> spellchecking, hyphenation and grammer checking. Or turkish spellchecing.
>
> And those are extensions written in python
On Jul 22 2023, Rene Engelhard wrote:
> Yes. _basically_. (Only with -O0 or maybe -Os as upstreams makefile says,
> though)
On openSUSE Factory, libreoffice is built with the usual compiler flags,
wich includes full optimisation and hardening.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key
On Jul 22 2023, Rene Engelhard wrote:
> Just not registering or unregistering *any* extension.
What does that mean? I haven't seen any errors about extensions.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for
Hi,
Am 22.07.23 um 14:34 schrieb Andreas Schwab:
On Jul 22 2023, Rene Engelhard wrote:
And that includes LibreOffice-bundled extensions like the
english,hungarian,russian grammar checker for example. Ot external finnish
spellchecking, hyphenation and grammer checking. Or turkish spellchecing.
Hi,
Am 22.07.23 um 14:28 schrieb Andreas Schwab:
On Jul 22 2023, Rene Engelhard wrote:
Yes. _basically_. (Only with -O0 or maybe -Os as upstreams makefile says,
though)
On openSUSE Factory, libreoffice is built with the usual compiler flags,
wich includes full optimisation and hardening.
Hi,
Am 22.07.23 um 14:25 schrieb Andreas Schwab:
On Jul 22 2023, Rene Engelhard wrote:
Just not registering or unregistering *any* extension.
What does that mean? I haven't seen any errors about extensions.
Do you run the testsuite?
Especially the smoketest?
And you are replying to
Hi,
Am 22.07.23 um 14:09 schrieb Rene Engelhard:
And that included packaged extensions so if they install but don't work
that's a grave bug.
And that includes LibreOffice-bundled extensions like the
english,hungarian,russian grammar checker for example. Ot external
finnish spellchecking,
On Jun 18 2023, Rene Engelhard wrote:
> For riscv64 I already pointed that out in the thread starting at
> https://lists.debian.org/debian-riscv/2023/06/msg0.html, but for the
> other architectures there is the mail now. riscv64 is different because
> the failures are even more big than any
Hi,
Am 22.07.23 um 14:02 schrieb Andreas Schwab:
On Jun 18 2023, Rene Engelhard wrote:
For riscv64 I already pointed that out in the thread starting at
https://lists.debian.org/debian-riscv/2023/06/msg0.html, but for the
other architectures there is the mail now. riscv64 is different
On Fri, Jul 21, 2023 at 06:14:04PM +1000, Finn Thain wrote:
>
> I'm not blaming the unstable API for the bugs, I'm blaming it for the
> workload. A stable API (like a userspace API) decreases the likelihood
> that overloaded maintainers have to orphan a filesystem implementation.
You are
On Fri, 21 Jul 2023, Matthew Wilcox wrote:
>
> You've misunderstood. Google have decided to subject the entire kernel
> (including obsolete unmaintained filesystems) to stress tests that it's
> never had before. IOW these bugs have been there since the code was
> merged. There's nothing to
On Fri, Jul 21, 2023 at 11:03:28AM +1000, Finn Thain wrote:
> On Fri, 21 Jul 2023, Dave Chinner wrote:
>
> > > I suspect that this is one of those catch-22 situations: distros are
> > > going to enable every feature under the sun. That doesn't mean that
> > > anyone is actually _using_ them
On Fri, 21 Jul 2023, Dave Chinner wrote:
> > I suspect that this is one of those catch-22 situations: distros are
> > going to enable every feature under the sun. That doesn't mean that
> > anyone is actually _using_ them these days.
I think the value of filesystem code is not just a question
On Thu, 20 Jul 2023 at 15:37, Matthew Wilcox wrote:
>
> I think you're missing the context. There are bugs in how this filesystem
> handles intentionally-corrupted filesystems. That's being reported as
> a critical bug because apparently some distributions automount HFS/HFS+
> filesystems
On Thu, Jul 20, 2023 at 05:38:52PM -0400, Jeffrey Walton wrote:
> On Thu, Jul 20, 2023 at 2:39 PM Matthew Wilcox wrote:
> >
> > On Thu, Jul 20, 2023 at 07:50:47PM +0200, John Paul Adrian Glaubitz wrote:
> > > > Then we should delete the HFS/HFS+ filesystems. They're orphaned in
> > > >
On Thu, Jul 20, 2023 at 02:27:50PM -0400, Jeff Layton wrote:
> On Thu, 2023-07-20 at 18:59 +0100, Matthew Wilcox wrote:
> > On Thu, Jul 20, 2023 at 07:50:47PM +0200, John Paul Adrian Glaubitz wrote:
> > > > Then we should delete the HFS/HFS+ filesystems. They're orphaned in
> > > > MAINTAINERS
On Thu, Jul 20, 2023 at 2:39 PM Matthew Wilcox wrote:
>
> On Thu, Jul 20, 2023 at 07:50:47PM +0200, John Paul Adrian Glaubitz wrote:
> > > Then we should delete the HFS/HFS+ filesystems. They're orphaned in
> > > MAINTAINERS and if distros are going to do such a damnfool thing,
> > > then we
On Thu, 2023-07-20 at 18:59 +0100, Matthew Wilcox wrote:
> On Thu, Jul 20, 2023 at 07:50:47PM +0200, John Paul Adrian Glaubitz wrote:
> > > Then we should delete the HFS/HFS+ filesystems. They're orphaned in
> > > MAINTAINERS and if distros are going to do such a damnfool thing,
> > > then we
On Thu, Jul 20, 2023 at 07:50:47PM +0200, John Paul Adrian Glaubitz wrote:
> > Then we should delete the HFS/HFS+ filesystems. They're orphaned in
> > MAINTAINERS and if distros are going to do such a damnfool thing,
> > then we must stop them.
>
> Both HFS and HFS+ work perfectly fine. And if
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 19 Jul 2023 11:59:49 +0200
Source: ctfutils
Architecture: source
Version: 10.3~svn297264-2.1
Distribution: unstable
Urgency: medium
Maintainer: GNU/kFreeBSD Maintainers
ctfutils_10.3~svn297264-2.1_source.changes uploaded successfully to localhost
along with the files:
ctfutils_10.3~svn297264-2.1.dsc
ctfutils_10.3~svn297264-2.1.debian.tar.xz
ctfutils_10.3~svn297264-2.1_source.buildinfo
Greetings,
Your Debian queue daemon (running on host
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: kfreebsd...@packages.debian.org
Control: affects -1 + src:kfreebsd-11
Hi,
With the removal of the kfreebsd-amd64 and kfreebsd-i386 architectures
from the debian-ports archive [1], it
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: kfreebsd...@packages.debian.org
Control: affects -1 + src:kfreebsd-10
Hi,
With the removal of the kfreebsd-amd64 and kfreebsd-i386 architectures
from the debian-ports archive [1], it
Dear all,
On 2023-05-29 18:11, Aurelien Jarno wrote:
> Dear GNU/kFreeBSD porters,
>
> Over the past year, GNU/kFreeBSD hasn't seen any significant
> development. After reaching out to various individuals involved, it
> seems unlikely that the situation will change in the foreseeable future.
>
On Mon, Jul 03, 2023 at 09:31:29PM +0200, Rene Engelhard wrote:
> Hi,
>
> Am 25.06.23 um 13:37 schrieb Rene Engelhard:
> > > what about the
> > > following:
> > > - make all test failures fatal on a*64 (since upstream tests these), and
> > > - make smoketest failures fatal on all architectures
Hi,
Am 03.07.23 um 21:31 schrieb Rene Engelhard:
Am 25.06.23 um 13:37 schrieb Rene Engelhard:
what about the
following:
- make all test failures fatal on a*64 (since upstream tests these), and
- make smoketest failures fatal on all architectures (including ports)
That was implemented (+ two
Hi,
Am 25.06.23 um 13:37 schrieb Rene Engelhard:
what about the
following:
- make all test failures fatal on a*64 (since upstream tests these), and
- make smoketest failures fatal on all architectures (including ports)
That was implemented (+ two more important tests) in experimental. See
Package: istgt
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
istgt has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked because
Hi,
Am 20.06.23 um 10:25 schrieb Adrian Bunk:
On Tue, Jun 20, 2023 at 05:52:44AM +0200, Rene Engelhard wrote:
Hi,
Am 19.06.23 um 23:29 schrieb Rene Engelhard:
The pragmatic option would be to run only a smoketest for build success
on architectures not tested by upstream.
And have
On Tue, 2023-06-20 at 22:46 +0200, Kurt Roeckx wrote:
> Can I suggest that if you file a few bugs and add some information in
> it so that maybe someone can look at it? If it only affects one
> architecture, send a mail to that list asking for help.
PS: when filing architecture-specific bugs,
Can I suggest that if you file a few bugs and add some information in it so
that maybe someone can look at it? If it only affects one architecture, send a
mail to that list asking for help.
Kurt
Hi,
Am 20.06.23 um 16:52 schrieb Kurt Roeckx:
On Tue, Jun 20, 2023 at 05:52:44AM +0200, Rene Engelhard wrote:
Hi,
Am 19.06.23 um 23:29 schrieb Rene Engelhard:
The pragmatic option would be to run only a smoketest for build success
on architectures not tested by upstream.
And have
On Tue, Jun 20, 2023 at 05:52:44AM +0200, Rene Engelhard wrote:
> Hi,
>
> Am 19.06.23 um 23:29 schrieb Rene Engelhard:
> > > The pragmatic option would be to run only a smoketest for build success
> > > on architectures not tested by upstream.
> >
> > And have Format->Character in Impress crash
1 - 100 of 15615 matches
Mail list logo
