Re: guesoglc FTBFS: make[2]: *** No rule to make target '../src/glew.c', needed by 'libGLC_la-glew.lo'. Stop.

[Paul Wise]

Control: tags -1 + sid

On Tue, 7 Sep 2021 12:14:21 +0200 Helmut Grohne wrote:

> quesoglc fails to build from source in unstable.

This seems to have been caused by the update to autoconf, it does not
occur with bookworm and upgrading autoconf to sid causes the issue.

Looking at the config.log, the old autoconf seems to do the check
twice, which works the first time but fails the second time.

The g++ command-line is identical for all three of the checks.

The new autoconf seems to only do the check once, which then fails.

The failure with the old autoconf is due to missing -DGLEW_MX=1,
which is a bug in the patch adding GLEW mx support.

The failure with the new autoconf seems to be C++ related, the same
test file links successfully when named .c and built with gcc.

The difference is that autoconf 2.71 removed this from conftest.cpp:

   #ifdef __cplusplus
   extern "C"
   #endif

OTOH the library is entirely C not C++ so it should use conftest.c
instead of conftest.cpp for detecting the tests.

It looks like AX_CHECK_GLU pulls in C++ support, but as far as I can
tell it restores the language correctly after modifying it.

Moving the AX_CHECK_GLU check after the GLEW check fixes the build.

When I delete build/m4/ax_check_glu.m4 and try to use the one from
autoconf-archive, the build fails due to a circular dependency:

   configure.in:157: error: m4_require: circular dependency of 
AC_LANG_COMPILER(C++)

When I then add AC_PROG_CXX before AX_CHECK_GLU then that failure
doesn't happen and the build succeeds as conftest.c is used this time.

Unfortunately that workaround does not work for the original copy of
the AX_CHECK_GLU macro in the upstream tarball.

Removing use of AC_PROG_CXX/AC_LANG_PUSH/POP from the original copy of
the AX_CHECK_GLU macro in the upstream tarball works around the issue.

I have zero idea where to go from here but I'm going to apply that
workaround for now and the next upstream release will drop the embedded
code and m4 copies so should not be affected by this bug either.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Processed: gyrus: depends on amtk which has been abandoned upstream

[Debian Bug Tracking System]

Processing control commands:

> block 993922 by -1
Bug #993922 [src:amtk] amtk: abandoned upstream
993922 was blocked by: 993909 993929 993928
993922 was not blocking any bugs.
Added blocking bug(s) of 993922: 993931

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

Bug#993931: gyrus: depends on amtk which has been abandoned upstream

[Simon McVittie]

Source: gyrus
Version: 0.3.12-1
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs
Control: block 993922 by -1
X-Debbugs-Cc: Yavor Doganov , Jonathan Carter 

amtk has been frozen and archived upstream, and contributions are no longer
accepted. See https://gitlab.gnome.org/Archive/amtk and
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/564 for
more details.

