NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: shim-signed_1.39~1+deb11u1_all-buildd.changes
  ACCEPT
Processing changes file: shim-signed_1.39~1+deb11u1_amd64-buildd.changes
  ACCEPT
Processing changes file: shim-signed_1.39~1+deb11u1_arm64-buildd.changes
  ACCEPT
Processing changes file: shim-signed_1.39~1+deb11u1_i386-buildd.changes
  ACCEPT

Re: bookworm release date?

[James Addison]

Hi Adam,

On Thu, 09 Mar 2023 17:05:28 +, Adam wrote:
> ftp-master have now published their bookworm keys, so we can get those
> incorporated. For the SRM side, you probably saw that we've been
> considering moving to an EC key. From the very limited responses to the
> discussion I started on debian-release, I'm still not entirely sure if
> that's feasible / a good idea.

Does the signing method update have to be one-method-for-another, or
is there is a way to phase-in a new method before phasing-out the old?

(my question is inspired by a recent talk by djb and Tanje Lange that
discusses[1] an encryption migration at Google that involved use of
two algorithms in parallel.  I realize that we're talking about
integrity signing rather than confidentiality, and it's also possible
that I'm creating a time-wasting distraction here, so.. take with a
grain of salt)

Thanks,
James

[1] - 
https://media.ccc.de/v/fire-shonks-2022-49246-post-quantum-cryptography-detours-delays-and-disasters#t=500

Re: Bug#1032545: r-cran-qpdf: FTBFS in testing: QPDF.hh:1569:36: error: ‘std::string_view’ has not been declared

[Andreas Tille]

Am Thu, Mar 09, 2023 at 10:08:02PM +0100 schrieb Sebastian Ramacher:
> > What do you think?
> 
> std::string_view was introduced in C++17, but r-cran-qpdf is building
> with C++11. Have you tried bumping the C++ version?

Ahhh, right.  Thanks a lot for the hint.  Just uploaded a fix.

I guess I need to file an unblock request for the just uploaded
r-cran-qpdf 1.3.0+dfsg-2?

Kind regards
   Andreas.

-- 
http://fam-tille.de

Re: Bug#1032545: r-cran-qpdf: FTBFS in testing: QPDF.hh:1569:36: error: ‘std::string_view’ has not been declared

[Sebastian Ramacher]

On 2023-03-09 21:13:02 +0100, Andreas Tille wrote:
> Hi,
> 
> Am Wed, Mar 08, 2023 at 09:30:38PM +0100 schrieb Lucas Nussbaum:
> > > /usr/include/qpdf/QPDF.hh:1569:36: error: ‘std::string_view’ has not been 
> > > declared
> > >  1569 | void linearizationWarning(std::string_view);
> > >   |^~~
> > > In file included from bindings.cpp:3:
> > > /usr/include/qpdf/QPDFWriter.hh:557:27: error: ‘std::string_view’ has not 
> > > been declared
> > >   557 | void writeString(std::string_view str);
> > >   |   ^~~
> > > /usr/include/qpdf/QPDFWriter.hh:559:30: error: ‘std::string_view’ has not 
> > > been declared
> > >   559 | void writeStringQDF(std::string_view str);
> > >   |  ^~~
> > > /usr/include/qpdf/QPDFWriter.hh:560:32: error: ‘std::string_view’ has not 
> > > been declared
> > >   560 | void writeStringNoQDF(std::string_view str);
> > >   |^~~
> > > make[1]: *** [/usr/lib/R/etc/Makeconf:178: bindings.o] Error 1
> 
> This error occures due to the upgrade of qpdf from 11.2.0 to 11.3.0.
> r-cran-qpdf ships with a code copy of 11.2.0 which was removed in favour
> of dynamic linking.  The only way I see to fix this bug while keeping
> the same r-cran-qpdf version is to keep the original upstream tarball
> and link against the code copy.
> 
> What do you think?

std::string_view was introduced in C++17, but r-cran-qpdf is building
with C++11. Have you tried bumping the C++ version?

Cheers
-- 
Sebastian Ramacher

Bug#1032580: marked as done (unblock: gnome-initial-setup/43.2-4)

[Debian Bug Tracking System]

Your message dated Thu, 09 Mar 2023 20:57:11 +
with message-id 
and subject line unblock gnome-initial-setup
has caused the Debian Bug report #1032580,
regarding unblock: gnome-initial-setup/43.2-4
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 ow...@bugs.debian.org
immediately.)


-- 
1032580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032580
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: gnome-initial-se...@packages.debian.org
Control: affects -1 + src:gnome-initial-setup

Please unblock package gnome-initial-setup

[ Reason ]
Fix UI glitches observed while testing fixes for #1029821

[ Impact ]
If not fixed, the full-screen "out of box experience" app shown on the
first login to GNOME, after initial installation or creating a new user,
is less polished than it should be.

The main fix since bookworm is that for users in locales that use a
non-trivial IBus input method rather than a simple Xkb keyboard layout
(Chinese, Japanese, Hindi, etc.), the default input method was mislabelled
and did not always appear. (#1032382)

This version also has an upstream change backported from upstream version
44.rc, fixing a regression that caused the shortlist of plausible
non-default keyboard layouts and input methods to be empty. There is
still a known bug that the shortlist is not very *useful* (it does not
have enough information to be weighted towards commonly-used keyboard
layouts and input methods for the relevant country, and away from
rare/specialized layouts like Dvorak), but that's not a regression and
it's better than nothing.

It also includes smaller tweaks to ensure the gnome-initial-setup window
is appropriately labelled in Alt+Tab and the Overview.

[ Tests ]
Manually tested via the steps in debian/README.source of unstable's
gnome-initial-setup, using English and Japanese locales.

Also carried out an installation of bookworm in Japanese (using a
parallel installation in English as a reference for which button does
what) and before logging in to GNOME for the first time, logged in via
tty to upgrade gnome-initial-setup and all packages from src:gnome-desktop
to their unstable versions.

[ Risks ]
This is a highly visible package with code that is surprisingly
fragile internally, and my initial attempt at this patchset caused it
to crash; but I expect that a lot of people will be testing new GNOME
installs between now and release day, so we'll get regression reports
if appropriate.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

unblock gnome-initial-setup/43.2-4
diffstat for gnome-initial-setup-43.2 gnome-initial-setup-43.2

 data/gnome-initial-setup.desktop.in.in |1 
 debian/README.source   |   19 +
 debian/changelog   |   52 ++
 debian/control |2 
 debian/patches/Add-StartupWMClass-to-.desktop-file.patch   |   29 +
 debian/patches/driver-Set-a-non-trivial-window-title.patch |   28 +
 debian/patches/keyboard-Correctly-update-labels-for-IBus-engines.patch |  189 ++
 debian/patches/keyboard-Resort-refilter-list-when-picking-shortlist.patch  |   96 +
 debian/patches/keyboard-Update-filter-and-sort-when-the-display-name-cha.patch |   46 ++
 debian/patches/reenable-existing-user-mode.patch   |6 
 debian/patches/series  |5 
 gnome-initial-setup/gis-driver.c   |1 
 gnome-initial-setup/pages/keyboard/cc-input-chooser.c  |   86 +++-
 13 files changed, 529 insertions(+), 31 deletions(-)

diff -Nru gnome-initial-setup-43.2/data/gnome-initial-setup.desktop.in.in gnome-initial-setup-43.2/data/gnome-initial-setup.desktop.in.in
--- gnome-initial-setup-43.2/data/gnome-initial-setup.desktop.in.in	2022-12-02 15:11:34.0 +
+++ gnome-initial-setup-43.2/data/gnome-initial-setup.desktop.in.in	2023-03-09 12:51:50.0 +
@@ -10,3 +10,4 @@
 OnlyShowIn=GNOME;
 NoDisplay=true
 X-GNOME-HiddenUnderSystemd=@systemd_hidden@
+StartupWMClass=org.gnome.InitialSetup
diff -Nru gnome-initial-setup-43.2/debian/changelog gnome-initial-setup-

Bug#1032579: marked as done (unblock: gnome-desktop/43.2-2)

[Debian Bug Tracking System]

Your message dated Thu, 09 Mar 2023 20:56:24 +
with message-id 
and subject line unblock gnome-desktop
has caused the Debian Bug report #1032579,
regarding unblock: gnome-desktop/43.2-2
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 ow...@bugs.debian.org
immediately.)


