Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Current Corresponding Ubuntu Version
0 views
Skip to first unread message
Joshua Blagden
Apr 20, 2021, 12:40:03 AM4/20/21
to
Hi,
I'm trying to install Handbrake from the official Handbrake repository
so I can get a newer version than the one in the Debian Testing
repository. I would just use the one from the Debian Testing repository,
but it has a terrible memory leak problem, to the point where if you
have it render enough previews, it'll exhaust your system's memory and
quit. I think I just need to choose the right branch of the Handbrake
repository. Unfortunately, it's geared toward Ubuntu, so you have to
choose the Ubuntu codename which corresponds to the version of Debian
that you're running. I'm running Debian Testing* and I usually update
every couple days to keep everything running smoothly. Which version of
Ubuntu does Debian Testing currently correspond to?
*Partially because I built my current system back in November and Debian
Stable didn't have a new enough kernel and GPU drivers for my system -
MSI B550 Gaming Plus, AMD Ryzen 5600X, Sapphire RX 5600 XT.
Thanks,
Josh Blagden
I'm trying to install Handbrake from the official Handbrake repository
so I can get a newer version than the one in the Debian Testing
repository. I would just use the one from the Debian Testing repository,
but it has a terrible memory leak problem, to the point where if you
have it render enough previews, it'll exhaust your system's memory and
quit. I think I just need to choose the right branch of the Handbrake
repository. Unfortunately, it's geared toward Ubuntu, so you have to
choose the Ubuntu codename which corresponds to the version of Debian
that you're running. I'm running Debian Testing* and I usually update
every couple days to keep everything running smoothly. Which version of
Ubuntu does Debian Testing currently correspond to?
*Partially because I built my current system back in November and Debian
Stable didn't have a new enough kernel and GPU drivers for my system -
MSI B550 Gaming Plus, AMD Ryzen 5600X, Sapphire RX 5600 XT.
Thanks,
Josh Blagden
Dan Ritter
Apr 20, 2021, 2:40:03 PM4/20/21
to
Joshua Blagden wrote:
> Hi,
>
> I'm trying to install Handbrake from the official Handbrake repository so I
> can get a newer version than the one in the Debian Testing repository. I
> would just use the one from the Debian Testing repository, but it has a
> terrible memory leak problem, to the point where if you have it render
> enough previews, it'll exhaust your system's memory and quit. I think I just
> need to choose the right branch of the Handbrake repository. Unfortunately,
> it's geared toward Ubuntu, so you have to choose the Ubuntu codename which
> corresponds to the version of Debian that you're running. I'm running Debian
> Testing* and I usually update every couple days to keep everything running
> smoothly. Which version of Ubuntu does Debian Testing currently correspond
> to?
It doesn't.
> Hi,
>
> I'm trying to install Handbrake from the official Handbrake repository so I
> can get a newer version than the one in the Debian Testing repository. I
> would just use the one from the Debian Testing repository, but it has a
> terrible memory leak problem, to the point where if you have it render
> enough previews, it'll exhaust your system's memory and quit. I think I just
> need to choose the right branch of the Handbrake repository. Unfortunately,
> it's geared toward Ubuntu, so you have to choose the Ubuntu codename which
> corresponds to the version of Debian that you're running. I'm running Debian
> Testing* and I usually update every couple days to keep everything running
> smoothly. Which version of Ubuntu does Debian Testing currently correspond
> to?
Ubuntu's schedule is (IIRC) to release twice a year, and every 2
years makes a .04 release into a long-term-support version.
Debian's schedule is to release stable (approximating what
Ubuntu thinks of as LTS, but Debian uses that term differently)
whenever stable is ready.
In addition to stable, there is backports, unstable and testing.
backports is available to add to each stable release, so for
example buster is stable right now, so buster-backports can be
added to it.
unstable and testing are complete distributions, but you are
advised not to use them if you don't know why you are using
them.
Packages in unstable are freshly compiled and have no security
support. You should expect them to change rapidly, have major
bugs, and not have those bugs fixed quickly.
After a package has been in unstable for 2-10 days (depending on the
urgency of the upload), and the package has been built for all the
architectures which the present version in testing was built for, and
Installing the package into testing will not make the distribution more
uninstallable, and the package is not known to introduce new release
critical bugs... it can go into testing.
Testing is cyclic: right now, it is relatively quiet (for a
sample desktop, 1-50 package updates a day) because it is
getting close to release time.
At release time, stable becomes oldstable, testing becomes
stable. The major version is incremented.
And soon after that release, testing will become a near-anarchy
for the next year or three.
Hope that helps.
Also, read
https://wiki.debian.org/DontBreakDebian#Don.27t_make_a_FrankenDebian
-dsr-
Celejar
Apr 20, 2021, 8:30:02 PM4/20/21
to
On Tue, 20 Apr 2021 14:13:19 -0400
Dan Ritter <d...@randomstring.org> wrote:
...
> Packages in unstable are freshly compiled and have no security
> support. You should expect them to change rapidly, have major
> bugs, and not have those bugs fixed quickly.
To clarify: while it is true that
"there are no security updates for unstable"
and that
"The fact is that some security issues might appear in unstable and not
in the stable distribution. This is due to new functionality constantly
being added to the applications provided there, as well as new
applications being included which might not yet have been thoroughly
tested."
it is also true that
"When a security fix is prepared, the Security Team backports the patch
to stable (since stable is usually some minor or major versions
behind). Package maintainers are responsible for preparing packages for
the unstable branch, usually based on a new upstream release. Sometimes
the changes happen at nearly the same time and sometimes one of the
releases gets the security fix before. Packages for the stable
distribution are more thoroughly tested than unstable, since the latter
will in most cases provide the latest upstream release (which might
include new, unknown bugs).
Security updates are available for the unstable branch usually when the
package maintainer makes a new package and for the stable branch when
the Security Team make a new upload and publish a DSA."
https://www.debian.org/doc/manuals/securing-debian-manual/ch10.en.html#id-1.11.2.5
So while it's true that unstable doesn't get dedicated security
support, it's an open question as to whether unstable or stable will
get any given security fix first.
Celejar
Dan Ritter <d...@randomstring.org> wrote:
...
> Packages in unstable are freshly compiled and have no security
> support. You should expect them to change rapidly, have major
> bugs, and not have those bugs fixed quickly.
"there are no security updates for unstable"
and that
"The fact is that some security issues might appear in unstable and not
in the stable distribution. This is due to new functionality constantly
being added to the applications provided there, as well as new
applications being included which might not yet have been thoroughly
tested."
it is also true that
"When a security fix is prepared, the Security Team backports the patch
to stable (since stable is usually some minor or major versions
behind). Package maintainers are responsible for preparing packages for
the unstable branch, usually based on a new upstream release. Sometimes
the changes happen at nearly the same time and sometimes one of the
releases gets the security fix before. Packages for the stable
distribution are more thoroughly tested than unstable, since the latter
will in most cases provide the latest upstream release (which might
include new, unknown bugs).
Security updates are available for the unstable branch usually when the
package maintainer makes a new package and for the stable branch when
the Security Team make a new upload and publish a DSA."
https://www.debian.org/doc/manuals/securing-debian-manual/ch10.en.html#id-1.11.2.5
So while it's true that unstable doesn't get dedicated security
support, it's an open question as to whether unstable or stable will
get any given security fix first.
Celejar
Andrew M.A. Cater
Apr 22, 2021, 9:40:02 AM4/22/21
to
It's probably a good idea to change anything that says "testing" to
something that says bullseye right now- that way, when Bullseye gets released
(possibly within the month) you won't end up with a huge churn as
Testing points to Bookworm and begins another two years of churn.
To clarify, what you probably need is somethin close to this
#
deb http://deb.debian.org/debian/ bullseye main non-free contrib
deb-src http://deb.debian.org/debian/ bullseye main non-free contrib
deb http://security.debian.org/debian-security bullseye/updates main contrib non-free
deb-src http://security.debian.org/debian-security bullseye/updates main contrib non-free
# bullseye-updates, previously known as 'volatile'
deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free
deb-src http://deb.debian.org/debian/ bullseye-updates main contrib non-free
# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.
Current Ubuntu - 21.04 - will probably have been based on a mixture of
Debian unstable/testing.
To be honest - always take Debian native packages if you can: you really
don't want to be mixing things and creating a FrankenDebian.
Hope this helps,
Andy C.
JAM8
Apr 22, 2021, 9:50:02 AM4/22/21
to
Pierre-Elliott Bécue
Apr 24, 2021, 9:10:06 AM4/24/21
to
Le jeudi 22 avril 2021 à 09:25:47-0400, JAM8 a écrit :
> unsubscribe
Have a look at https://www.debian.org/MailingLists/unsubscribe
--
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2
It's far easier to fight for principles than to live up to them.
> unsubscribe
Have a look at https://www.debian.org/MailingLists/unsubscribe
--
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2
It's far easier to fight for principles than to live up to them.
0 new messages