Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Audacity and Scribus Missing in Debian Testing repo
Audacity and Scribus Missing in Debian Testing repo
I've been using Debian Testing (Bookworm). It's been working great except that I can't find Audacity and Scribus in the repo. Highly appreciate if someone informs me when these two applications are supposed to enter Testing repo.
- canci
- Global Moderator
- Posts: 2502
- Joined: 2006-09-24 11:28
- Has thanked: 136 times
- Been thanked: 136 times
Re: Audacity and Scribus Missing in Debian Testing repo
If you use a development branch like testing, then you should be able to just google why the packages were removed.
Stable / Asus VivoBook X421DA / AMD Ryzen 7 3700U / Radeon Vega Mobile Gfx (Picasso) / 8 GB RAM / 512GB NVMe
READ THIS:
* How to Post a Thread Here
* Other Tips and Great Resources
READ THIS:
* How to Post a Thread Here
* Other Tips and Great Resources
- cds60601
- df -h | participant
- Posts: 719
- Joined: 2017-11-25 05:58
- Location: Florida
- Has thanked: 133 times
- Been thanked: 63 times
Re: Audacity and Scribus Missing in Debian Testing repo
https://tracker.debian.org/pkg/audacity
In short...
testing migrations
excuses:
Migration status for audacity (- to 2.4.2~dfsg0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
Issues preventing migration:
∙ ∙ Updating audacity would introduce bugs in testing: #1004598
∙ ∙ Impossible Depends: audacity -> libavcodec-extra58/7:4.4.2-1+b3/mipsel
∙ ∙ Impossible Depends: audacity -> libavformat-extra58/7:4.4.2-1+b3/mipsel
∙ ∙ Impossible Depends: audacity -> libavutil56/7:4.4.2-1+b3/mipsel
Additional info:
∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/a/audacity.html
∙ ∙ 488 days old (needed 5 days)
Not considered
And for Scribus:
testing migrations
This package will soon be part of the auto-icu transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.
excuses:
Migration status: Blocked. Can't migrate due to a non-migratable dependency. Check status below.
Blocked by: openscenegraph
Migration status for scribus (- to 1.5.8+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
Issues preventing migration:
∙ ∙ Build-Depends(-Arch): scribus openscenegraph (not considered)
∙ ∙ Depends: scribus openscenegraph (not considered)
∙ ∙ Invalidated by build-dependency
∙ ∙ Invalidated by dependency
Additional info:
∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scribus.html
∙ ∙ 101 days old (needed 5 days)
Not considered
In short...
testing migrations
excuses:
Migration status for audacity (- to 2.4.2~dfsg0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
Issues preventing migration:
∙ ∙ Updating audacity would introduce bugs in testing: #1004598
∙ ∙ Impossible Depends: audacity -> libavcodec-extra58/7:4.4.2-1+b3/mipsel
∙ ∙ Impossible Depends: audacity -> libavformat-extra58/7:4.4.2-1+b3/mipsel
∙ ∙ Impossible Depends: audacity -> libavutil56/7:4.4.2-1+b3/mipsel
Additional info:
∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/a/audacity.html
∙ ∙ 488 days old (needed 5 days)
Not considered
And for Scribus:
testing migrations
This package will soon be part of the auto-icu transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.
excuses:
Migration status: Blocked. Can't migrate due to a non-migratable dependency. Check status below.
Blocked by: openscenegraph
Migration status for scribus (- to 1.5.8+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
Issues preventing migration:
∙ ∙ Build-Depends(-Arch): scribus openscenegraph (not considered)
∙ ∙ Depends: scribus openscenegraph (not considered)
∙ ∙ Invalidated by build-dependency
∙ ∙ Invalidated by dependency
Additional info:
∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scribus.html
∙ ∙ 101 days old (needed 5 days)
Not considered
Last edited by cds60601 on 2022-09-28 17:01, edited 1 time in total.
Supercalifragilisticexpialidocious
Re: Audacity and Scribus Missing in Debian Testing repo
See Developer Information after a search at https://www.debian.org/distrib/packages for the two packages.
--
Brian.
Brian.
Re: Audacity and Scribus Missing in Debian Testing repo
Our experience is, don't use Testing except a couple of months before a new Debian release (in this cast, it will be Bookworm).
Use Sid/"Unstable" instead.
Both audacity and scribus are in Sid repo.
Re: Audacity and Scribus Missing in Debian Testing repo
Both Testing and Unstable are development releases. Those who use them should be prepared for problems, know how to troubleshoot them and file bug reports. That's how Debian creates a Stable release. To put it bluntly, if you have to ask, use Stable.
Re: Audacity and Scribus Missing in Debian Testing repo
OK. I pulled in both the applications from Unstable. They both work as expected, thanks.
- cds60601
- df -h | participant
- Posts: 719
- Joined: 2017-11-25 05:58
- Location: Florida
- Has thanked: 133 times
- Been thanked: 63 times
Re: Audacity and Scribus Missing in Debian Testing repo
The use of Stable is always suggested. Using Testing affords you at least security updates to a point. Telling users not to use Testing only at a certain point is not only foolish, but not advised. Telling a user to use Sid (Unstable) is just plain incorrect. Especially if a user does not know how to handle that branch.
Do not advise users to use Unstable just because an application is not in the repo at the time. If you opt to continue to tell users to use a release such as Unstable, at least post the proper links so that a user can make an educated decision as to why they might or might not use a certain branch.
As a reminder... https://www.debian.org/releases/
Do not advise users to use Unstable just because an application is not in the repo at the time. If you opt to continue to tell users to use a release such as Unstable, at least post the proper links so that a user can make an educated decision as to why they might or might not use a certain branch.
As a reminder... https://www.debian.org/releases/
Supercalifragilisticexpialidocious