Package: samba
Version: 4.22.0
Hi,
I am testing Debian Trixie, and I believe I have identified a regression
in the Samba server package.
Description
---
The issue has to do with the listing of shares containing files or
directories with names including special characters such as do
Hi David,
Thanks for clarifying the evolution of the php-gettext package. I have
indeed been using it more more than 10 years, so I wasn't aware that, in
that time, gettext had been formally integrated into PHP without
requiring a separate dependencies, and that the package also had gone
thro
Hi,
I'm trying to understand the context of this bug, as my current take on
this is that php-gettext is at risk of being removed from Trixie purely
on account that:
- There exists a *downstream* package (tt-rss, i.e. not an actual
dependency of php-gettext) that is posing a problem.
- The PH
Hello all and sorry for pinging in late into this conversation.
First of all, as someone who noticed the original issue but never got
around to properly report or investigate it, a big thanks go to the
people here who have been devoting time and effort trying to get to the
bottom of it, and of
t could be qualified as case sensitive.
I guess Pete Batard can give a more comprehensive list.
Well, once you eliminate the search of installation media by label
(which Debian doesn't do), the lack of symbolic links, which is what
we've been dealing with here, is actually the bigge
Hi James
On 2023.03.15 00:47, James Addison wrote:
The problem, in both cases, was that I hadn't copied the '.disk' dotfile
directory from the install media ISO filesystem(s) in each case.
Ah, yes, the infamous '.disk/' directory.
If it's any consolation, you're not the first person to stumbl
Package: debian-cd
Version: debian-testing-amd64-DVD.iso (2023.03.08)
This is a requested follow up to #1031696
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031696).
Besides essential installation packages using symlinks, the upcoming
bookworm also uses symlinks for non essential files
On 2023.03.13 12:16, Holger Levsen wrote:
what's FST? https://en.wikipedia.org/wiki/FST is not helpful.
File System Transposition.
It's in the title of this very bug report and after repeating it all
over the place for a while, I hope that using a shorthand for the term
is fine.
/Pete
Hi Steve,
On 2023.03.12 14:53, Steve McIntyre wrote:
It looks like James (with some help from Thomas) has worked out a
quick way to change things to make things better for you, which is
good! (Thanks, guys! I'm about to test the change locally.)
Yes, I'm happy to see this development as well.
words in my mouth
I don't. Let me re-quote the exchange:
On 2023.03.11 13:06, Cyril Brulebois wrote:
> Pete Batard (2023-03-11):
>> Again, I will point out that the goal is for users of any OS to be
>> able to bypass the need to use any external utility (and I'll remind
On 2023.03.11 13:06, Cyril Brulebois wrote:
That. is. not. a. change. from. Bullseye.
It is when you consider from a standpoint that an image created with
'dd' should perform the same in terms of being able to retrieve .deb
packages as one that is created through file system transposition.
Hi James,
> so the regression:
>
> * IS NOT that non-free firmware becomes unavailable when UEFI
> file transposition is used to create bootable drives
> -- because that firmware was not available previously
>
> * IS that bootable drives created using UEFI file transposition
> fro
Hi Cyril,
The regression, in my opinion, is that the standard release of bullseye
made sure that all the packages that may be required for a successful
installation would be available for users who did not create their media
using 'dd', whereas bookworm doesn't.
Whereas one could use file sy
Thanks for looking into this.
Just going to add, in case you wonder why it shouldn't be up to the
software that is mounting the ISO to sort out symbolic links and just
duplicate content, that neither Windows File Explorer nor 7-zip (both of
which can mount/extract ISO content) will list anythi
Please note that, since bookworm has started to include firmware files,
this issue is also starting to affect bookworm users [1] and I can only
advise Debian maintainers to raise its priority, rather than dismiss it
as something that will only affect folks who don't use DD mode to write
the ISO
Package: non-free
Version: firmware-11.6.0
Not sure if this is something that should be sent to the official bug
tracker, since it's an issue with cdimage/unofficial/non-free, but I
would like to report that the current cd-including-firmware images, such
as 'firmware-11.6.0-amd64-netinst.iso'
Hi Wookey,
Thanks a lot for looking into this!
On 2021.05.14 03:08, Wookey wrote:
I've done this, and if you want to test the mini.iso image at:
http://wookware.org/software/rpi4-test.iso
That would be good. (I don't have an rpi4 to test on)
Just tested it, and I can confirm it fixes the NI
For reference I have submitted a new pull request against src:linux that
attempts to fix this in
https://salsa.debian.org/kernel-team/linux/-/merge_requests/350
As people who monitor the Debian ARM64 mailing list should be aware,
this is a rather major issue, that people wanting to install Deb
I can try to submit a pull request for linux if needed, but I may need
some guidance.
I'm going to drop trying to submit a pull request for the linux package
for the time being, as I can't quite seem to manage to get the required
process to insert CONFIG_MDIO_BCM_UNIMAC=m where it should appea
On 2021.04.16 14:04, Ben Hutchings wrote:
On Thu, 2021-04-15 at 17:28 +0200, Samuel Thibault wrote:
Hello,
Pete Batard, le jeu. 15 avril 2021 16:11:02 +0100, a ecrit:
Quite a few people are negatively affected by this bug, and one can expect a
lot more to be if Debian 11 goes to release
Note that this is a rather critical regression (since it used to work
fine with previous bullseye ISOs), that is currently preventing
installation of Debian on the Raspberry Pi 4, i.e. by far the most
widespread ARM64 platform out there.
Quite a few people are negatively affected by this bug,
We confirm that this bug, which is a duplicate of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967918, can be closed
as we validated that the latest Debian testing netsint.iso resolves the
aforementioned issue.
Package: partman-efi
Severity: important
Tags: d-i
Logging a bug against this, since it's a rather important issue.
https://salsa.debian.org/installer-team/partman-efi/-/commit/1a096e6ede94cce8e5272e31946a506ae7f611e7.patch
had the rather unfortunate side effect of removing the +x attribute fro
Hi Adrian,
On 2020.08.05 07:48, John Paul Adrian Glaubitz wrote:
On 8/5/20 1:47 AM, Pete Batard wrote:
A patch for this issue has now been submitted in:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967918
A new report was created since we ultimately propose to fix
this in partman-efi
A patch for this issue has now been submitted in:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967918
A new report was created since we ultimately propose to fix this in
partman-efi instead of partman-auto.
As such so we would greatly appreciate if this patch could be
reviewed and applied quickly.
Thank you,
/Pete
From dff3328ce6243956254e1d71e7b72dc93ce0c103 Mon Sep 17 00:00:00 2001
From: Pete Batard
Date: Wed, 5 Aug 2020 00:12:40 +0100
Subject: [PATCH] Remount /cdrom read-write if it also hap
Since we haven't seen any progress or update on this from Debian, we're
sending a reminder that, as per https://github.com/pftf/RPi4/issues/76,
this issue is still very much active for us and an actual showstopper
for the installation of Debian 11 on the Pi 4, using the regular Debian
setup uti
On 2020.06.20 14:49, Andrei POPESCU wrote:
Control: reassign -1 debian-installer
On Vi, 19 iun 20, 18:36:33, Pete Batard wrote:
Package: partman
Severity: important
Tags: d-i
'partman' is not a "real" package, reassigning accordingly.
Ah yes, I found that after I o
Package: partman-auto
Severity: important
Tags: d-i
(NB: Resubmitting this bug, which was already submitted as
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963150, against
partman-auto since "partman" does not appear to exist as a valid Debian
package)
THE GOAL
When installin
Package: partman
Severity: important
Tags: d-i
THE GOAL
When installing Debian from the official netinst ISO in UEFI mode it may
be very convenient to do so by:
- Creating a large enough ESP (GPT or MBR) on the target installation
disk (e.g. 350 MB)
- Extracting the ISO content to sa
On 2020.05.09 22:20, Ben Hutchings wrote:
On Thu, 2020-05-07 at 14:23 +0100, Pete Batard wrote:
[...]
I specifically designed the patch I submitted for easy review and
integration, because there are missing elements from 4.x that are
present in 5.x, that we have to compensate for. I would
On 2020.05.07 13:45, Ben Hutchings wrote:
Also, there would be no point in enabling this driver in 4.19, only to
have people find on upgrade to the next version on Debian that we
didn't enable it there. That's why we're concerned with both versions.
Yes, I did consider that, but I feel that th
I would really like to get an update on this, because I really can't
understand what the holdup is, or why non related issues seem to be be
shoved into this bug, with the apparent end result of completely
distracting from the matter at hand.
This bug is about one thing and one thing only: Enab
Does that mean that the next Debian ISO installer will use Linux kernel
5.5.13.1 or later?
Because, if that is not the case, this bug is certainly not fixed at all
and must be reopened.
To reiterate, the problem is that the official netinst ISO cannot
perform a network installation of the De
Just going to point out that the 5.x equivalent patch has now been
applied to Linux mainline as per:
https://lkml.kernel.org/lkml/20200224.153146.125327154283545636.da...@davemloft.net/
Could we get some acknowledgement that this patchset is being looked at
for possible integration and isn't f
aspberry Pi Foundation
declares the network interface (though using it as such in a 4.19 kernel
will require the provision of the "brcm,max-dma-burst-size" attribute).
Signed-off-by: Pete Batard
---
.../net/ethernet/broadcom/genet/bcmgenet.c| 74 ++-
drive
Just gonna add that the latest UEFI Firmware, released today at
https://github.com/pftf/RPi4/releases, now contains all the elements
needed (ACPI binding and UMAC initialization) for the above patch to work.
Which means that, the only limiting factor for UEFI Debian 10.x netinst
on a Raspberry
9 kernel
will require the provision of the "brcm,max-dma-burst-size" attribute).
Signed-off-by: Pete Batard
---
.../net/ethernet/broadcom/genet/bcmgenet.c| 74 ++-
drivers/net/ethernet/broadcom/genet/bcmmii.c | 33 -
drivers/net/phy/mdio-bcm-unimac.c
Yes! At long last 231-6 seems to have cleared the systemd issue I was
observing on Raspberry Pi:
--
root@pi ~ # systemctl status
● pi
State: running
Jobs: 0 queued
Failed: 0 units
Okay.
I have logged issue #651
(https://github.com/raspberrypi/firmware/issues/651) with the rpi team
so that they try to sort their SECCOMP configuration in future kernels.
Regards,
/Pete
On 2016.08.30 17:30, Felipe Sateler wrote:
I managed to get the config from a jessie rpi by loading the 'configs'
module (sudo modprobe configs). After that the config is found on
/proc/config.gz
Yeah, I just discovered the same after I replied.
This is also documented on the official rpi githu
Thanks Felipe.
I guess with the new detection process, the resurgence of the issue is
starting to make sense now.
For the record, I am using one of the latest official Raspberry Pi
kernels from https://github.com/raspberrypi/firmware (which I get
indirectly through the https://github.com/Hex
Please find my boot log. Note that I've tried commenting out
'MemoryDenyWriteExecute=yes' in the various .service config files, but
it didn't help.
If you need anything else, please let me know.
Regards,
/Pete
[0.00] Booting Linux on physical CPU 0xf00
[0.00] Initializing cgro
On 2016.08.28 15:37, Felipe Sateler wrote:
Could you try 231-5 from unstable?
Oops, I mean 231-5 broke it. I'm seeing the issue back in 231-5 and not
231-4 as I mentioned earlier.
231-4 seemed to be okay, and it's only when I upgraded to 231-5 that the
problem reappeared.
Regards,
/Pete
...and 231-4 broke the whole thing down again. :(
Same error:
root@pi ~ # systemctl status systemd-journald.service
● systemd-journald.service - Journal Service
Loaded: loaded (/lib/systemd/system/systemd-journald.service;
s
Didn't fix it for me... :(
I went to an 'apt-get --reinstall install' of every single package that
is listed under 'Description' above (expect -udeb and -dev), and got the
231-2 version alright, but the issue remains exactly the same, even
after a full reboot.
I should point out that I did g
Okay. I have now gone through a dpkg -i install of all the (non dbgsym)
.deb I see on your server, and also issued a reboot for good measure,
but I still see the same problem with journald being failed, along with
dependent services
-
Thanks Felipe.
I installed libsystemd0_231-2_armhf.deb but shouldn't there be a
systemd_231-2_armhf.deb as well? Strangely there's a
systemd-dbgsym_231-2_armhf.deb but no non-dbgsym version, as opposed to
other .debs.
The .dsc does mention a 'systemd' binary, and earlier, the idea was to
in
Thanks Felipe.
I'm afraid it's still not completing successfully though:
../src/test/test-execute.c: In function ‘test_exec_systemcallfilter’:
../src/test/test-execute.c:120:14: error: implicit declaration of
function ‘is_seccomp_e
Since Rick hasn't replied, and I've been encountering the same issue on
a Raspberry Pi 2 model B running sid, I've been trying the steps
mentioned above.
However the post-build tests failed with the following:
-
test-
50 matches
Mail list logo
