Re: docker-compose removed from Trixie

Niels Thykier <[email protected]> Tue, 17 Dec 2024 20:18:39 +0100
Newsgroups	gmane.linux.debian.user.testing
Message-ID	<[email protected]>
Rafał Lichwała:
> Hi,
> 

Hi :)

> docker-compose package has been removed from Trixie repo 10 days ago:
> 
> [...]
> 
> I'm a new user of Debian testing, so sorry if it's obvious, but I want 
> to ask two questions:
> 
> 1. I know that Debian testing is an ongoing process of updates and 
> testing before the next Debian major release, but is that normal to have 
> this package removed?

It is normal for packages removed from testing in general. They can also 
be removed from unstable (which you refer to later), though for this 
kind of situation usually with a considerable delay comparable to testing.

> Does is mean that someone works on that and if 
> solved this package will appear again in repo?
> 

No, In general, it is not possible to make a statement like that. It is 
a "maybe" 99% of the time.

Debian is build by volunteers. The only way for sure to know if 
"someone" works on it is by being that "someone". Maybe that is not for 
you. But if it is or you might think it is, you can try the patch at 
https://bugs.debian.org/1084703 and request a "Non-Maintainer Upload" 
for the package if the patch works. From what I can see that is all that 
is needed for `docker-compose` to be returned to testing.

If you are considering that, [email protected] can help 
you with problems and getting the upload sponsored (performed). And if 
not, that is fine too.

Otherwise, you are welcome to wait to see if someone else gets around to 
do it (the official maintainer or a drive-by volunteer).

> 2. I read somewhere that Debian unstable (sid) is more reliable for 
> daily usage then Debian testing (currently Trixie). Is that true?
> (BTW: I switched from bookworm to trixie due to availability of KDE 
> Plasma 6)
> 
> Thanks,
> Rafal
> 

I think that strongly depends on your definition of "reliable". You 
might have avoided this particular kind of problem. However, unstable is 
called unstable for a reason.

However, there are some for which unstable works well for them. They 
tend to have their own answers to how they handle the problems of 
unstable. Like backups, pulling from both testing and unstable with a 
preference for testing, active tracking Debian changes, etc. They all 
have different trade-offs on risks vs. benefits vs. cost (mental 
load/time spent) to you as the user/system admin.


If you are mostly happy with testing and only occasionally run into a 
package being temporarily from testing, then the "Testing-Unstable Mix" 
*may* work for you (per https://wiki.debian.org/DebianUnstable). It 
worked for some people I know as a "best of both worlds" most of time 
and then on occasion "worst of both worlds". Though, in the end, it is 
up to you to "pick your poison".

If you are looking for a support channel on either unstable or testing, 
then 
https://wiki.debian.org/DebianUnstable#Where_can_I_get_help_with_Sid.3F 
may work for you. I do not know if they cover this particular topic, but 
it is the only unstable/testing support channel I know of.

Best regards,
Niels
OpenPGP_signature.asc (application/pgp-signature, 488 B)