-- 
1032579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: gnome-desk...@packages.debian.org, 
debian-japan...@lists.debian.org
Control: affects -1 + src:gnome-desktop

Please unblock package gnome-desktop

[ Reason ]
Make default input method for ja_JP match what tasksel installs
(#1029821, grave)

[ Impact ]
If not accepted, Japanese-speaking users will find that gnome-initial-setup
leaves them without a working input method, unless they happen to have
installed ibus-anthy separately. This is because GNOME upstream prefers
to default to ibus-anthy, but Japanese-speaking Debian/Ubuntu users say
that ibus-mozc is a higher-quality default on architectures where it
is built, and therefore that's what task-japanese-gnome-desktop pulls in.

If this change is not accepted, then we should change tasksel to make
task-japanese-gnome-desktop pull in ibus-anthy instead of ibus-mozc
();
but Japanese-speaking users have told us that defaulting to ibus-anthy
would be unacceptable, so we have not gone that route.

[ Tests ]
Manually tested via the steps in debian/README.source of unstable's
gnome-initial-setup, both with ibus-mozc installed (reflecting what will
happen on x86 and ARM) and with only ibus-anthy installed (reflecting
what will happen on ppc64el and s390x, where ibus-mozc is unavailable
and ibus-anthy is the best thing available for Japanese users).

Also carried out an installation of bookworm in Japanese (using a
parallel installation in English as a reference for which button does
what) and before logging in to GNOME for the first time, logged in via
tty to upgrade gnome-initial-setup and all packages from src:gnome-desktop
to their unstable versions.

I can't read or write Japanese, so I can't tell the difference between
anthy and mozc; but in the Japanese installation,
`gsettings list-recursively` contained

org.gnome.desktop.input-sources sources [('xkb', 'jp'), ('ibus', 'mozc-jp')]

which seems like it's probably the desired result. Also, the option
selected in GNOME's menu of input methods by default is
"日本語 (Mozc)" which again seems plausibly correct.

[ Risks ]
The core change here is trivial: it's just replacing the name of one
IBus input method with another.

The hack to fall back to ibus-anthy if ibus-mozc isn't installed is
less trivial, but still straightforward. I wish we didn't have to do this,
but from what I understand of the problem, we need this for unconventional
CPU architectures.

If the accompanying gnome-initial-setup change (see separate unblock
request) is not accepted, then the UI will be sub-optimal (the ibus-mozc
option will appear as "mozc-jp" in the UI instead of the intended
"Japanese (Mozc)"), but that's not actually a regression: the same thing
happens today for ibus-anthy.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

unblock gnome-desktop/43.2-2
diffstat for gnome-desktop-43.2 gnome-desktop-43.2

 debian/changelog   |   25 ++
 debian/control |6 -
 debian/control.in  |4 -
 debian/libgnome-desktop-doc.lintian-overrides  |2 
 debian/patches/Fall-back-to-ibus-anthy-if-ibus-mozc-jp-is-unavailable.patch|   39 ++
 debian/patches/Use-mozc-as-the-default-input-source-for-Japanese.patch |   34 
 debian/patches/languages-Look-at-LOCPATH-before-compile-time-LIBLOCALEDI.patch |8 +-
 debian/patches/series  |2 
 libgnome-desktop/default-input-sources.h   |2 
 libgnome-desktop/gnome-languages.c |9 ++
 10 files changed, 119 insertions(+), 12 deletions(-)

diff -Nru gnome-desktop-43.2/debian/changelog gnome-desktop-43.2/debian/changelog
--- gnome-desktop-43.2/debi

Re: Bug#1032545: r-cran-qpdf: FTBFS in testing: QPDF.hh:1569:36: error: ‘std::string_view’ has not been declared

[Andreas Tille]

Hi,

Am Wed, Mar 08, 2023 at 09:30:38PM +0100 schrieb Lucas Nussbaum:
> > /usr/include/qpdf/QPDF.hh:1569:36: error: ‘std::string_view’ has not been 
> > declared
> >  1569 | void linearizationWarning(std::string_view);
> >   |^~~
> > In file included from bindings.cpp:3:
> > /usr/include/qpdf/QPDFWriter.hh:557:27: error: ‘std::string_view’ has not 
> > been declared
> >   557 | void writeString(std::string_view str);
> >   |   ^~~
> > /usr/include/qpdf/QPDFWriter.hh:559:30: error: ‘std::string_view’ has not 
> > been declared
> >   559 | void writeStringQDF(std::string_view str);
> >   |  ^~~
> > /usr/include/qpdf/QPDFWriter.hh:560:32: error: ‘std::string_view’ has not 
> > been declared
> >   560 | void writeStringNoQDF(std::string_view str);
> >   |^~~
> > make[1]: *** [/usr/lib/R/etc/Makeconf:178: bindings.o] Error 1

This error occures due to the upgrade of qpdf from 11.2.0 to 11.3.0.
r-cran-qpdf ships with a code copy of 11.2.0 which was removed in favour
of dynamic linking.  The only way I see to fix this bug while keeping
the same r-cran-qpdf version is to keep the original upstream tarball
and link against the code copy.

What do you think?

Kind regards
Andreas.

-- 
http://fam-tille.de

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: shim-signed_1.39~1+deb11u1_source.changes
  ACCEPT

Re: bookworm release date?

[Steve McIntyre]

On Thu, Mar 09, 2023 at 05:05:28PM +, Adam Barratt wrote:
>
>Sorry for the delayed reply, apparently I'm further behind than I
>realised. :-(

:-/ *hugs*

>On Fri, 2023-02-17 at 21:56 +0100, Paul Gevers wrote:
>[...]
>> What do people think of the idea
>> to start picking a release date already?
>> 
>[...]
>> Adam, I think we'd also want to do a point release before that time, 
>> e.g. to include a fix for bug #1029803. What do you think about it?
>> 
>
>Yes. We also really want to get a debian-archive-keyring update into
>bullseye before the release, or we can't use the new keys to sign the
>bookworm release files. But first we need to get it into unstable. I'm
>aware that we're very late here, sorry. :-(
>
>ftp-master have now published their bookworm keys, so we can get those
>incorporated. For the SRM side, you probably saw that we've been
>considering moving to an EC key. From the very limited responses to the
>discussion I started on debian-release, I'm still not entirely sure if
>that's feasible / a good idea.
>
>It would also be good to finally get the shim updates into bullseye at
>the same time, unless Steve tells me that's a bad plan. :-)

:-) I uploaded the latest signed shim last night expressly to have it
in the next bullseye point release. Do you want an unblock for that?

I'm also looking at some (small!) updates for grub too.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
“Why do people find DNS so difficult? It’s just cache invalidation and
 naming things.”
   -– Jeff Waugh (https://twitter.com/jdub)

Re: bookworm release date?

[Adam D. Barratt]

Hi,

Sorry for the delayed reply, apparently I'm further behind than I
realised. :-(

On Fri, 2023-02-17 at 21:56 +0100, Paul Gevers wrote:
[...]
> What do people think of the idea
> to start picking a release date already?
> 
[...]
> Adam, I think we'd also want to do a point release before that time, 
> e.g. to include a fix for bug #1029803. What do you think about it?
> 

Yes. We also really want to get a debian-archive-keyring update into
bullseye before the release, or we can't use the new keys to sign the
bookworm release files. But first we need to get it into unstable. I'm
aware that we're very late here, sorry. :-(

ftp-master have now published their bookworm keys, so we can get those
incorporated. For the SRM side, you probably saw that we've been
considering moving to an EC key. From the very limited responses to the
discussion I started on debian-release, I'm still not entirely sure if
that's feasible / a good idea.

It would also be good to finally get the shim updates into bullseye at
the same time, unless Steve tells me that's a bad plan. :-)

Regards,

Adam

Processed: reassign debci

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 970675 debci
Bug #970675 [release.debian.org] enable per-package timeout exceptions
Bug reassigned from package 'release.debian.org' to 'debci'.
Ignoring request to alter found versions of bug #970675 to the same values 
previously set
Ignoring request to alter fixed versions of bug #970675 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
970675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1021984: marked as done ((some kind of) transition: add python3.11 as a supported python3 version)

[Debian Bug Tracking System]

Your message dated Thu, 9 Mar 2023 16:24:55 +0100
with message-id <44cf98d9-a13a-06fd-ffc0-6c847a1bd...@debian.org>
and subject line Re: (some kind of) transition: add python3.11 as a supported 
python3 version
has caused the Debian Bug report #1021984,
regarding (some kind of) transition: add python3.11 as a supported python3 
version
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 ow...@bugs.debian.org
immediately.)


-- 
1021984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021984
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Please setup a tracker to add python3.11 as a supported python3 version. This is
non-blocking, as packages can migrate on their own once built. I'm not yet
starting this, just want to have an overview of affected packages.

Please re-use the final version of the python3.9 tracker (#996584).

The upstream release in on time again, so we should be prepared to start this 
addition after the upstream release end of October.
--- End Message ---
--- Begin Message ---

Hi,

On Tue, 18 Oct 2022 12:14:28 +0200 Matthias Klose  wrote:

Please setup a tracker to add python3.11 as a supported python3 version. This is
non-blocking, as packages can migrate on their own once built. I'm not yet
starting this, just want to have an overview of affected packages.

Please re-use the final version of the python3.9 tracker (#996584).

The upstream release in on time again, so we should be prepared to start this 
addition after the upstream release end of October.


python3.11 is the only Python in bookworm now.

Paul


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---

Bug#1032580: unblock: gnome-initial-setup/43.2-4

[Simon McVittie]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: gnome-initial-se...@packages.debian.org
Control: affects -1 + src:gnome-initial-setup

Please unblock package gnome-initial-setup

[ Reason ]
Fix UI glitches observed while testing fixes for #1029821

[ Impact ]
If not fixed, the full-screen "out of box experience" app shown on the
first login to GNOME, after initial installation or creating a new user,
is less polished than it should be.

The main fix since bookworm is that for users in locales that use a
non-trivial IBus input method rather than a simple Xkb keyboard layout
(Chinese, Japanese, Hindi, etc.), the default input method was mislabelled
and did not always appear. (#1032382)

This version also has an upstream change backported from upstream version
44.rc, fixing a regression that caused the shortlist of plausible
non-default keyboard layouts and input methods to be empty. There is
still a known bug that the shortlist is not very *useful* (it does not
have enough information to be weighted towards commonly-used keyboard
layouts and input methods for the relevant country, and away from
rare/specialized layouts like Dvorak), but that's not a regression and
it's better than nothing.

It also includes smaller tweaks to ensure the gnome-initial-setup window
is appropriately labelled in Alt+Tab and the Overview.

[ Tests ]
Manually tested via the steps in debian/README.source of unstable's
gnome-initial-setup, using English and Japanese locales.

Also carried out an installation of bookworm in Japanese (using a
parallel installation in English as a reference for which button does
what) and before logging in to GNOME for the first time, logged in via
tty to upgrade gnome-initial-setup and all packages from src:gnome-desktop
to their unstable versions.

[ Risks ]
This is a highly visible package with code that is surprisingly
fragile internally, and my initial attempt at this patchset caused it
to crash; but I expect that a lot of people will be testing new GNOME
installs between now and release day, so we'll get regression reports
if appropriate.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

unblock gnome-initial-setup/43.2-4
diffstat for gnome-initial-setup-43.2 gnome-initial-setup-43.2

 data/gnome-initial-setup.desktop.in.in |1 
 debian/README.source   |   19 +
 debian/changelog   |   52 ++
 debian/control |2 
 debian/patches/Add-StartupWMClass-to-.desktop-file.patch   |   29 +
 debian/patches/driver-Set-a-non-trivial-window-title.patch |   28 +
 debian/patches/keyboard-Correctly-update-labels-for-IBus-engines.patch |  189 ++
 debian/patches/keyboard-Resort-refilter-list-when-picking-shortlist.patch  |   96 +
 debian/patches/keyboard-Update-filter-and-sort-when-the-display-name-cha.patch |   46 ++
 debian/patches/reenable-existing-user-mode.patch   |6 
 debian/patches/series  |5 
 gnome-initial-setup/gis-driver.c   |1 
 gnome-initial-setup/pages/keyboard/cc-input-chooser.c  |   86 +++-
 13 files changed, 529 insertions(+), 31 deletions(-)

diff -Nru gnome-initial-setup-43.2/data/gnome-initial-setup.desktop.in.in gnome-initial-setup-43.2/data/gnome-initial-setup.desktop.in.in
--- gnome-initial-setup-43.2/data/gnome-initial-setup.desktop.in.in	2022-12-02 15:11:34.0 +
+++ gnome-initial-setup-43.2/data/gnome-initial-setup.desktop.in.in	2023-03-09 12:51:50.0 +
@@ -10,3 +10,4 @@
 OnlyShowIn=GNOME;
 NoDisplay=true
 X-GNOME-HiddenUnderSystemd=@systemd_hidden@
+StartupWMClass=org.gnome.InitialSetup
diff -Nru gnome-initial-setup-43.2/debian/changelog gnome-initial-setup-43.2/debian/changelog
--- gnome-initial-setup-43.2/debian/changelog	2022-12-06 14:27:10.0 +
+++ gnome-initial-setup-43.2/debian/changelog	2023-03-06 23:46:19.0 +
@@ -1,3 +1,55 @@
+gnome-initial-setup (43.2-4) unstable; urgency=medium
+
+  * Team upload
+  * d/p/keyboard-Resort-refilter-list-when-picking-shortlist.patch:
+Add patch from upstream 44.rc to display more input methods and
+keyboard layouts without clicking the "more..." button. This has
+a known issue that the shortlist of keyboard layouts is often not
+particularly useful, but at least it includes the default and
+current layouts (possibly different) and some other possibilities.
+  * d/p/keyboard-Correctly-update-labels-for-IBus-engines.patch,
+d/p/keyboard-Update-filter-a

Processed: unblock: gnome-initial-setup/43.2-4

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:gnome-initial-setup
Bug #1032580 [release.debian.org] unblock: gnome-initial-setup/43.2-4
Added indication that 1032580 affects src:gnome-initial-setup

-- 
1032580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032580
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1032579: unblock: gnome-desktop/43.2-2

[Simon McVittie]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: gnome-desk...@packages.debian.org, 
debian-japan...@lists.debian.org
Control: affects -1 + src:gnome-desktop

Please unblock package gnome-desktop

[ Reason ]
Make default input method for ja_JP match what tasksel installs
(#1029821, grave)

[ Impact ]
If not accepted, Japanese-speaking users will find that gnome-initial-setup
leaves them without a working input method, unless they happen to have
installed ibus-anthy separately. This is because GNOME upstream prefers
to default to ibus-anthy, but Japanese-speaking Debian/Ubuntu users say
that ibus-mozc is a higher-quality default on architectures where it
is built, and therefore that's what task-japanese-gnome-desktop pulls in.

If this change is not accepted, then we should change tasksel to make
task-japanese-gnome-desktop pull in ibus-anthy instead of ibus-mozc
();
but Japanese-speaking users have told us that defaulting to ibus-anthy
would be unacceptable, so we have not gone that route.

[ Tests ]
Manually tested via the steps in debian/README.source of unstable's
gnome-initial-setup, both with ibus-mozc installed (reflecting what will
happen on x86 and ARM) and with only ibus-anthy installed (reflecting
what will happen on ppc64el and s390x, where ibus-mozc is unavailable
and ibus-anthy is the best thing available for Japanese users).

Also carried out an installation of bookworm in Japanese (using a
parallel installation in English as a reference for which button does
what) and before logging in to GNOME for the first time, logged in via
tty to upgrade gnome-initial-setup and all packages from src:gnome-desktop
to their unstable versions.

I can't read or write Japanese, so I can't tell the difference between
anthy and mozc; but in the Japanese installation,
`gsettings list-recursively` contained

org.gnome.desktop.input-sources sources [('xkb', 'jp'), ('ibus', 'mozc-jp')]

which seems like it's probably the desired result. Also, the option
selected in GNOME's menu of input methods by default is
"日本語 (Mozc)" which again seems plausibly correct.

[ Risks ]
The core change here is trivial: it's just replacing the name of one
IBus input method with another.

The hack to fall back to ibus-anthy if ibus-mozc isn't installed is
less trivial, but still straightforward. I wish we didn't have to do this,
but from what I understand of the problem, we need this for unconventional
CPU architectures.

If the accompanying gnome-initial-setup change (see separate unblock
request) is not accepted, then the UI will be sub-optimal (the ibus-mozc
option will appear as "mozc-jp" in the UI instead of the intended
"Japanese (Mozc)"), but that's not actually a regression: the same thing
happens today for ibus-anthy.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

unblock gnome-desktop/43.2-2
diffstat for gnome-desktop-43.2 gnome-desktop-43.2

 debian/changelog   |   25 ++
 debian/control |6 -
 debian/control.in  |4 -
 debian/libgnome-desktop-doc.lintian-overrides  |2 
 debian/patches/Fall-back-to-ibus-anthy-if-ibus-mozc-jp-is-unavailable.patch|   39 ++
 debian/patches/Use-mozc-as-the-default-input-source-for-Japanese.patch |   34 
 debian/patches/languages-Look-at-LOCPATH-before-compile-time-LIBLOCALEDI.patch |8 +-
 debian/patches/series  |2 
 libgnome-desktop/default-input-sources.h   |2 
 libgnome-desktop/gnome-languages.c |9 ++
 10 files changed, 119 insertions(+), 12 deletions(-)

diff -Nru gnome-desktop-43.2/debian/changelog gnome-desktop-43.2/debian/changelog
--- gnome-desktop-43.2/debian/changelog	2023-02-15 16:15:51.0 +
+++ gnome-desktop-43.2/debian/changelog	2023-03-05 18:11:37.0 +
@@ -1,3 +1,28 @@
+gnome-desktop (43.2-2) unstable; urgency=medium
+
+  * Team upload
+  * d/control.in: Fix Vcs-Git and Vcs-Browser syntax
+  * d/p/Use-mozc-as-the-default-input-source-for-Japanese.patch:
+Change the default input method for Japanese to mozc-jp, matching
+tasksel.
+mozc is pulled in as the most-preferred input method by
+task-japanese-desktop (uim-mozc) and task-japanese-gnome-desktop
+(ibus-mozc) on the architectures where it is available, notably
+x86 and ARM. There seems to be consensus among Japanese-speaking
+Debian and Ubuntu users that mozc is the best default input method,
+so make the default

Processed: unblock: gnome-desktop/43.2-2

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:gnome-desktop
Bug #1032579 [release.debian.org] unblock: gnome-desktop/43.2-2
Added indication that 1032579 affects src:gnome-desktop

-- 
1032579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Re: Bug#1032316: llvm-toolchain-15: is this version intended for Debian 12 'bookworm'?

[Christian Kastner]

(debian-ai, apologies for re-sending, I hit the wrong reply button.)

On 2023-03-08 18:21, Simon McVittie wrote:
> There is *a* version of llvm-toolchain-15 in bookworm, version 1:15.0.6-4,
> which is used by the rocm-hipamd_5.2.3-1 and mesa_22.3.3-1 in bookworm.
> I'm not suggesting that 1:15.0.6-4 should be *removed*. What I'm asking
> here is whether it's intended to be upgraded to 1:15.0.7-1 (or presumably
> a later version where #1029010 has been fixed), or kept at 1:15.0.6-4
Are the upstream differences between 15.0.6 and 15.0.7 that big?

I think for rocm-hipamd, the main issue is that 5.2.3-5 depends on
libclang-rt-15-dev, which was introduced to unstable by means of a
package split in 1:15.0.7-1.

I'm pretty sure rocm-hipamd could live with the version in bookworm, but
it would need a new upload to change the dependency to reflect the
pre-split view.

In fact, we almost went so far as to implement just that, but we let it
as-is after all, because we assumed that #1029010 would be resolved in
due time, one way or another.

Best,
Christian

Bug#1032483: marked as done (unblock: drawtiming/0.7.1-8)

[Debian Bug Tracking System]

Your message dated Thu, 9 Mar 2023 13:38:30 +0100
with message-id <740f7e78-387e-973e-03ab-178793573...@debian.org>
and subject line Re: Bug#1032483: unblock: drawtiming/0.7.1-8
has caused the Debian Bug report #1032483,
regarding unblock: drawtiming/0.7.1-8
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 ow...@bugs.debian.org
immediately.)


-- 
1032483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032483
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package drawtiming

[ Reason ]
Fixes RC bug #984038

[Tests]
autopkgtest & Piuparts testsed OK: 
https://piuparts.debian.org/sid/source/d/drawtiming.html
https://salsa.debian.org/electronics-team/drawtiming/-/pipelines/508918

[ Checklist ]
  [*] all changes are documented in the d/changelog
  [*] I reviewed all changes and I approve them
  [*] attach debdiff against the package in testing

unblock drawtiming/0.7.1-8

-- 
‎أحمد المحمودي (Ahmed El-Mahmoudy)
 Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
GPG Fingerprints:
 6E2E E4BB 72E2 F417 D066  6ABF 7B30 B496 A7EF 5761
 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7
diff --git a/debian/changelog b/debian/changelog
index 72d0df3..335b42e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,20 @@
+drawtiming (0.7.1-8) unstable; urgency=medium
+
+  [ Aymeric Agon-Rambosson ]
+  * Add repair-build-c++-17.patch (Closes: #984038).
+  * d/control:
+- Add bison to Build-Depends (needed by upstream Makefile).
+- Replace graphicsmagick with imagemagick to avoid segfault during
+  tests.
+- Replace gsfonts with fonts-urw-base35 (transition), and add
+  fonts-urw-base35 as explicit runtime dependency to prevent segfault.
+
+  [ أحمد المحمودي (Ahmed El-Mahmoudy) ]
+  * Add gitlab-ci.yml
+  * d/gbp.conf: switch to bullseye branch
+
+ -- أحمد المحمودي (Ahmed El-Mahmoudy)   
Sat, 04 Mar 2023 03:07:13 +0100
+
 drawtiming (0.7.1-7) unstable; urgency=medium
 
   [ Dima Kogan ]
diff --git a/debian/control b/debian/control
index ac4079c..5448bb6 100644
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,12 @@ Section: electronics
 Priority: optional
 Maintainer: Debian Electronics Team 

 Uploaders: أحمد المحمودي (Ahmed El-Mahmoudy) 

-Build-Depends: debhelper (>= 10), graphicsmagick-libmagick-dev-compat, 
pkg-config, gsfonts
+Build-Depends:
+ debhelper (>= 10),
+ libmagick++-6.q16-dev,
+ fonts-urw-base35,
+ pkg-config,
+ bison
 Standards-Version: 4.1.5
 Homepage: http://drawtiming.sourceforge.net/
 Vcs-Git: https://salsa.debian.org/electronics-team/drawtiming.git
@@ -11,7 +16,7 @@ Vcs-Browser: 
https://salsa.debian.org/electronics-team/drawtiming
 
 Package: drawtiming
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}, fonts-urw-base35
 Description: tool for documenting hardware designs through timing diagrams
  Drawtiming is a command-line tool for documenting hardware designs through
  timing diagrams. In inputs textual signal descriptions and outputs image
diff --git a/debian/gbp.conf b/debian/gbp.conf
index f9636dc..c3d8c22 100644
--- a/debian/gbp.conf
+++ b/debian/gbp.conf
@@ -1,3 +1,3 @@
 [DEFAULT]
 pristine-tar = False
-debian-branch = pkg-debian
+debian-branch = bullseye
diff --git a/debian/gitlab-ci.yml b/debian/gitlab-ci.yml
new file mode 100644
index 000..5c575a1
--- /dev/null
+++ b/debian/gitlab-ci.yml
@@ -0,0 +1,6 @@
+include:
+ - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml
+ - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml
+
+variables:
+ RELEASE: 'unstable'
diff --git a/debian/patches/repair-build-c++-17.patch 
b/debian/patches/repair-build-c++-17.patch
new file mode 100644
index 000..8c48ae4
--- /dev/null
+++ b/debian/patches/repair-build-c++-17.patch
@@ -0,0 +1,208 @@
+Description: Fix compile failures for newer g++ release
+Author: Thomas Sailer 
+Forwarded: yes
+Comment: Found on https://sourceforge.net/p/drawtiming/patches/12/
+--- a/src/parser.yy
 b/src/parser.yy
+@@ -42,13 +42,13 @@ statements:
+ statement { $$ = $1; deps.push_back ($1); }
+ | statements ',' statement { $$ = $3; deps.push_back ($3); }
+ | statements ';' statement { $$ = $3; deps.clear (); deps.push_back ($3); }
+-| statements CAUSE statement { $$ = $3; data.add_dependencies ($3, deps); 
++| statements CAUSE statement { $$ = $3; data_.add_dependencies ($3, deps); 
+ deps.clear (); deps.push_back ($3); }
+-| statements DELAY statement { $$ = $3; 

Bug#1032578: marked as done (unblock: gnome-shell/43.3-3)

[Debian Bug Tracking System]

Your message dated Thu, 9 Mar 2023 13:31:10 +0100
with message-id <03394153-4bcf-a09e-21bd-47199dc79...@debian.org>
and subject line Re: Bug#1032578: unblock: gnome-shell/43.3-3
has caused the Debian Bug report #1032578,
regarding unblock: gnome-shell/43.3-3
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 ow...@bugs.debian.org
immediately.)


-- 
1032578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032578
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: gnome-sh...@packages.debian.org
Control: affects -1 + src:gnome-shell

Please unblock package gnome-shell

[ Reason ]
Fix #1032497

[ Impact ]
Users with some triggering factor (not completely understood, but an
unreliable display connector is one possible culprit) will find that
the Shell is stuck and unresponsive once per 2-3 logins.

[ Tests ]
Manual testing (normal use of GNOME), and the bug reporter has confirmed
that they no longer see the bug with this updated version.

[ Risks ]
Straightforward patch backported from upstream 44.rc, looks obviously
correct. I've asked upstream to consider including this change in 43.4,
but they're concentrating on GNOME 44 deadlines right now so there has
been no response yet.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

unblock gnome-shell/43.3-3
diffstat for gnome-shell-43.3 gnome-shell-43.3

 debian/changelog   |   11 ++
 debian/patches/overview-Don-t-claim-to-be-SHOWN-when-HIDDEN-during-start.patch |   38 ++
 debian/patches/overview-Hide-when-failing-to-take-grab-at-end-of-startup.patch |   27 +++
 debian/patches/series  |2 
 js/ui/overview.js  |7 +
 5 files changed, 85 insertions(+)

diff -Nru gnome-shell-43.3/debian/changelog gnome-shell-43.3/debian/changelog
--- gnome-shell-43.3/debian/changelog	2023-03-02 09:14:28.0 +
+++ gnome-shell-43.3/debian/changelog	2023-03-08 11:09:54.0 +
@@ -1,3 +1,14 @@
+gnome-shell (43.3-3) unstable; urgency=medium
+
+  * Team upload
+  * d/p/overview-Don-t-claim-to-be-SHOWN-when-HIDDEN-during-start.patch,
+d/p/overview-Hide-when-failing-to-take-grab-at-end-of-startup.patch:
+Fix regression in 43.3 which could cause the shell to become
+unresponsive, for example if a display is plugged or unplugged during
+the startup animation. (Closes: #1032497)
+
+ -- Simon McVittie   Wed, 08 Mar 2023 11:09:54 +
+
 gnome-shell (43.3-2) unstable; urgency=medium
 
   * Team upload
diff -Nru gnome-shell-43.3/debian/patches/overview-Don-t-claim-to-be-SHOWN-when-HIDDEN-during-start.patch gnome-shell-43.3/debian/patches/overview-Don-t-claim-to-be-SHOWN-when-HIDDEN-during-start.patch
--- gnome-shell-43.3/debian/patches/overview-Don-t-claim-to-be-SHOWN-when-HIDDEN-during-start.patch	1970-01-01 01:00:00.0 +0100
+++ gnome-shell-43.3/debian/patches/overview-Don-t-claim-to-be-SHOWN-when-HIDDEN-during-start.patch	2023-03-08 11:09:54.0 +
@@ -0,0 +1,38 @@
+From: Sebastian Keller 
+Date: Wed, 1 Mar 2023 21:43:15 +0100
+Subject: overview: Don't claim to be SHOWN when HIDDEN during startup
+ animation
+
+When the overview gets hidden during the startup animation, the callback
+would still change the state to SHOWN, despite the overview not being
+shown.
+
+This can happen for example if a `monitors-changed` signal triggers a
+relayout during startup.
+
+Bug: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2514#note_1683525
+Bug: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6478
+Bug-Debian: https://bugs.debian.org/1032497
+Forwarded: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2667
+Origin: upstream, 44.rc, commit:bb42973730a1a96881cb63bf7c1e9fdc68fb9fba
+---
+ js/ui/overview.js | 6 ++
+ 1 file changed, 6 insertions(+)
+
+diff --git a/js/ui/overview.js b/js/ui/overview.js
+index a3540d4..cd4b01b 100644
+--- a/js/ui/overview.js
 b/js/ui/overview.js
+@@ -684,6 +684,12 @@ var Overview = class extends Signals.EventEmitter {
+ this._changeShownState(OverviewShownState.SHOWING);
+ 
+ this._overview.runStartupAnimation(() => {
++// Overview got hidden during startup animation
++if (this._shownState !== OverviewShownState.SHOWING) {
++callback(

Bug#1032578: unblock: gnome-shell/43.3-3

[Simon McVittie]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: gnome-sh...@packages.debian.org
Control: affects -1 + src:gnome-shell

Please unblock package gnome-shell

[ Reason ]
Fix #1032497

[ Impact ]
Users with some triggering factor (not completely understood, but an
unreliable display connector is one possible culprit) will find that
the Shell is stuck and unresponsive once per 2-3 logins.

[ Tests ]
Manual testing (normal use of GNOME), and the bug reporter has confirmed
that they no longer see the bug with this updated version.

[ Risks ]
Straightforward patch backported from upstream 44.rc, looks obviously
correct. I've asked upstream to consider including this change in 43.4,
but they're concentrating on GNOME 44 deadlines right now so there has
been no response yet.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

unblock gnome-shell/43.3-3
diffstat for gnome-shell-43.3 gnome-shell-43.3

 debian/changelog   |   11 ++
 debian/patches/overview-Don-t-claim-to-be-SHOWN-when-HIDDEN-during-start.patch |   38 ++
 debian/patches/overview-Hide-when-failing-to-take-grab-at-end-of-startup.patch |   27 +++
 debian/patches/series  |2 
 js/ui/overview.js  |7 +
 5 files changed, 85 insertions(+)

diff -Nru gnome-shell-43.3/debian/changelog gnome-shell-43.3/debian/changelog
--- gnome-shell-43.3/debian/changelog	2023-03-02 09:14:28.0 +
+++ gnome-shell-43.3/debian/changelog	2023-03-08 11:09:54.0 +
@@ -1,3 +1,14 @@
+gnome-shell (43.3-3) unstable; urgency=medium
+
+  * Team upload
+  * d/p/overview-Don-t-claim-to-be-SHOWN-when-HIDDEN-during-start.patch,
+d/p/overview-Hide-when-failing-to-take-grab-at-end-of-startup.patch:
+Fix regression in 43.3 which could cause the shell to become
+unresponsive, for example if a display is plugged or unplugged during
+the startup animation. (Closes: #1032497)
+
+ -- Simon McVittie   Wed, 08 Mar 2023 11:09:54 +
+
 gnome-shell (43.3-2) unstable; urgency=medium
 
   * Team upload
diff -Nru gnome-shell-43.3/debian/patches/overview-Don-t-claim-to-be-SHOWN-when-HIDDEN-during-start.patch gnome-shell-43.3/debian/patches/overview-Don-t-claim-to-be-SHOWN-when-HIDDEN-during-start.patch
--- gnome-shell-43.3/debian/patches/overview-Don-t-claim-to-be-SHOWN-when-HIDDEN-during-start.patch	1970-01-01 01:00:00.0 +0100
+++ gnome-shell-43.3/debian/patches/overview-Don-t-claim-to-be-SHOWN-when-HIDDEN-during-start.patch	2023-03-08 11:09:54.0 +
@@ -0,0 +1,38 @@
+From: Sebastian Keller 
+Date: Wed, 1 Mar 2023 21:43:15 +0100
+Subject: overview: Don't claim to be SHOWN when HIDDEN during startup
+ animation
+
+When the overview gets hidden during the startup animation, the callback
+would still change the state to SHOWN, despite the overview not being
+shown.
+
+This can happen for example if a `monitors-changed` signal triggers a
+relayout during startup.
+
+Bug: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2514#note_1683525
+Bug: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6478
+Bug-Debian: https://bugs.debian.org/1032497
+Forwarded: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2667
+Origin: upstream, 44.rc, commit:bb42973730a1a96881cb63bf7c1e9fdc68fb9fba
+---
+ js/ui/overview.js | 6 ++
+ 1 file changed, 6 insertions(+)
+
+diff --git a/js/ui/overview.js b/js/ui/overview.js
+index a3540d4..cd4b01b 100644
+--- a/js/ui/overview.js
 b/js/ui/overview.js
+@@ -684,6 +684,12 @@ var Overview = class extends Signals.EventEmitter {
+ this._changeShownState(OverviewShownState.SHOWING);
+ 
+ this._overview.runStartupAnimation(() => {
++// Overview got hidden during startup animation
++if (this._shownState !== OverviewShownState.SHOWING) {
++callback();
++return;
++}
++
+ if (!this._syncGrab()) {
+ callback();
+ return;
diff -Nru gnome-shell-43.3/debian/patches/overview-Hide-when-failing-to-take-grab-at-end-of-startup.patch gnome-shell-43.3/debian/patches/overview-Hide-when-failing-to-take-grab-at-end-of-startup.patch
--- gnome-shell-43.3/debian/patches/overview-Hide-when-failing-to-take-grab-at-end-of-startup.patch	1970-01-01 01:00:00.0 +0100
+++ gnome-shell-43.3/debian/patches/overview-Hide-when-failing-to-take-grab-at-end-of-startup.patch	2023-03-08 11:09:54.0 +
@@ -0,0 +1,27 @@
+From: Sebastian Keller 
+Date: Wed, 1 Mar 2023 21:48:45 +0100
+Subject: overview: Hide when failing to take grab at end of startup animation
+
+Otherwise keyboard input would be going to whatever window was
+preventi

Processed: unblock: gnome-shell/43.3-3

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:gnome-shell
Bug #1032578 [release.debian.org] unblock: gnome-shell/43.3-3
Added indication that 1032578 affects src:gnome-shell

-- 
1032578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032578
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1032577: marked as done (unblock: opendrop/3.3.1-5)

[Debian Bug Tracking System]

Your message dated Thu, 9 Mar 2023 13:04:25 +0100
with message-id 
and subject line Re: Bug#1032577: unblock: opendrop/3.3.1-5
has caused the Debian Bug report #1032577,
regarding unblock: opendrop/3.3.1-5
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 ow...@bugs.debian.org
immediately.)


-- 
1032577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: opend...@packages.debian.org
Control: affects -1 + src:opendrop

Please unblock package opendrop

[ Reason ]

opendrop had a grave bug which meant that Interfacial Tensions could
not be evaluated, which is half of the functionality of the program.
This is now fixed, so we should let the fixed version 3.3.1-5 into
bookworm.

[ Impact ]

opendrop 3.3.1-4 only half works. Contact angle calculations work, but
interfacial tension calculations do not. It makes it feel as if the
probram is completely broken.

[ Tests ]

debci tests pass.  The fixed functionality has been tested manually on
sample images files.

[ Risks ]

The patches fix_DBo_2f7dc0e.patch and pygobject_gtk3.patch are trivial.
Patch sundials_API6_cf9d5aa.patch is equivalent to (and improves upon)
sundials_nvector_API6.patch which was already in the archive.

[ Checklist ]
  [x ] all changes are documented in the d/changelog
  [x ] I reviewed all changes and I approve them
  [x ] attach debdiff against the package in testing

unblock opendrop/3.3.1-5
diff -Nru opendrop-3.3.1/debian/changelog opendrop-3.3.1/debian/changelog
--- opendrop-3.3.1/debian/changelog 2022-12-13 20:36:32.0 +0100
+++ opendrop-3.3.1/debian/changelog 2023-03-09 02:24:59.0 +0100
@@ -1,3 +1,16 @@
+opendrop (3.3.1-5) unstable; urgency=medium
+
+  * debian patch fix_DBo_2f7dc0e.patch applies upstream commit 2f7dc0e
+to fix analysis of Interfacial Tension.  Closes: #1032488.
+  * replace debian patch sundials_nvector_API6.patch with
+sundials_API6_cf9d5aa.patch applying upstream commit
+cf9d5aa (dev branch) to fix build with sundials 6.
+  * debian patch pygobject_gtk3.patch reduces gui errors by
+asserting use of Gtk 3.
+  * Standards-Version: 4.6.2
+
+ -- Drew Parsons   Thu, 09 Mar 2023 02:24:59 +0100
+
 opendrop (3.3.1-4) unstable; urgency=medium
 
   * debian/patches/sundials_nvector_API6.patch updates sundials
diff -Nru opendrop-3.3.1/debian/control opendrop-3.3.1/debian/control
--- opendrop-3.3.1/debian/control   2022-12-13 20:36:32.0 +0100
+++ opendrop-3.3.1/debian/control   2023-03-09 02:24:59.0 +0100
@@ -33,7 +33,7 @@
  gir1.2-gtk-3.0,
  scons,
  unzip,
-Standards-Version: 4.6.1
+Standards-Version: 4.6.2
 Homepage: http://opencolloids.com/
 Vcs-Browser: https://salsa.debian.org/debichem-team/opendrop
 Vcs-Git: https://salsa.debian.org/debichem-team/opendrop.git
diff -Nru opendrop-3.3.1/debian/patches/fix_DBo_2f7dc0e.patch 
opendrop-3.3.1/debian/patches/fix_DBo_2f7dc0e.patch
--- opendrop-3.3.1/debian/patches/fix_DBo_2f7dc0e.patch 1970-01-01 
01:00:00.0 +0100
+++ opendrop-3.3.1/debian/patches/fix_DBo_2f7dc0e.patch 2023-03-09 
02:24:59.0 +0100
@@ -0,0 +1,13 @@
+diff --git a/include/opendrop/younglaplace_detail.hpp 
b/include/opendrop/younglaplace_detail.hpp
+index d2aa671..837a77f 100644
+--- a/include/opendrop/younglaplace_detail.hpp
 b/include/opendrop/younglaplace_detail.hpp
+@@ -469,7 +469,7 @@ YoungLaplaceShape::step_DBo()
+ flag = ERKStepGetCurrentTime(arkode_mem_DBo, &told);
+ if (flag == ARK_MEM_NULL) throw std::runtime_error("ARK_MEM_NULL");
+ 
+-if (tcur == RCONST(0.0)) {
++if (told == RCONST(0.0)) {
+ // First step. Set tout to 0.1 to give a rough scale of t variable 
when using ARK_ONE_STEP.
+ tnext = told + RCONST(0.1);
+ } else {
diff -Nru opendrop-3.3.1/debian/patches/pygobject_gtk3.patch 
opendrop-3.3.1/debian/patches/pygobject_gtk3.patch
--- opendrop-3.3.1/debian/patches/pygobject_gtk3.patch  1970-01-01 
01:00:00.0 +0100
+++ opendrop-3.3.1/debian/patches/pygobject_gtk3.patch  2023-03-09 
02:24:59.0 +0100
@@ -0,0 +1,13 @@
+Index: opendrop/opendrop/utility/bindable/gextension/style.py
+===
+--- opendrop.orig/opendrop/utility/bindable/gextension/style.py
2022-12-13 11:13:16.230515410 +0100
 opendrop/opendrop/utility/bindable/gextension/style.py 2023-03-08 
00:52:19.570180380 +0100
+@@ -1,6 +1,8 @@
+ import weakref
+ from typing import Any
+ 
++from 

Bug#1032577: unblock: opendrop/3.3.1-5

[Drew Parsons]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: opend...@packages.debian.org
Control: affects -1 + src:opendrop

Please unblock package opendrop

[ Reason ]

opendrop had a grave bug which meant that Interfacial Tensions could
not be evaluated, which is half of the functionality of the program.
This is now fixed, so we should let the fixed version 3.3.1-5 into
bookworm.

[ Impact ]

opendrop 3.3.1-4 only half works. Contact angle calculations work, but
interfacial tension calculations do not. It makes it feel as if the
probram is completely broken.

[ Tests ]

debci tests pass.  The fixed functionality has been tested manually on
sample images files.

[ Risks ]

The patches fix_DBo_2f7dc0e.patch and pygobject_gtk3.patch are trivial.
Patch sundials_API6_cf9d5aa.patch is equivalent to (and improves upon)
sundials_nvector_API6.patch which was already in the archive.

[ Checklist ]
  [x ] all changes are documented in the d/changelog
  [x ] I reviewed all changes and I approve them
  [x ] attach debdiff against the package in testing

unblock opendrop/3.3.1-5
diff -Nru opendrop-3.3.1/debian/changelog opendrop-3.3.1/debian/changelog
--- opendrop-3.3.1/debian/changelog 2022-12-13 20:36:32.0 +0100
+++ opendrop-3.3.1/debian/changelog 2023-03-09 02:24:59.0 +0100
@@ -1,3 +1,16 @@
+opendrop (3.3.1-5) unstable; urgency=medium
+
+  * debian patch fix_DBo_2f7dc0e.patch applies upstream commit 2f7dc0e
+to fix analysis of Interfacial Tension.  Closes: #1032488.
+  * replace debian patch sundials_nvector_API6.patch with
+sundials_API6_cf9d5aa.patch applying upstream commit
+cf9d5aa (dev branch) to fix build with sundials 6.
+  * debian patch pygobject_gtk3.patch reduces gui errors by
+asserting use of Gtk 3.
+  * Standards-Version: 4.6.2
+
+ -- Drew Parsons   Thu, 09 Mar 2023 02:24:59 +0100
+
 opendrop (3.3.1-4) unstable; urgency=medium
 
   * debian/patches/sundials_nvector_API6.patch updates sundials
diff -Nru opendrop-3.3.1/debian/control opendrop-3.3.1/debian/control
--- opendrop-3.3.1/debian/control   2022-12-13 20:36:32.0 +0100
+++ opendrop-3.3.1/debian/control   2023-03-09 02:24:59.0 +0100
@@ -33,7 +33,7 @@
  gir1.2-gtk-3.0,
  scons,
  unzip,
-Standards-Version: 4.6.1
+Standards-Version: 4.6.2
 Homepage: http://opencolloids.com/
 Vcs-Browser: https://salsa.debian.org/debichem-team/opendrop
 Vcs-Git: https://salsa.debian.org/debichem-team/opendrop.git
diff -Nru opendrop-3.3.1/debian/patches/fix_DBo_2f7dc0e.patch 
opendrop-3.3.1/debian/patches/fix_DBo_2f7dc0e.patch
--- opendrop-3.3.1/debian/patches/fix_DBo_2f7dc0e.patch 1970-01-01 
01:00:00.0 +0100
+++ opendrop-3.3.1/debian/patches/fix_DBo_2f7dc0e.patch 2023-03-09 
02:24:59.0 +0100
@@ -0,0 +1,13 @@
+diff --git a/include/opendrop/younglaplace_detail.hpp 
b/include/opendrop/younglaplace_detail.hpp
+index d2aa671..837a77f 100644
+--- a/include/opendrop/younglaplace_detail.hpp
 b/include/opendrop/younglaplace_detail.hpp
+@@ -469,7 +469,7 @@ YoungLaplaceShape::step_DBo()
+ flag = ERKStepGetCurrentTime(arkode_mem_DBo, &told);
+ if (flag == ARK_MEM_NULL) throw std::runtime_error("ARK_MEM_NULL");
+ 
+-if (tcur == RCONST(0.0)) {
++if (told == RCONST(0.0)) {
+ // First step. Set tout to 0.1 to give a rough scale of t variable 
when using ARK_ONE_STEP.
+ tnext = told + RCONST(0.1);
+ } else {
diff -Nru opendrop-3.3.1/debian/patches/pygobject_gtk3.patch 
opendrop-3.3.1/debian/patches/pygobject_gtk3.patch
--- opendrop-3.3.1/debian/patches/pygobject_gtk3.patch  1970-01-01 
01:00:00.0 +0100
+++ opendrop-3.3.1/debian/patches/pygobject_gtk3.patch  2023-03-09 
02:24:59.0 +0100
@@ -0,0 +1,13 @@
+Index: opendrop/opendrop/utility/bindable/gextension/style.py
+===
+--- opendrop.orig/opendrop/utility/bindable/gextension/style.py
2022-12-13 11:13:16.230515410 +0100
 opendrop/opendrop/utility/bindable/gextension/style.py 2023-03-08 
00:52:19.570180380 +0100
+@@ -1,6 +1,8 @@
+ import weakref
+ from typing import Any
+ 
++from gi import require_version
++require_version("Gtk", "3.0")
+ from gi.repository import Gtk
+ 
+ from opendrop.utility.bindable.abc import Bindable
diff -Nru opendrop-3.3.1/debian/patches/series 
opendrop-3.3.1/debian/patches/series
--- opendrop-3.3.1/debian/patches/series2022-12-13 20:36:32.0 
+0100
+++ opendrop-3.3.1/debian/patches/series2023-03-09 02:24:59.0 
+0100
@@ -2,4 +2,6 @@
 no-git-version.patch
 pep517-scons-fix.patch
 pep517-scons-interpreter.patch
-sundials_nvector_API6.patch
+sundials_API6_cf9d5aa.patch
+fix_DBo_2f7dc0e.patch
+pygobject_gtk3.patch
diff -Nru opendrop-3.3.1/debian/patches/sundials_API6_cf9d5aa.patch 
opendrop-3.3.1/debian/patches/sundials_API6_cf9d5aa.patch
--- opendrop-3.3.1/debian/patches/sundials_API6_cf9d5aa.patch   1970-01-0

Processed: unblock: opendrop/3.3.1-5

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:opendrop
Bug #1032577 [release.debian.org] unblock: opendrop/3.3.1-5
Added indication that 1032577 affects src:opendrop

-- 
1032577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Re: testing security uploads to bookworm-security

[Salvatore Bonaccorso]

Hi Ansgar,

[Adding debian-wb-t...@lists.debian.org list]

On Thu, Mar 09, 2023 at 01:16:21AM +0100, Ansgar wrote:
> Hi,
> 
> Salvatore Bonaccorso writes:
> > python-cryptography/38.0.4-3~deb12u1 was uploaded to security-master
> > as source only upload, the upload got rejected with:
> >
> > | Source-only uploads to NEW are not allowed.
> 
> There were two issues:
> 
>  - The override sync from ftp-master to security-master was not handling
>the fancy new `-security` addition to suite names.
> 
>  - `bookworm-security` was still configured to not accept any uploads
>(as was done when the suite was created to prevent accidental
>uploads).
> 
> Both issues are now solved and the python-cryptography source upload was
> processed successfully.

Thank you for addressing both. I can confirm we have now partially
builds on the embargoed queue.

>From what I see there are the mipsel and mips64el builds missing and
according to a quick chat with Adam on IRC it is not that they are yet
just missing because of buildd overloaded. Actually bookworm-security
seems not yet configured to be handled by mipsel and mips64el buildds.

Wanna-build team, can you have a look and check the mipsel, mips64el
status (and actually if we are setup complete as well on buildd setup
for bookworm-security)?

Regards,
Salvatore