Hello Paul, thank you for the notice. Hello, non-free managers! I read the page https://www.debian.org/doc/manuals/developers-reference/pkgs.html#marking-non-free-packages-as-auto-buildable and found that I missed one step in the process in order to make ooohg auto-buildable.
I forgot to describe why ooohg was in non-free section. Its license is CC-BY-NC, which prohibits its commercial use, but does not prohibit building the package and redistributing it. I upload release 09.2013-6 shortly. Thank for your future help if I forgot someting else. Best regards, Georges. Paul Gevers a écrit : > Source: ooohg > Version: 09.2013-4 > Severity: serious > Control: close -1 09.2013-5 > Tags: sid forky > User: [email protected] > Usertags: out-of-sync > > [Manual note to template: this package is a non-free package that hasn't > properly opted in to autobuilding. Please follow the required steps or > upload the binaries manually: > https://www.debian.org/doc/manuals/developers-reference/pkgs.html#marking-non-free-packages-as-auto-buildable > .] > > Dear maintainer(s), > > The Release Team considers packages that are out-of-sync between testing and > unstable for more than 30 days as having a Release Critical bug in testing > [1]. Your package src:ooohg has been trying to migrate for 31 days [2], > hence this bug report. The current output of the migration software for this > package is copied to the bottom of this report and should list the reason > why the package is blocked. Regularly, reporting issues against reverse > (build/test/regular) dependencies is what needs to happen. If this has > already been done, than this bug is just for tracking purposes. > > If a package is out of sync between unstable and testing for a longer > period, this usually means that bugs in the package in testing cannot be > fixed via unstable. Blocked packages can have impact on other packages, > which makes preparing for the release more difficult. The situation that > caused this bug report might even be the result of such an issue. We expect > maintainers to fix issues that hamper the migration of their package in a > timely manner. If your package in this situation due to another package, > consider helping out. > > This bug will trigger auto-removal when appropriate. As with all new bugs, > there will be at least 30 days before the package is auto-removed. > > This bug submission immediately closes the bug with the version in unstable, > so if that version or a later version migrates, this bug will no longer > affect testing. This bug is also tagged to only affect sid and forky, so it > doesn't affect (old-)stable. > > If you believe your package is unable to migrate to testing due to issues > beyond your control, don't hesitate to contact the Release Team. > > This bug report has been automatically generated. If you have any comments > with regards to the content or the process, please reach out to me. > > Paul > > [1] https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html > [2] https://qa.debian.org/excuses.php?package=ooohg > > Current text from [2]: > Migration status for ooohg (09.2013-4 to 09.2013-5): BLOCKED: Maybe > temporary, maybe blocked but Britney is missing information (check below) > Issues preventing migration: > ∙ ∙ Missing build on all > ∙ ∙ Autopkgtest deferred: missing builds > ∙ ∙ Lintian check deferred: missing builds > Additional info (not blocking): > ∙ ∙ Piuparts can't test ooohg (not a blocker) - (no link yet) > ∙ ∙ 31 days old (needed 5 days)
signature.asc
Description: PGP signature
