Your message dated Sat, 30 Aug 2025 22:52:34 +0000
with message-id <[email protected]>
and subject line Bug#1065733: fixed in ratt 0.0~git20250829.39528ce-1
has caused the Debian Bug report #1065733,
regarding ratt: Unable to run ratt for packages targetting experimental.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1065733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065733
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ratt
Version: 0.0~git20190123.9e77a6d-1+b9
Severity: normal
Dear Maintainer,
I tried many things to make ratt work against experimental (see the
following examples) but I didn't succeed. It would be great to be able
to run rutt with experimental packages to see whether they're good to be
uploaded to unstable.
```
SBUILD_CONFIG=~/.sbuildrc.experimental ratt
../golang-github-protonmail-go-crypto_1.0.0-1_amd64.changes
2024/03/09 14:53:14 Loading changes file
"../golang-github-protonmail-go-crypto_1.0.0-1_amd64.changes"
2024/03/09 14:53:14 - 1 binary packages: golang-github-protonmail-go-crypto-dev
2024/03/09 14:53:14 Corresponding .debs (will be injected when building):
2024/03/09 14:53:14
../golang-github-protonmail-go-crypto-dev_1.0.0-1_all.deb
2024/03/09 14:53:14 Setting -dist=experimental (from .changes file)
2024/03/09 14:53:14 Could not find InRelease file for experimental . Are you
missing experimental in your /etc/apt/sources.list?
```
```
APT_CONFIG=~/.chdist/experimental/etc/apt/apt.conf ratt -sbui
ld_dist=experimental-amd64-sbuild
../golang-github-protonmail-go-crypto_1.0.0-1_amd64.changes
2024/03/09 14:57:52 Loading changes file
"../golang-github-protonmail-go-crypto_1.0.0-1_amd64.changes"
2024/03/09 14:57:52 - 1 binary packages: golang-github-protonmail-go-crypto-dev
2024/03/09 14:57:52 Corresponding .debs (will be injected when building):
2024/03/09 14:57:52
../golang-github-protonmail-go-crypto-dev_1.0.0-1_all.deb
2024/03/09 14:57:52 Setting -dist=experimental (from .changes file)
2024/03/09 14:57:53 Could not find InRelease file for experimental . Are you
missing experimental in your /etc/apt/sources.list?
```
It seems ratt just refuses to use anything targetting at experimental.
Best regards,
Martin
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (900, 'testing'), (600, 'unstable'), (500, 'unstable-debug'),
(500, 'testing-debug'), (500, 'experimental'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.7.7-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages ratt depends on:
ii libc6 2.37-15.1
ii sbuild 0.85.6
Versions of packages ratt recommends:
ii dose-extra 7.0.0-4+b1
ratt suggests no packages.
-- no debconf information
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hi Martin,
Thanks for the report.
ratt now handles the experimental release correctly. I added support for
this case, and it is included in the current archive version
0.0~git20250829.39528ce-1.
Best regards,
Aquila
--- End Message ---
