On 08/03/2024 07:38, Rene Engelhard wrote:
Hi,
I did my part for example with this one, that maintainer denied first
but fixed later in his next upload as suggested...
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065349
Well, you haven't seen the various discussion how to fix smbclie
On 07/03/2024 21:16, Rene Engelhard wrote:
ct more people.
But not so much for dependency issues like this. Which is my sole point.
In 99,9% of cases this won't even migrate to testing. And unstable won't
be released - testing will.
What is your point? Without known bugs or new versions pack
On 07/03/2024 20:55, Rene Engelhard wrote:
unstable is unstable. Don't use it if you can't handle stuff like this.
And yes, be it even for more days or however it takes.
The usual mantra. However, if no one use unstable and debug it to make
it work correctly, maintainers will discover existi
On 07/03/2024 19:58, Rene Engelhard wrote:
I'm sure it will be done at some point. However, I just point out that
on amd64
Maybe, though in my sid VM with all tasks installed plasma-workspace
fails to upgrade, claiming about gdb-minmal | gdb not to be installed
whereas both of that install,
On 07/03/2024 18:57, Rene Engelhard wrote:
That one is tracked and will get appropriate bin-NMUs from the release
team, I am sure.
It is right that this uninstallability is "being part of the normal
things due to transition".
I'm sure it will be done at some point. However, I just point o
On 07/03/2024 07:25, Kevin Bowling wrote:
As of this evening these are the packages that currently have broken
deps on amd64 for me:
gstreamer1.0-plugins-good gstreamer1.0-pulseaudio
libkf5akonadisearch-bin libkf5akonadisearch-plugins occt-misc
Someone already opened a bug for libkf5akonadise
My current list of unupgradable packages on amd64 is:
gir1.2-gstreamer-1.0/unstable 1.24.0-1 amd64 [upgradable from: 1.22.10-1]
libegl-mesa0/unstable 24.0.2-1 amd64 [upgradable from: 24.0.1-1]
libgbm1/unstable 24.0.2-1 amd64 [upgradable from: 24.0.1-1]
libgl1-mesa-dri/unstable 24.0.2-1 amd64 [upg
On Sun, Jan 10, 2016 at 10:56:21AM +0100, Eric Valette wrote:
Russ Allbery writes:
>For one specific example, it's become quite clear over the past year that
>systemd has achieved the same status as abortion debates in US politics.
>Not only is it clear that we will *never* stop
Russ Allbery writes:
For one specific example, it's become quite clear over the past year that
systemd has achieved the same status as abortion debates in US politics.
Not only is it clear that we will *never* stop arguing about systemd,
opposition to or support of systemd has turned into a trib
On 01/06/2016 10:40 AM, Simon McVittie wrote:
On 05/01/16 15:55, Ian Jackson wrote:
Abolishing the distinction between /usr and /
"Merged /usr" is not about removing the distinction between /usr and /,
it's about removing the distinction between subdirectories of /usr and
the corresponding sub
On 04/01/2016 20:43, Michael Biebl wrote:
an initramfs is not mandatory as long as you don't have /usr on a
separate partition.
No initramfs + split /usr is not supported and has been broken for a while.
Did you actually test it? It works for me TM on fairly simple setup...
-- eric
Remember that / and /usr don't have to reside on the same partition with
the usrmerge proposal: they only have to be both available
post-initramfs. The initramfs already takes care to mount /usr (for the
systemd case as initscripts needs updates for sysvinit as was said
elsewhere). So no reparti
Remember that / and /usr don't have to reside on the same partition with
the usrmerge proposal: they only have to be both available
post-initramfs. The initramfs already takes care to mount /usr (for the
systemd case as initscripts needs updates for sysvinit as was said
elsewhere
I'm confused why you think anything will break. There would obviously be
symlinks, so anything that's currently in /bin will continue to work if
invoked with an absolute /bin path.
I consider linking across file system a very bad practice because if
/usr gets errors all the symlinks may be bro
On 03/01/2016 22:10, Russ Allbery wrote:
Eric Valette writes:
The problem of getting /usr mounted before things start using it is mostly
separate from the question of whether we want to merge it with /bin and
/lib. This thread is more about the latter than the former. (Obviously,
mounting
Note that mounting /usr early, something we *already do*, is separate from
actually merging /usr with /bin and /lib. Once you mount /usr early, it's
rather less important whether you actually merge the file systems. While
it does let you do some interesting things, I see it as more of a cleanup.
>This is not true: you just need to use an initramfs.
Ok, so it should warn that this setup will soon require to use an initramfs.
It is the Debian default, there is no need to do this.
Being debian installer default does not mean any debian users
1) really has any benefit of using it a
The debian installer should first loudly warn that having a separated / and
/usr may break things in the future but not forbid it. With that in place,
This is not true: you just need to use an initramfs.
Ok, so it should warn that this setup will soon require to use an
initramfs. I just pointe
What is the "upgrade path" for an older system that has /usr split
off? Will it just stop being bootable after upgrading?
It just needs to use an initramfs.
A standalone /usr without an initramfs IS ALREADY NOT SUPPORTED by
systemd.
This is not relevant for merged /usr.
What is the "upgrade pa
On 11/21/2014 03:26 PM, Jonathan de Boyne Pollard wrote:
> Eric Valette:
>> There has been a good and valuable effort trying to split original
>> upstream packages provided init system scripts by debian developers
>> into /etc/default/X and /etc/init.d/X file and storing mos
> I did not know that. It is very interesting.
>
> But, is there a way to be notified at upgrade time that the
> system service file has been modified when there is local
> (partial or full) changes ?
> As a small workaround, I think I will put symlinks such as
> /lib/systemd/[perhaps sub-direc
> well, debconf seems like a win here.
> There's no reasonable default so it's desirable to make it easy for the
> admin to specify and so you'd probably want to use normal best practice
> for debconf updates.
I agree with this but unfortunately original minidlna package as no
debconf setup :-)
--
Parsing User=$TOTO as "the User is the value of the environment variable
TOTO as given by Environment or EnvironmentFile" might be a reasonable
feature request, but it is not currently an implemented feature.
I think anything that simplify transitioning from an init system to
another new one is
On 18/11/2014 19:47, Matthias Urlichs wrote:
ExecStart=sudo -u $USER_MINIDLNA -g GROUP_MINIDLNA /usr/sbin/minidlnad -S
is an adequate and perfectly serviceable answer to your question.
On the other hand, the documented way to do this in systemd man pages is
to use User and Group. If th
On 18/11/2014 18:36, Ansgar Burchardt wrote:
Hi,
On 11/18/2014 06:25 PM, Eric Valette wrote:
In the file they just need to set User and Group then?
With systemd you can ship a default configuration in
/lib/systemd/system and administrators can override specific options,
for example
On 18/11/2014 17:46, Ansgar Burchardt wrote:
Hi,
On 11/18/2014 05:39 PM, Matthias Urlichs wrote:
trying to convert minidlna sysv init file to systemd, managed to have
a working unit file but failed to split the configuration mimicing
the ../default/minidlna content with the habil
On 18/11/2014 17:39, Matthias Urlichs wrote:
Text emails, please.
I alway forget that in my company my mailer is configured for html as
outlook discussion cut is absurd...
You _can_ do
ExecStart=sudo -u $USER_MINIDLNA -g GROUP_MINIDLNA /usr/sbin/minidlnad -S
but that's not the o
Which bug report is that?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748651
I will try to add the requested debug log ASAP. Dunno where I got the
initial bogus trace command from. Probably not invented it.
--eric
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
w
On 01/07/2014 19:59, Matthias Klumpp wrote:
These are valid points, and thank you for reporting bugs! However, as
unstable user, some breakage can be expected, and the point for
transitioning early in unstable is to make the transition as smooth as
possible when someone uprades Debian stable, wh
I think that this would be an annoying waste of time for most users,
since only a few people care so much about not being tainted by systemd
I do not care being tainted by systemd when it works. Actually on two
very different machines it means no audio for me.
On a NAS it means no boot(probab
While working on debian one thing I have not managed to find is
documentation on what packages can and can't assume about the build
environment. Does such documentation exist and if not should it be
created.
Some specific cases i'm wondering about:
I just discovered that on my beagleboard XM (un
On 29/09/2012 12:32, Henrique de Moraes Holschuh wrote:
If you want to use non-modular, built-in microcode, the documentation of
iucode-tool does explain how to trigger the microcode reload after boot. You
will have to add it to your system yourself.
Fair enough. Already done. However, during
Unless under very specific circumstances, the use of a modular
kernel brings one the ability to replace the particular hardware
the system runs on at will.
If I do taylor my kernel for my machine, I do not care at all
Say, it's possible to replace a just burn
On 29/09/2012 03:46, Henrique de Moraes Holschuh wrote:
1. No html, please.
non-initrd is supported. Read the package documentation for the details.
I did. I do not want to compile microcode tool as a module because
module loading juts slows down the boot process and contrarilly to many
o
Reading the thread about microcode, I wonder why
there is no more any /etc/init.d/microcode.ctl equivalent for
people like building their own kernel without initrd.
-- eric
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with
Unless I missed someting, the binary contained in
digikam_2.9.0-2_amd64.deb is still linked with the libmarblewidget12
library, the control file is still wrong, and I think the conflick
with phonon-backend-vlc is unnecessary.
I edited the control file using dpkg-d
> And how do you expect non-experts be able to solve problems when they
> pop up. Buying consultant services from the experts?
Non-experts are not able to solve any problem, so this is not an issue.
You are even unable to understand how brilliant I am you poo
On 18/03/2012 02:24, Christoph Anton Mitterer wrote:
Which distro provides Blu-Ray playback?
Even though there is libaacs and friends now... the MKBs are only
publicly known till version ... what? ... 10?
As long as it remains free of charge and available, you can package
makemkv in non-f
Actually official debian does not offers this and is furthermore
criticizing good willing people that try to make Debian useable in a
multimedia/HTPC system.
official Debian is not criticising anyone here. This is just debian-
devel@l.d.o: some people ranting, some discussing and some totally of
When exactly was vlc not up-to-date on Debian?
As long as it is unable to play dvd or various codec that are non
supported given the option for compiling libav for example
-- eric
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Co
When the totem law of Kbanga declares that displaying any words with two
consonant clusters is illegal on Fridays, the rest of the world doesn't
suffer. Being able to pop in a DVD and play it is something an average
person takes for granted. If oppressive laws in a single country stop a
good par
> take a look at yavdr, openelec, geexbox, ubuntu studio and the
> packages they provide
>
>
Readhttp://thelinuxcauldron.wordpress.com/2009/04/14/the-list-the-top-5-media-center-programs-for-linux/
> and see the one you have.
Ahh, so your definition of "serious multimedia" is "media centers"
On 10/03/2012 12:40, Philip Hands wrote:
Really?
Again, vlc or mplayer do not make a multi-media capable distribution.
take a look at yavdr, openelec, geexbox, ubuntu studio and the packages
they provide
Read
http://thelinuxcauldron.wordpress.com/2009/04/14/the-list-the-top-5-media-center
Yes acknowledged that vlc and mplayer are now up-to-date.
Libav vs ffmpeg could be per se part of the debate. We could also speak
about compilation options and induced feature/codec support
what about xbmc, mythv, tvheadend, avidemux?
-- eric
--
To UNSUBSCRIBE, email to debian-devel-requ..
On 10/03/2012 12:03, Eric Valette wrote:
On 10/03/2012 11:44, Eric Valette wrote:
I know the version already yes. And yes debian is completely outdated.
To be fair, but catching up at least for vlc, mplayer...
Still no xbmc, handbrake, libdvbcsa tough and quite old ffmpeg
mythtv
On 10/03/2012 11:44, Eric Valette wrote:
I know the version already yes. And yes debian is completely outdated.
To be fair, but catching up at least for vlc, mplayer...
Still no xbmc, handbrake, libdvbcsa tough and quite old ffmpeg
-- eric
--
To UNSUBSCRIBE, email to debian-devel-requ
On 10/03/2012 11:14, Thomas Goirand wrote:
In where? Stable? SID? Backports? FYI, you can check all
of this easily by yourself using packages.debian.org. Or
are you trying to make the point that Debian has outdated
packages?
I ask you a question: what are the version of the packeges in debian
While debian-multimedia.org has gained a reputation of providing
packages, which were desperately lacking in Debian,
IMO this repository has turned into a major source of trouble and
pissed users provoking flamewars in the recent past. There is still a
number of remaining multimedia-related packag
48 matches
Mail list logo
