Very unimpressed with the so called "fix" for #842145 of just blocking
running the script on nfs mount rather than fixing the script to work
properly with nfs.
The problem with the script is that it does not ignore the .nfs*
files. An explanation of these files is available here:
https://unix.sta
Hi Sven,
On Sat, Oct 07, 2023 at 09:09:27AM +0200, Sven Joachim wrote:
> On 2023-10-06 22:32 +, Andy Smith wrote:
> > It got done years ago in Ubuntu, and their dpkg doesn't have this
> > issue, as they've carried patches for that for all those years.
>
> Ubuntu may have patched out the dpkg
On 2023-10-06 22:32 +, Andy Smith wrote:
> On Fri, Oct 06, 2023 at 04:42:56PM +0200, Urs Thuermann wrote:
>> Greg Wooledge writes:
>>
>> > Yeah, usrmerge is a bit wonky in these early stages.
>>
>> $ apt-get changelog usrmerge | tail -n2
>> -- Marco d'Itri Tue, 04 Nov 2014 22:42:44
Hello,
On Fri, Oct 06, 2023 at 04:42:56PM +0200, Urs Thuermann wrote:
> Greg Wooledge writes:
>
> > Yeah, usrmerge is a bit wonky in these early stages.
>
> $ apt-get changelog usrmerge | tail -n2
> -- Marco d'Itri Tue, 04 Nov 2014 22:42:44 +0100
> Fetched 11.0 kB in 0s (58.9 k
Greg Wooledge writes:
> Yeah, usrmerge is a bit wonky in these early stages.
$ apt-get changelog usrmerge | tail -n2
-- Marco d'Itri Tue, 04 Nov 2014 22:42:44 +0100
Fetched 11.0 kB in 0s (58.9 kB/s)
Not what I'd call 'early' stages.
> Part of the reason for this is that it's n
Marco writes:
> Am 06.10.2023 schrieb Steve Keller :
>
> > I have always been sceptical about /usr merge, since all binaries now
> > appear in two places, "type sh" in bash gives the strange looking
> > /usr/bin/sh where all Uni*ers are strongly used to /bin/sh. But also
> > things like the fol
On Fri, Oct 06, 2023 at 11:06:56AM +0200, Steve Keller wrote:
> $ dpkg -S $(type -p sh)
> dpkg-query: no path found matching pattern /usr/bin/sh
>
> And I don't see a comfortable way around this.
Yeah, usrmerge is a bit wonky in these early stages. Part of the reason
for this is that it'
Am 06.10.2023 schrieb Steve Keller :
> I have upgraded from bullseye to bookworm and it seems the package
> usrmerge is installed forcedly now. At least it has been installed
> and I haven't been asked about it :-(
>
> I have always been sceptical about /usr merge, since all binaries now
> appea
On Thu, 14 Sep 2023 22:17:35 +0200
Marco wrote:
> If I screw with this I'd prefer to do it at night or on a weekend to
> keep the systems running during business hours.
Followup:
I went through the list and resolved each conflict manually. I
launched usrmerge after every change and deleted/merg
On Fri, 15 Sep 2023 17:55:06 +
Andy Smith wrote:
> I haven't followed this thread closely, but is my understanding
> correct:
>
> - You have a FreeBSD NFS server with an export that is a root
> filesystem of a Debian 11 install shared by multiple clients
Almost. It's not *one* Debian inst
Hello,
On Fri, Sep 15, 2023 at 01:52:27PM +0200, Marco wrote:
> On Thu, 14 Sep 2023 16:43:09 -0400
> Dan Ritter wrote:
> > Each of these things could be rewritten to be compatible with
> > FreeBSD; I suspect it would take about twenty minutes to an hour,
> > most of it testing, for someone who wa
> So the file in /lib appears to be newer. So what to do? Can I delete
> the one in /usr/lib ?
Yes.
Stefan
On Thu, 14 Sep 2023 16:54:27 -0400
Stefan Monnier wrote:
> Still going on with this?
I am.
> Have you actually looked at those two files:
>
> /lib/udev/rules.d/60-libsane1.rules and
> /usr/lib/udev/rules.d/60-libsane1.rules
>
> to see if they're identical or not and to see if you might ha
On Thu, 14 Sep 2023 16:43:09 -0400
Dan Ritter wrote:
> The heart of the convert-usrmerge perl script is pretty
> reasonable. However:
>
> […]
>
> Similarly, there are calls to stat and du which probably have
> some incompatibilities.
>
> The effect of running this would be fairly safe, but als
Still going on with this?
Have you actually looked at those two files:
/lib/udev/rules.d/60-libsane1.rules and
/usr/lib/udev/rules.d/60-libsane1.rules
to see if they're identical or not and to see if you might have an idea
how to merge them?
[ as I suggested a week ago. ]
`usrmerge` did g
On Thu, 14 Sep 2023 15:01:50 -0400
Dan Ritter wrote:
> Is this a mission-critical server?
I'd say so, yes. It's not one single server. It's *all*
workstations.
> i.e. will screwing it up for a day cause other people to be upset
Yes, because no one can use their computer.
> or you to lose mone
On Thu, 14 Sep 2023 13:20:09 -0400
Dan Ritter wrote:
> > FreeBSD (actually a TrueNAS appliance)
>
> If it supports the 9P share system, Debian can mount that with
> -t 9p.
>
> I don't know whether TrueNAS enabled that.
No it does not. I just confirmed, the only choices are raw disk
access (Z
On Thu, 14 Sep 2023 11:00:17 -0400
Dan Ritter wrote:
> What VM software are you using
bhyve
…which I know very little about. It's supported on the server, I've
tried it, set up a VM, it works. But the server is mainly serving
NFS shares to various clients.
> and what's the OS on which that run
Marco wrote:
> On Fri, 8 Sep 2023 12:26:38 -0400
> Dan Ritter wrote:
> > * have the VM mount the filesystem directly
>
> How? I can only attach devices (=whole disks) to the VM or mount the
> FS via NFS. I can't attach it as a device because it's not a device,
> rather than a directory with the
On Fri, 8 Sep 2023 12:26:38 -0400
Dan Ritter wrote:
> Can you start a temporary VM directly on the server?
I just checked. I can, yes.
> If so, you can
> * stop your remote Debian machine
Ok, no problem.
> * run a Debian rescue image in the VM on the NFS server
No problem.
> * have the VM m
Hello,
El dom., 10 sept. 2023 21:55, Marco escribió:
> On Fri, 8 Sep 2023 12:26:38 -0400
> Dan Ritter wrote:
>
> > > That is quite an involved task. I didn't expect such fiddling for a
> > > simple OS update. I'm a bit worried that the permissions and owners
> > > go haywire when I copy stuff d
On Fri, 8 Sep 2023 12:26:38 -0400
Dan Ritter wrote:
> > That is quite an involved task. I didn't expect such fiddling for a
> > simple OS update. I'm a bit worried that the permissions and owners
> > go haywire when I copy stuff directly off the server onto a VM and
> > back onto the server. Is t
> root@foobar:~# /usr/lib/usrmerge/convert-usrmerge
>
> FATAL ERROR:
> Both /lib/udev/rules.d/60-libsane1.rules and
> /usr/lib/udev/rules.d/60-libsane1.rules exist.
The problem is that "usrmerge" needs to unify those two and doesn't
know how. So you need to do it by hand.
E.g. get rid of
On Fri, 8 Sep 2023 16:55:23 +0200
zithro wrote:
> On 08 Sep 2023 12:54, Marco wrote:
> >Warning: NFS detected, /usr/lib/usrmerge/convert-usrmerge will
> > not be run automatically. See #842145 for details.
>
> Read :
> - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842145
“I repeat
On 08 Sep 2023 12:54, Marco wrote:
Warning: NFS detected, /usr/lib/usrmerge/convert-usrmerge will not be run
automatically. See #842145 for details.
Read :
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842145
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039522
The solution
On 2022-10-28 15:49, Tim Woodall wrote:
On Fri, 28 Oct 2022, Tim Woodall wrote:
Top post:
try installing usr-is-merged after changing sources.list before
anything else.
If that works and nobody else chimes in first I'll explain what is
going
on.
(may or may not work, no time to check now)
What you said about overlayfs is true and usrmerge is imho giving a
rather clear error message.
That said, I thought the best practice for docker containers is to throw
them away and rebuild them and that upgrading containers is frowned upon?
If you build / pull a new bookworm docker containe
On Fri, 28 Oct 2022, Tim Woodall wrote:
Top post:
try installing usr-is-merged after changing sources.list before
anything else.
If that works and nobody else chimes in first I'll explain what is going
on.
(may or may not work, no time to check now)
Tim.
To followup here:
If the docker
Top post:
try installing usr-is-merged after changing sources.list before
anything else.
If that works and nobody else chimes in first I'll explain what is going
on.
(may or may not work, no time to check now)
Tim.
On Fri, 28 Oct 2022, Tim Woodall wrote:
On Thu, 27 Oct 2022, Hogren wrote
On Thu, 27 Oct 2022, Hogren wrote:
Anybody can help me or confirm me that it?s a bug and I need to open a bug
issue ?
#9 28.26 Preparing to unpack .../archives/usrmerge_33_all.deb ...
#9 28.28 Unpacking usrmerge (33) ...
#9 28.32 Setting up usrmerge (33) ...
#9 28.42 Warning: overlayfs dete
Le 27 octobre 2022 20:03:57 GMT+02:00, "Andrew M.A. Cater"
a écrit :
>On Thu, Oct 27, 2022 at 09:05:54AM -0400, Greg Wooledge wrote:
>> On Thu, Oct 27, 2022 at 06:55:12AM -0600, Charles Curley wrote:
>> > On Thu, 27 Oct 2022 09:47:39 +0200
>> > Hogren wrote:
>> >
>> > > RUN echo 'deb http://
On Thu, Oct 27, 2022 at 09:05:54AM -0400, Greg Wooledge wrote:
> On Thu, Oct 27, 2022 at 06:55:12AM -0600, Charles Curley wrote:
> > On Thu, 27 Oct 2022 09:47:39 +0200
> > Hogren wrote:
> >
> > > RUN echo 'deb http://deb.debian.org/debian testing main' >
> > > /etc/apt/sources.list
> >
> > I ha
On Thu, Oct 27, 2022 at 06:55:12AM -0600, Charles Curley wrote:
> On Thu, 27 Oct 2022 09:47:39 +0200
> Hogren wrote:
>
> > RUN echo 'deb http://deb.debian.org/debian testing main' >
> > /etc/apt/sources.list
>
> I haven't yet read the entire email, but this sticks out like a sore
> thumb. It is
On Thu, 27 Oct 2022 09:47:39 +0200
Hogren wrote:
> RUN echo 'deb http://deb.debian.org/debian testing main' >
> /etc/apt/sources.list
I haven't yet read the entire email, but this sticks out like a sore
thumb. It is almost certainly not what you want. This completely
obliterates your entire /et
Sent this earlier, but it doesn't show up on the list, so I must have
used 'reply to sender' instead of 'reply to list'... :(
Op 03-10-2022 om 15:30 schreef billium:
There was no failed or manual moves. usrmerge may have failed during
previous upgrades and I may not have noticed.
Please do not
On 03/10/2022 09:40, Frank wrote:
Op 02-10-2022 om 21:29 schreef billium:
/usr/bin /usr/lib* & /usr/sbin are directories
/lib/x86_64-linux-gnu & /usr/lib/x86_64-linux-gnu are directories
/lib/x86_64-linux-gnu/libc.so.6 /usr/lib/x86_64-linux-gnu/libc.so.6 are
both files
Before the fault occurr
Op 02-10-2022 om 21:29 schreef billium:
/usr/bin /usr/lib* & /usr/sbin are directories
/lib/x86_64-linux-gnu & /usr/lib/x86_64-linux-gnu are directories
/lib/x86_64-linux-gnu/libc.so.6 /usr/lib/x86_64-linux-gnu/libc.so.6 are
both files
Before the fault occurred I had made no changes (except ap
On 02/10/2022 20:09, Frank wrote:
Op 02-10-2022 om 19:12 schreef billium:
/bin, /lib(*) and /sbin are directories not links, sorry I did not make
that clear.
And the corresponding items in /usr? Also directories?
What about /lib/x86_64-linux-gnu/libc.so.6 and
/usr/lib/x86_64-linux-gnu/libc.so
Op 02-10-2022 om 19:12 schreef billium:
/bin, /lib(*) and /sbin are directories not links, sorry I did not make
that clear.
And the corresponding items in /usr? Also directories?
What about /lib/x86_64-linux-gnu/libc.so.6 and
/usr/lib/x86_64-linux-gnu/libc.so.6? Both files?
And /lib/x86_64-li
On 02/10/2022 18:19, Michael Stone wrote:
On Sun, Oct 02, 2022 at 06:12:45PM +0100, billium wrote:
may be I am idiot for keeping it so long since a re-install. I think
stretch was the install, and it is now on bookworm.
FYI, skipping releases is not supported; in future, go through each
rele
On Sun, Oct 02, 2022 at 06:12:45PM +0100, billium wrote:
may be I am idiot for keeping it so long since a re-install. I think
stretch was the install, and it is now on bookworm.
FYI, skipping releases is not supported; in future, go through each
release in order when upgrading. Whether that w
On 02/10/2022 15:32, Michael Biebl wrote:
On Sat, Oct 01, 2022 at 11:06:55AM +0100, billium wrote:
Since the last update to my debian testing I am unable to install
anything
or upgrade.
Setting up usrmerge (31) ...
FATAL ERROR:
Both /lib/x86_64-linux-gnu/libc.so.6 and
/usr/lib/x86_64-linux-g
On Sat, Oct 01, 2022 at 11:06:55AM +0100, billium wrote:
Since the last update to my debian testing I am unable to install anything
or upgrade.
Setting up usrmerge (31) ...
FATAL ERROR:
Both /lib/x86_64-linux-gnu/libc.so.6 and /usr/lib/x86_64-linux-gnu/libc.so.6
exist.
How did you arrive in t
On 01/10/2022 15:07, billium wrote:
Thanks for your time Greg
This occurred from updates only no installs for a while.
I did try moving some of the files and sym linking, then rebooting to
check, all worked (inc libc) but got bored doing it after about 30
times. I also tried sym linking /usr
Thanks for your time Greg
This occurred from updates only no installs for a while.
I did try moving some of the files and sym linking, then rebooting to
check, all worked (inc libc) but got bored doing it after about 30
times. I also tried sym linking /usr/bin and /usr/lib etc but it locked
On Sat, Oct 01, 2022 at 11:06:55AM +0100, billium wrote:
> Since the last update to my debian testing I am unable to install anything
> or upgrade.
>
> Setting up usrmerge (31) ...
>
> FATAL ERROR:
> Both /lib/x86_64-linux-gnu/libc.so.6 and /usr/lib/x86_64-linux-gnu/libc.so.6
> exist.
How did yo
46 matches
Mail list logo
