Hi again,
Am Tue, May 16, 2023 at 07:49:55PM +0530 schrieb Nilesh Patra:
> On Tue, May 16, 2023 at 07:25:15PM +0530, Nilesh Patra wrote:
> > I personally prefer "1" over 2 as it is less noise (and effort).
>
> On second thoughts, I think sending it via testing-proposed-updates
> would be a better thing to do, as this case perfectly fits the problem.
I hope I was following developers reference about t-p-u[6] correctly
and pushed
$ git diff HEAD^
diff --git a/debian/changelog b/debian/changelog
index 21d12c3..a2b6c26 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+r-cran-shiny (1.7.4+dfsg-3~deb12u1) bookworm; urgency=medium
+
+ * Upload to testing-proposed-updates "bookworm" due to the fact that
+ there was an accidental upload of a new version of r-base to unstable
+
+ -- Andreas Tille <ti...@debian.org> Wed, 17 May 2023 07:56:25 +0200
+
r-cran-shiny (1.7.4+dfsg-3) unstable; urgency=medium
* Fix link for normalize.css
to git. I've choosen the version 1.7.4+dfsg-3~deb12u1 to match
the requirement that the version is lower than in unstable
$ if dpkg --compare-versions 1.7.4+dfsg-3 gt 1.7.4+dfsg-3~deb12u1 ; then echo
"OK" ; else echo "hmmm" ; fi
OK
I wonder whether dput is working with target distribution bookworm since
lintian throws an error. Release team is in CC - do you think I should
file a bug right now or just after an upload?
Kind regards
Andreas.
> > > [1]
> > > https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-thematic/33619891/log.gz
> > > [2]
> > > https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-treescape/33619892/log.gz
> > > [3]
> > > https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-treespace/33619893/log.gz
> > > [4]
> > > https://tracker.debian.org/news/1429562/accepted-r-base-430-1-source-into-unstable/
> > [5] https://wiki.debian.org/TestingProposedUpdates
[6] https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#t-p-u
--
http://fam-tille.de
