On Tue, Oct 4, 2022 at 3:05 PM Adrian Bunk <b...@debian.org> wrote:
>
> On Tue, Oct 04, 2022 at 02:57:07PM -0400, Jeremy Bicha wrote:
> > On Tue, Oct 4, 2022 at 2:54 PM Adrian Bunk <b...@debian.org> wrote:
> > > On Tue, Oct 04, 2022 at 02:49:37PM -0400, Jeremy Bicha wrote:
> > > > Control: severity -1 important
> > > >
> > > > Since gtkmm4.0 is new to Debian, a broken autopkgtest isn't a
> > > > regression and doesn't block migration to Testing.
> >
> > I think that's a bug in the testing migration. I don't believe it's
> > supposed to block in this case.
>
> autopkgtest failures in testing are release critical bugs,
> blocking prevents an RC bug from entering testing.
I don't think so? I believe there are autopkgtests that have always
failed in Testing.
Anyway, here's the current failure:
gtktest.cc: In function ‘void {anonymous}::do_quit()’:
gtktest.cc:10:10: error: ‘Gtk::Main’ has not been declared
10 | Gtk::Main::quit();
| ^~~~
gtktest.cc: In function ‘int main(int, char**)’:
gtktest.cc:18:10: error: ‘Main’ is not a member of ‘Gtk’
18 | Gtk::Main main_instance (&argc, &argv);
| ^~~~
gtktest.cc:24:10: error: ‘Gtk::Main’ has not been declared
24 | Gtk::Main::run();
| ^~~~
The gtkmm4 documentation provides an example ("Hello, world") app but
it works differently. I don't have much experience with gtkmm coding
or C++. We'll need to decide whether we want to just use their example
or tweak what we copied from gtkmm3. Or just drop our custom basic
app.
Jeremy Bicha