The versions of gedit and devhelp on GNOME infrastructure stopped using
amtk at the same time they stopped using tepl, which is in a similar
situation (see #993909). I don't think amtk should be included in Debian 12.

The remaining packages that use amtk (genius, goodvibes and gyrus) will
either need to stop using amtk (and switch to making the same calls into
GTK that amtk does, but more directly), or fork it. If they fork it,
the former maintainer requests that they use a different name.

Note that in the case of this unmaintained Debian package, the use of amtk
is a Debian-specific patch (part of the port from GTK 2 to GTK 3) rather
than an upstream decision.

smcv

Bug#993932: gyrus: unmaintained upstream

[Simon McVittie]

Package: gyrus
Version: 0.3.12-1
Severity: important
Tags: upstream wontfix
X-Debbugs-Cc: Yavor Doganov , Jonathan Carter 

gyrus is unmaintained upstream, and has been archived and made read-only:
. Its most recent release was
in 2013.

The version in Debian is effectively a fork, moving it from GTK 2 to
GTK 3. However, there is no Debian maintainer since 2013 either
(see #732011). I don't think it's a good idea for Debian to contain
packages that nobody maintains, either upstream or downstream.

This particular program seems to be a network client, which means it is
probably security-sensitive. I'm also concerned that it's a special-purpose
administrative IMAP client, yet is documented to not support TLS/SSL.

If someone wants to maintain gyrus, I would recommend that they fork the
(abandoned) upstream project and become its new upstream maintainer.

Perhaps this package should be removed from testing/unstable? If anyone
wants it, they can retrieve the most recent version from bullseye.

smcv

Bug#981496: svtools: ship with bullseye?

[Adrian Bunk]

On Sun, Jan 31, 2021 at 10:35:45PM +0100, Chris Hofstaedtler wrote:
> Package: svtools
> Version: 0.6-4
> Severity: important
> 
> Hi,
> 
> the package "svtools" has been orphaned by its original maintainer
> over 7 years ago. The Debian maintainer was also the upstream
> maintainer. Upstream has archived the project, and the last change
> was over 9 years ago.
> 
> Is this still useful software? Should we continue to ship it?
> 
> If you are interested, please speak up now.
>...

Jan, you intend to addopt daemontools.

Can you check whether svtools is still useful for Debian
(and if yes, ideally also adopt it)?

> Chris

Thanks
Adrian

Processed: tagging 978840

[Debian Bug Tracking System]

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

> tags 978840 + ftbfs
Bug #978840 [src:java2html] java2html: ftbfs with autoconf 2.70
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#993957: (no subject)

[lkcl]

Package: schroot
Version: 1.6.10-12
Severity: important

schroot 1.6.10 (04 May 2014) fails with a continuous attempt to read
a non-existent subdirectory, /run/systemd/userdb, when operating a
type "directory" schroot.

a type "plain" does not have this same issue.

creating the missing subdirectory manually "allows" the schroot to "proceed"
without errors.

please - do not summarily dismiss this bugreport "just because systemd is
not installed".  it is a *CHROOT*.  it is *INAPPROPRIATE* to install
systemd or expect systemd to be a critical dependency within a MINIMALIST
chroot.

-- System Information:

(REMOVED DUE TO NOT BEING ON THE TARGET SYSTEM)

Kernel: Linux 5.6.0-1-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- no debconf information
openat(AT_FDCWD, "/run/systemd/userdb/", 
O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or 
directory)
openat(AT_FDCWD, "/run/systemd/userdb/", 
O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or 
directory)
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
mmap(NULL, 34359742464, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) 
= 0x7f6239d9f000
munmap(0x7f6a39da, 17179873280) = 0
openat(AT_FDCWD, "/etc/group", O_RDONLY|O_CLOEXEC) = 5
lseek(5, 0, SEEK_CUR)   = 0
fstat(5, {st_mode=S_IFREG|0644, st_size=660, ...}) = 0
read(5, "root:x:0:\ndaemon:x:1:\nbin:x:2:\ns"..., 4096) = 660
lseek(5, 0, SEEK_CUR)   = 660
read(5, "", 4096)   = 0
close(5)= 0
rt_sigprocmask(SIG_BLOCK, [HUP USR1 USR2 PIPE ALRM CHLD TSTP URG VTALRM PROF 
WINCH IO], [], 8) = 0
openat(AT_FDCWD, "/run/systemd/userdb/", 
O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or 
directory)
openat(AT_FDCWD, "/run/systemd/userdb/", 
O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or 
directory)
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
mmap(NULL, 68719480832, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) 
= 0x7f5239d9e000
munmap(0x7f6239d9f000, 34359742464) = 0
openat(AT_FDCWD, "/etc/group", O_RDONLY|O_CLOEXEC) = 5
lseek(5, 0, SEEK_CUR)   = 0
fstat(5, {st_mode=S_IFREG|0644, st_size=660, ...}) = 0
read(5, "root:x:0:\ndaemon:x:1:\nbin:x:2:\ns"..., 4096) = 660
lseek(5, 0, SEEK_CUR)   = 660
read(5, "", 4096)   = 0
close(5)= 0
rt_sigprocmask(SIG_BLOCK, [HUP USR1 USR2 PIPE ALRM CHLD TSTP URG VTALRM PROF 
WINCH IO], [], 8) = 0
openat(AT_FDCWD, "/run/systemd/userdb/", 
O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or 
directory)
openat(AT_FDCWD, "/run/systemd/userdb/", 
O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or 
directory)
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
mmap(NULL, 137438957568, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 
0) = -1 ENOMEM (Cannot allocate memory)
brk(0x564c49ed1000) = 0x562c49ed1000
mmap(NULL, 137439088640, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 
0) = -1 ENOMEM (Cannot allocate memory)
futex(0x7f723a5af1a0, FUTEX_WAKE_PRIVATE, 2147483647) = 0
munmap(0x7f5239d9e000, 68719480832) = 0
write(2, "E: ", 3)  = 3
write(2, "std::bad_alloc", 14)  = 14
write(2, "\n", 1)   = 1
close(4)= 0
close(3)= 0
exit_group(1)   = ?
+++ exited with 1 +++

Bug#993957:

[Adam D. Barratt]

On Wed, 2021-09-08 at 16:58 +0100, lkcl wrote:
> schroot 1.6.10 (04 May 2014) fails with a continuous attempt to read
> a non-existent subdirectory, /run/systemd/userdb, when operating a
> type "directory" schroot.
> 

So far as I can see from the strace output you provided, that doesn't
actually appear to be the cause of the failure. Rather, this does:

> rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
> mmap(NULL, 137438957568, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = -1 ENOMEM (Cannot allocate
> memory)
> brk(0x564c49ed1000) = 0x562c49ed1000
> mmap(NULL, 137439088640, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = -1 ENOMEM (Cannot allocate
> memory)
> futex(0x7f723a5af1a0, FUTEX_WAKE_PRIVATE, 2147483647) = 0
> munmap(0x7f5239d9e000, 68719480832) = 0
> write(2, "E: ", 3)  = 3
> write(2, "std::bad_alloc", 14)  = 14
> write(2, "\n", 1)   = 1
> close(4)= 0
> close(3)= 0
> exit_group(1)   = ?
> +++ exited with 1 +++

i.e. it failed due to an unsuccessful attempt to allocate 128GB of RAM,
rather than anything to do with systemd.

Regards,

Adam

Bug#993957:

[Adam D. Barratt]

On Wed, 2021-09-08 at 18:21 +0100, Adam D. Barratt wrote:
> On Wed, 2021-09-08 at 16:58 +0100, lkcl wrote:
> > schroot 1.6.10 (04 May 2014) fails with a continuous attempt to
> > read
> > a non-existent subdirectory, /run/systemd/userdb, when operating a
> > type "directory" schroot.
> > 
> 
> So far as I can see from the strace output you provided, that doesn't
> actually appear to be the cause of the failure. Rather, this does:
[...]
> i.e. it failed due to an unsuccessful attempt to allocate 128GB of
> RAM,
> rather than anything to do with systemd.
> 

and that's probably 
https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/1899414

Regards,

Adam

Bug#993957:

[Neil Williams]

On Wed, 08 Sep 2021 18:27:39 +0100
"Adam D. Barratt"  wrote:

> On Wed, 2021-09-08 at 18:21 +0100, Adam D. Barratt wrote:
> > On Wed, 2021-09-08 at 16:58 +0100, lkcl wrote:  
> > > schroot 1.6.10 (04 May 2014) fails with a continuous attempt to
> > > read
> > > a non-existent subdirectory, /run/systemd/userdb, when operating a
> > > type "directory" schroot.
> > >   
> > 
> > So far as I can see from the strace output you provided, that
> > doesn't actually appear to be the cause of the failure. Rather,
> > this does:  
> [...]
> > i.e. it failed due to an unsuccessful attempt to allocate 128GB of
> > RAM,
> > rather than anything to do with systemd.
> >   
> 
> and that's probably 
> https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/1899414
> 

The routine reportbug questions haven't been answered for this bug and
there are a few important elements:

1. What is installed in this schroot? 
2. What suite is used inside the chroot?
3. What suite is the external system?
4. What exact commands were used, including options.
5. To which groups does the user running those commands belong?
6. What system is running these commands? (Information on the reporting
system was removed but equivalent information about the running system
was not included).

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



pgpkIwu9kvaSQ.pgp
Description: OpenPGP digital signature

Bug#826911: marked as done (pepperflashplugin-nonfree: Missing man page for update-pepperflashplugin-nonfree)

[Debian Bug Tracking System]

Your message dated Wed, 08 Sep 2021 22:37:11 +
with message-id 
and subject line Bug#979047: Removed package(s) from unstable
has caused the Debian Bug report #826911,
regarding pepperflashplugin-nonfree: Missing man page for 
update-pepperflashplugin-nonfree
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.)


-- 
826911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826911
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pepperflashplugin-nonfree
Version: 1.8.2+nmu1
Severity: normal

Dear Maintainer,

The binary for updating pepperflash is missing a man page.

Additionally, the help text leaves out some flags such as --unverified which
are only discoverable by inspecting the source.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.5.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pepperflashplugin-nonfree depends on:
ii  binutils   2.26-10
ii  ca-certificates20160104
ii  debconf [debconf-2.0]  1.5.59
ii  gnupg  1.4.20-6
ii  libatk1.0-02.20.0-1
ii  libcairo2  1.14.6-1+b1
ii  libcurl3-gnutls7.47.0-1
ii  libfontconfig1 2.11.0-6.4
ii  libfreetype6   2.6.3-3+b1
ii  libgcc11:6.1.1-5
ii  libglib2.0-0   2.48.1-1
ii  libgtk2.0-02.24.30-2
ii  libnspr4   2:4.12-2
ii  libnss32:3.23-2
ii  libpango-1.0-0 1.40.1-1
ii  libpango1.0-0  1.40.1-1
ii  libstdc++6 6.1.1-5
ii  libx11-6   2:1.6.3-1
ii  libxext6   2:1.3.3-1
ii  libxt6 1:1.1.5-1
ii  wget   1.17.1-2

pepperflashplugin-nonfree recommends no packages.

Versions of packages pepperflashplugin-nonfree suggests:
pn  chromium   
pn  hal
pn  ttf-dejavu 
ii  ttf-mscorefonts-installer  3.6
pn  ttf-xfree86-nonfree

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.8.8+rm

Dear submitter,

as the package pepperflashplugin-nonfree has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/979047

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#978954: marked as done (pepperflashplugin-nonfree: should not be part of bookworm)

[Debian Bug Tracking System]

Your message dated Wed, 08 Sep 2021 22:37:11 +
with message-id 
and subject line Bug#979047: Removed package(s) from unstable
has caused the Debian Bug report #978954,
regarding pepperflashplugin-nonfree: should not be part of bookworm
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.)


-- 
978954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978954
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pepperflashplugin-nonfree
Version: 1.8.7
Severity: grave
Justification: renders package unusable

Dear Maintainer,

flash has been EOL today. Browsers are starting to block flash.
I think we should block this package goes into next release?

Yours,
Paul

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8), 
LANGUAGE=zh_TW:en_US
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pepperflashplugin-nonfree depends on:
ii  binutils 2.35.1-6
ii  ca-certificates  20200601
ii  libgcc-s110.2.1-3
ii  libstdc++6   10.2.1-3
ii  wget 1.20.3-1+b3

pepperflashplugin-nonfree recommends no packages.

Versions of packages pepperflashplugin-nonfree suggests:
ii  chromium   83.0.4103.116-3.1+b2
pn  ttf-dejavu 
pn  ttf-mscorefonts-installer  
pn  ttf-xfree86-nonfree

-- no debconf information


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.8.8+rm

Dear submitter,

as the package pepperflashplugin-nonfree has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/979047

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#979047: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

pepperflashplugin-nonfree |  1.8.8 | source, amd64, i386

--- Reason ---
RoQA; No longer work; upstream eol
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 979...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/979047

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Sean Whitton (the ftpmaster behind the curtain)

Bug#979047: Removed package(s) from unstable

[Debian FTP Masters]

Version: 1.8.8+rm

Dear submitter,

as the package pepperflashplugin-nonfree has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/979047

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Sean Whitton (the ftpmaster behind the curtain)

user autoc...@packages.debian.org, usertagging 993870

[Paul Wise]

user autoc...@packages.debian.org
usertags 993870 + autoconf-2.71
thanks

user autoc...@packages.debian.org, usertagging 993870

[Paul Wise]

user autoc...@packages.debian.org
usertags 993870 - autoconf-2.71
thanks