date:20211106

Package: wnpp
Severity: wishlist
Owner: Mathias Gibbens 
X-Debbugs-CC: debian-de...@lists.debian.org, debian...@lists.debian.org

* Package name: golang-github-go-macaroon-bakery-macaroonpb
  Version : 1.0.0-1
  Upstream Author : Roger Peppe, Canonical Inc
* URL : https://github.com/go-macaroon-bakery/macaroonpb
* License : LGPL-3.0-with-exception
  Programming Lang: Go
  Description : Protobuf encoding used by macaroon-bakery

 This module defines the serialization format of macaroon identifiers
 for macaroons created by the macaroon-bakery. For the most part this
 encoding is considered an internal implementation detail of the
 macaroon-bakery and external applications should not rely on any of the
 details of this encoding being maintained between different bakery versions.
 .
 This is broken out into a separate module as the protobuf implementation
 works in such a way that one cannot have multiple definitions of a
 message in any particular application's dependency tree. This module
 therefore provides a common definition for use by multiple versions of
 the macaroon-bakery to facilitate easier migration in client applications.

This package is a dependency for packaging golang-gopkg-macaroon-
bakery.v2, which is in turn a dependency for LXD (ITP #768073).

This package will be team-maintained within the Debian Go Packaging
Team.


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

Bug#998713: adb: inconsistency between package description and dependencies

2021-11-06 Thread Vincent Lefevre

Package: adb
Version: 1:29.0.6-1
Severity: minor

$ dpkg -s adb
[...]
Replaces: android-tools-adb (<< 6.0~)
Provides: android-tools-adb
Depends: android-sdk-platform-tools-common (>= 28.0.2~), libc6 (>= 2.32), 
libgcc-s1 (>= 3.0), libstdc++6 (>= 9), libusb-1.0-0 (>= 2:1.0.16)
Breaks: android-tools-adb (<< 6.0~)
Description: Android Debug Bridge
 A versatile command line tool that lets you communicate with an emulator
 instance or connected Android-powered device.
 .
 This package recommends "android-sdk-platform-tools-common" which contains
 the udev rules for Android devices. Without this package, adb and fastboot need
 to be running with root permission.
[...]

The description says

  This package recommends "android-sdk-platform-tools-common"

but adb actually depends on it. So "recommends" needs to be changed
to "depends on" (unless the intent is to changed this dependency to
a Recommends).

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages adb depends on:
ii  android-sdk-platform-tools-common  28.0.2+3
ii  libc6  2.32-4
ii  libgcc-s1  11.2.0-10
ii  libstdc++6 11.2.0-10
ii  libusb-1.0-0   2:1.0.24-3

adb recommends no packages.

adb suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#998712: irrlicht: invalid Uploaders field: missing comma between Vincent Cheng and Julien Puydt

2021-11-06 Thread Paul Wise

Source: irrlicht
Version: 1.8.4+dfsg1-2
Severity: serious
Justification: Policy 5.6.3

irrlicht 1.8.4+dfsg1-2 introduced an invalid uploaders field, that is
missing a comma between Vincent Cheng and Julien Puydt.

   $ apt-cache showsrc irrlicht | grep -E '^$|^Version|^Uploaders'
   Version: 1.8.4+dfsg1-1.1
   Uploaders: Christoph Egger , Vincent Cheng 

   
   Version: 1.8.4+dfsg1-2
   Uploaders: Vincent Cheng  Julien Puydt 

According to Debian policy 5.6.3 the Uploaders field must separate
individual uploaders using commas:

   List of the names and email addresses of co-maintainers of the
   package, if any.
   ...
   The format of each entry is the same as that of the Maintainer
   field, and multiple entries must be comma separated.

This is causing the DDPO and BLS cron jobs to send error mails.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#997942: tomboy-ng: FTBFS with fpc 3.2.2

2021-11-06 Thread David Bannon

I was advised a week ago that the app I maintain is not building in
unstable as the compiler (fpc) has been updated. 

However, Testing still has the 'older' compiler and it builds fine with
that. How do I test my build against tools only available in sid ?

Background -
---
tomboy-ng is built using Free Pascal Compiler and Lazarus. Testing has
FPC3.2.0 but apparently sid has FPC3.2.2. Obviously, I can get (have
already got) FPC direct from its source but I have found the need to
test, for Debian, using Debian supplied tools.

I obtained my Testing from 
https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/, its
dated 1st November. Should I be using something else ?

My fix is trivial, my scripts (stupidly) includes a test that accepts
only FPC 3.2.0.

But I would prefer to update the release anyway, the version of tomboy-
ng in Bullseye has issues that flowed from Debian's decision to drop
libappindicator3 in favour of libayana (and, not surprisingly, they
have different file names!).

Davo

On Wed, 2021-10-27 at 14:11 +0200, Graham Inggs wrote:
> Source: tomboy-ng
> Version: 0.32-2
> Severity: serious
> Tags: ftbfs bookworm sid
> 
> Hi Maintainer
> 
> tomboy-ng fails to build from source since fpc 3.2.2 was uploaded to
> unstable.  I've copied what I hope is the relevant part of the log
> below.
> 
> Regards
> Graham
> 
> 
> make[1]: Entering directory '/build/1st/tomboy-ng-0.32'
> == We have compiled [tomboy-ng]
> == $BIN_DIR is [/usr/bin]
> bash ./buildit.bash
> /usr/bin/which: this version of `which' is deprecated; use `command
> -v' in scripts instead.
> /usr/bin/which: this version of `which' is deprecated; use `command
> -v' in scripts instead.
> Compiler reported [3.2.2]
> Unclear about your compiler, maybe edit script to support new one,
> exiting ...
> make[1]: *** [Makefile:36: tomboy-ngx86_64] Error 1

Bug#997638: nas: FTBFS: ar: libdeps specified more than once

2021-11-06 Thread Steve McIntyre

Control: reassign -1 imake
Control: forcemerge -1 997628
Control: affects 997628 src:nas

So I've looked into this and I can see that this is not a bug in nas
directly, but a disagreement between imake and binutils. Assigning to
imake for now, in the same fashion as #997628

On Sat, Oct 23, 2021 at 11:18:44PM +0200, Lucas Nussbaum wrote:
>Source: nas
>Version: 1.9.4-7
>Severity: serious
>Justification: FTBFS
>Tags: bookworm sid ftbfs
>User: lu...@debian.org
>Usertags: ftbfs-20211023 ftbfs-bookworm
>
>Hi,
>
>During a rebuild of all packages in sid, your package failed to build
>on amd64.
>
>
>Relevant part (hopefully):
>> make[4]: Entering directory '/<>/server/dia'
>> rm -f dispatch.o
>> gcc -c -g -O2 -fno-strict-aliasing -g -O2 
>> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
>> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fcommon   -I. 
>> -I../include -I../../include -I../../lib/audio -I../../include-Dlinux 
>> -D__amd64__ -D_POSIX_C_SOURCE=199309L  
>> -D_POSIX_SOURCE -D_XOPEN_SOURCE 
>> -D_BSD_SOURCE -D_SVID_SOURCE 
>> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64   
>> -DFUNCPROTO=15 -DNARROWPROTO   
>> -DNASCONFSEARCHPATH=\"/etc/nas/\"   dispatch.c
>> In file included from 
>> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>>  from /usr/include/string.h:26,
>>  from ../include/os.h:124,
>>  from ../include/misc.h:57,
>>  from dispatch.c:52:
>> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
>> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
>> _DEFAULT_SOURCE"
>>   |   ^~~
>> rm -f dixutils.o
>> gcc -c -g -O2 -fno-strict-aliasing -g -O2 
>> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
>> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fcommon   -I. 
>> -I../include -I../../include -I../../lib/audio -I../../include-Dlinux 
>> -D__amd64__ -D_POSIX_C_SOURCE=199309L  
>> -D_POSIX_SOURCE -D_XOPEN_SOURCE 
>> -D_BSD_SOURCE -D_SVID_SOURCE 
>> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64   
>> -DFUNCPROTO=15 -DNARROWPROTO   
>> -DNASCONFSEARCHPATH=\"/etc/nas/\"   dixutils.c
>> In file included from 
>> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>>  from /usr/include/string.h:26,
>>  from ../include/os.h:124,
>>  from ../include/misc.h:57,
>>  from dixutils.c:52:
>> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
>> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
>> _DEFAULT_SOURCE"
>>   |   ^~~
>> rm -f events.o
>> gcc -c -g -O2 -fno-strict-aliasing -g -O2 
>> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
>> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fcommon   -I. 
>> -I../include -I../../include -I../../lib/audio -I../../include-Dlinux 
>> -D__amd64__ -D_POSIX_C_SOURCE=199309L  
>> -D_POSIX_SOURCE -D_XOPEN_SOURCE 
>> -D_BSD_SOURCE -D_SVID_SOURCE 
>> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64   
>> -DFUNCPROTO=15 -DNARROWPROTO   
>> -DNASCONFSEARCHPATH=\"/etc/nas/\"   events.c
>> In file included from 
>> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>>  from /usr/include/string.h:26,
>>  from ../include/os.h:124,
>>  from ../include/misc.h:57,
>>  from events.c:52:
>> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
>> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
>> _DEFAULT_SOURCE"
>>   |   ^~~
>> rm -f globals.o
>> gcc -c -g -O2 -fno-strict-aliasing -g -O2 
>> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
>> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fcommon   -I. 
>> -I../include -I../../include -I../../lib/audio -I../../include-Dlinux 
>> -D__amd64__ -D_POSIX_C_SOURCE=199309L  
>> -D_POSIX_SOURCE -D_XOPEN_SOURCE 
>> -D_BSD_SOURCE -D_SVID_SOURCE 
>> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64   
>> -DFUNCPROTO=15 -DNARROWPROTO   
>> -DNASCONFSEARCHPATH=\"/etc/nas/\"   globals.c
>> In file included from 
>>

Bug#996833: Please include information whether system is usrmerged or not

2021-11-06 Thread Marco d'Itri

On Oct 19, Michael Biebl  wrote:

> I'd make this pretty straighforward and simply check if
> /lib is a symlink to /usr/lib and
> /bin a symlink to /usr/bin
The usrmerge package itself uses just:

[ "$(readlink -f /lib)" = '/usr/lib' ]

It is guaranteed that if /lib has been converted then /bin and /sbin 
will also have been.

-- 
ciao,
Marco

signature.asc
Description: PGP signature

Bug#982975: RFS: rsplib/3.3.3~test2-1 [ITP] -- Reliable Server Pooling


Control: tags -1 moreinfo

debian/copyright: copyright info missing. See src/sha1.c and 
src/storage/sha512.c.

Remove changelog.dist and empty *.manpages, and empty d/tests/control.

Bug#974185: cross.patch

2021-11-06 Thread Thorsten Alteholz


Hmm, after applying the patch, the build fails with something like:

  Makefile:738: *** Recursive variable 'CC' references itself (eventually).  
Stop.

and I have no idea why :-(

  Thorsten

Bug#997514: ctpl: FTBFS: dh_auto_test: error: make -j1 check VERBOSE=1 returned exit code 2

2021-11-06 Thread Colomban Wendling

On Sat, 23 Oct 2021 22:42:41 +0200 Lucas Nussbaum  wrote:
> […]
> > FAIL: tests.sh
> > ==
> > 
> > ./tests.sh: 35: tempfile: not found

Looks like it's breaking because `tempfile` is gone, but that's an easy
fix I just committed upstream, see
https://git.tuxfamily.org/ctpl/ctpl.git/commit/?id=932f7767af15592fc36137a868187e45dea80068

Regards,
Colomban

Bug#998711: ITP: golang-github-juju-webbrowser -- Go helpers for interacting with Web browsers

Package: wnpp
Severity: wishlist
Owner: Mathias Gibbens 
X-Debbugs-CC: debian-de...@lists.debian.org, debian...@lists.debian.org

* Package name: golang-github-juju-webbrowser
  Version : 1.0.0-1
  Upstream Author : Canonical Ltd
* URL : https://github.com/juju/webbrowser
* License : LGPL-3.0
  Programming Lang: Go
  Description : Go helpers for interacting with Web browsers

 Go helpers for interacting with Web browsers.

This ITP reintroduces the golang-github-juju-webbrowser package to the
archive. It was previously RM'ed in #940504 as no packages depended on
it.

This package is a dependency for packaging golang-gopkg-macaroon-
bakery.v2, which is in turn a dependency for LXD (ITP #768073).

This package will be team-maintained within the Debian Go Packaging
Team.


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

Bug#968145: Upstream commit 6db92eab5917e515c83fd773dad6111177a0207f

2021-11-06 Thread Jeremy Harris


https://bugs.exim.org/show_bug.cgi?id=2822
--
Cheers,
  Jeremy

Bug#934297: RFS: bibtexconv

On 06.11.21 21:30, Thomas Dreibholz wrote:

Hi,

version test3 makes the following updates:

* changelog is merged, i.e. new entry + all old entries from unstable. In the
new entry, all items
from the changes after the latest "unstable" version are merged.
* Installation of examples with dh_installexamples.
* Installation of manpages with dh_installman.
* Updated standards version
* Removed empty test/control
* Removed OpenSSL exception from debian/copyright. BibTeXConv uses LibSSL's
MD5 computation
function (from shared library). In addition, it uses (by default) libcurl
with OpenSSL (from
shared library).

If the changes are okay, I would create an upstream release 1.3.1 (i.e. without ~testX), and a new
package.

Den 04.11.2021 22:54, skrev Bastian Germann:

Control: tags -1 moreinfo

On Thu, 02 Jan 2020 12:18:40 +0100 Tobias Frost wrote:

- Can you please merge the d/changelog entries for (in Debian)
unreleased versions?
- The Debian changelog seems incomplete, I see (packaing) changes which
are not documented. Please also try to expand a bit on the changes, e.g
did the SV update require you add changes? (documenting "why has this
changed" is important as additional information to the "what")

These were fixed.

- You do not need to specify the standards versions 4th digit, this
digit is for editorial changes only. So it is sufficient to declare
compatiblitliy with e.g 4.4.1 (which has been released since you put
this package to mentors)
- d/test/control is a empty file. I don't think that is right.

nitpicks:
d/compat can be obsoleted. (
https://nthykier.wordpress.com/2019/01/04/debhelper-compat-12-is-now-released/
)

Please correct these.

- Where do you get the OpenSSL exception from? I know you are the upstream but this exception
should be present in the source as well or should be removed from d/copyright. Debian does not
require it any longer.

- Please change the version and the origtarxz to actually match the released
version/file. No ~test0

- Add "(Closes: #975076)" to d/changelog's "New upstream release." line.

With these changes I am going to sponsor the package. Please untag moreinfo
when you are done.

Still I cannot see the changelog closing the bug.

Bug#986108: RFS: f3d/1.1.0-1 [ITP] -- fast and minimalist 3D viewer

2021-11-06 Thread François Mazen

Hello Bastian,

Thanks for the salsa Debian repository creation and copyright update!
In the meantime, I've updated the upstream issue with the binary
package information you've provided.

The only remaining item is the "data" folder. The copyright is
apparently the global BSD-3 licence, but I agree that the origin is
unclear. Fortunately, it looks like it's used for testing purpose only
so it would be OK to remove it from the Debian archive.

I propose to repack the source with the +dfsg prefix to remove this
folder. Do you agree?

Best,
François




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

Bug#998333: RFS: lebiniou/3.63.0-2 -- user-friendly, powerful music visualization / VJing tool

2021-11-06 Thread Olivier Girondel

Ok. Anyway I will release 3.63.1 tomorrow which fixes a FTBFS with the next 
libcaca version (beta20). Not in Debian yet, but already breaks on Arch and 
derivatives. 

On November 6, 2021 10:09:14 PM GMT+01:00, Bastian Germann  
wrote:
>Please keep the -1 revision.
>

Bug#998710: Subject: ITP: golang-gopkg-macaroon.v2 -- Native Go implementation of macaroons

Package: wnpp
Severity: wishlist
Owner: Mathias Gibbens 
X-Debbugs-CC: debian-de...@lists.debian.org, debian...@lists.debian.org

* Package name: golang-gopkg-macaroon.v2
  Version : 2.1.0-1
  Upstream Author : Roger Peppe
* URL : https://github.com/go-macaroon/macaroon
* License : BSD-3-clause
  Programming Lang: Go
  Description : Native Go implementation of macaroons

 The macaroon package implements macaroons as described in
 the paper "Macaroons: Cookies with Contextual Caveats for
 Decentralized Authorization in the Cloud"

This ITP reintroduces the golang-gopkg-macaroon.v2 package to the
archive. It was previously RM'ed in #917811 as no packages depended on
it.

This package is a dependency for packaging golang-gopkg-macaroon-
bakery.v2, which is in turn a dependency for LXD (ITP #768073).

This package will be team-maintained within the Debian Go Packaging
Team.


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

Bug#998709: Subject: ITP: golang-gopkg-macaroon-bakery.v2 -- High level operations for building systems with macaroons

Package: wnpp
Severity: wishlist
Owner: Mathias Gibbens 
X-Debbugs-CC: debian-de...@lists.debian.org, debian...@lists.debian.org

* Package name: golang-gopkg-macaroon-bakery.v2
  Version : 2.3.0-1
  Upstream Author : Roger Peppe, Canonical Inc
* URL : https://github.com/go-macaroon-bakery/macaroon-bakery
* License : LGPL-3.0-with-exception
  Programming Lang: Go
  Description : High level operations for building systems with macaroons

 This library is a companion to gopkg.in/macaroon.v2. It provides
 higher level operations for building systems with macaroons.

This ITP reintroduces the golang-gopkg-macaroon-bakery.v2 package to
the archive. It was previously RM'ed in #911001 as no packages depended
on it.

This package is a dependency for packaging LXD (ITP #768073).

This package will be team-maintained within the Debian Go Packaging
Team.


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

Bug#998668: anna: Make it possible to install with a mismatched kernel

2021-11-06 Thread Vagrant Cascadian

On 2021-11-06, Holger Wansing wrote:
> Vagrant Cascadian  wrote (Fri, 05 Nov 2021 18:13:58 
> -0700):
>>   
>> https://salsa.debian.org/installer-team/anna/-/commit/f6d5052a00df58c8f9d27d74c8ab585cc4d341e2
>> 
>>   commit f6d5052a00df58c8f9d27d74c8ab585cc4d341e2
>>   Author: Holger Wansing 
>>   Date:   Wed Nov 6 00:04:45 2019 +0100
>> 
>>   Change template, to give a senseful message to the user, when no
>>   kernel modules can be found. Also, turn that from a question into an
>>   error message, since continuing isn't possible without kernel modules
>>   anyway.
>> 
>> While I understand the motivation for making this a hard error in the
>> default case, there are valid use-cases for testing with a mismatched
>> kernel.
>> 
>> I used to rely on being able to skip this step when testing new arm*
>> platforms or platforms that depend on a newer kernel version or features
>> using a custom kernel, or where there is a mismatch in the kernel
>> version due to a recent ABI bump where debian-installer hasn't yet
>> caught up with the archive...
>> 
>> Maybe an explicit debconf question with low priority could be used to
>> skip this step instead of issuing a hard error? That way expert installs
>> or debconf preseeding could be used with the default images in the less
>> typical use cases...
>
> Hmm, isn't that exactly the situation, we had before the above mentioned 
> change?
>
> There were reasons, why this change was made:
> it was mentioned, that proceeding without kernel modules in the correct
> version isn't possible at all. (That was #749991, #367515.)
>
> Was that statement incorrect?

In most situations, hard-failing definitely does make sense!

It would be nice to be able to still override it when in expert mode or
some other mechanism.

The issue is that the appropriate kernel module .udeb packages might not
be available, even though the modules and/or features might actually be
available... it is *possible* to append modules for a custom kernel to
the initrd or build a kernel with the needed features built-in, without
having to rebuild debian-installer, and this is useful in various
debugging scenarios (notably, finicky arm platforms).


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#998708: Please upgrade to 6.9.1

2021-11-06 Thread Toni

Package: gradle
Version: 4.4.1-13
Severity: wishlist



Hi,

while trying to create a new version of the groovy package, I noticed,
that they ask for version 6.9.1 of gradle. It would be nice to have,
given that our current version is already three years old.


Thanks,
Toni



-- System Information:
Debian Release: 11.1
  APT prefers stable-security
  APT policy: (990, 'stable-security'), (990, 'stable'), (500, 
'stable-updates'), (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-9-amd64 (SMP w/12 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gradle depends on:
ii  default-jre-headless [java8-runtime-headless] 2:1.11-72
ii  libgradle-core-java   4.4.1-13
ii  libgradle-plugins-java4.4.1-13
ii  openjdk-11-jre-headless [java8-runtime-headless]  11.0.13+8-1~deb11u1
ii  openjdk-17-jre-headless [java8-runtime-headless]  17~19-1

gradle recommends no packages.

Versions of packages gradle suggests:
pn  gradle-doc  

-- no debconf information

Bug#998668: anna: Make it possible to install with a mismatched kernel

2021-11-06 Thread John Paul Adrian Glaubitz

Hello Holger!

On 11/6/21 21:13, Holger Wansing wrote:
> Hmm, isn't that exactly the situation, we had before the above mentioned 
> change?
> 
> There were reasons, why this change was made:
> it was mentioned, that proceeding without kernel modules in the correct
> version isn't possible at all. (That was #749991, #367515.)
> 
> Was that statement incorrect?

Well, the claim that you cannot continue without kernel modules is wrong.

As Vagrant explained, when you build a custom kernel to boot the machine, you 
don't
care about the kernel package or the module packages that are part of Debian as 
the
custom kernel already gets the machine up and running and provides device 
drivers,
filesystems and so on.

The installer can just install the system normally and install the distribution 
kernel,
ignoring that the running kernel is actually a different one. Once the system 
has been
installed, the user can just boot the installed system with the custom kernel.

There is no need to make this particular check a hard fail.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#996153: pipetty doesn't set window size

2021-11-06 Thread Adam Borowski

On Thu, Nov 04, 2021 at 09:18:47PM +0100, Jakub Wilk wrote:
> * Adam Borowski , 2021-10-12, 22:09:
> > One option would be providing a bogus size (such as 80x24 as getty on
> > serial does). I'm not sure, though, if it'd do more or less harm than
> > not providing a size at all.
> > 
> > On the other hand, lesstty in any non-erroneous case will be invoked
> > from a terminal -- I've thus just changed it to pass the size.
> 
> I'm not sure either.
> 
> I needed this for my own lesstty-like program. But in the mean time, I
> figured out I can easily set the terminal size myself:
> https://github.com/jwilk/pagerboy/commit/375bbbcdc3550483
> 
> Feel free to close the bug.

It's still valid wrt lesstty, thanks for noticing.

As for pipetty, I have no clue what to do, and unless you can push me either
way I'll simply leave as-is.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Polexit is brewing?  Let's skip that smelly Polsha and reactivate
⢿⡄⠘⠷⠚⠋⠀ the Free City of Danzig and/or reapply to the Hansa.
⠈⠳⣄

Bug#986108: RFS: f3d/1.1.0-1 [ITP] -- fast and minimalist 3D viewer


On 06.11.21 21:00, François Mazen wrote:

The only remaining item is the "data" folder. The copyright is
apparently the global BSD-3 licence, but I agree that the origin is
unclear. Fortunately, it looks like it's used for testing purpose only
so it would be OK to remove it from the Debian archive.

I propose to repack the source with the +dfsg prefix to remove this
folder. Do you agree?


Yes, please do that.

Bug#998333: RFS: lebiniou/3.63.0-2 -- user-friendly, powerful music visualization / VJing tool


Please keep the -1 revision.

Bug#998703: src:gnuastro: fails to migrate to testing for too long: ftbfs on mips64el

2021-11-06 Thread Mohammad Akhlaghi


Dear Paul,

Thank you very much for noticing this and marking the bug as fixed. 
Also, I really appreciate the great explanation of the significance of 
such situations, I completely agree.


The delay originated from the Debian version freezing: version 0.15 of 
Gnuastro came in that time slot (so it couldn't be updated in Debian). 
By the time the freeze was lifted, Gnuastro had significantly grown (and 
almost ready for version 0.16). But we pushed version 0.15 only to keep 
continuity.


It was only after uploading version 0.15 that we noticed the bug in 
'mips64el'. So we fixed it and pushed it with all the other bug fixes 
that had been found as version 0.15.54. Because the library had changed 
in this time, the new upload went to the NEW stack (on September 22nd). 
However, it was stuck in the NEW list for about 1.5 months (with one 
rejection due to bad copyright statement that was immediately fixed and 
re-submitted). Ultimately it was approved this morning!


Version 0.16 of Gnuastro is already released upstream [1], so as soon as 
Gnuastro 0.15.54 passes on all CPU architectures in the experimental 
branch [2], we will upload version 0.16 to 'testing'.


Thanks again,
Mohammad

[1] https://lists.gnu.org/archive/html/info-gnuastro/2021-10/msg0.html
[2] 
https://buildd.debian.org/status/package.php?p=gnuastro=experimental

Bug#998693: gitlab: Upgrade to 14.2.6 fails with undefined method `install_monkey_patches'

2021-11-06 Thread Maximilian Stein

> Remove this initializer. I have added rm_conffile to remove this 
automatically in debian/gitlab.maintscript but it seems to be not working.


Thanks for the prompt response, removing 
/usr/share/gitlab/config/initializers/transaction_metrics.rb did the 
trick. The installation finishes now.



Unfortunately, now gitlab-sidekiq fails to start since it is apparently 
trying to run a command with `sudo`:


Nov 06 21:58:21 zgitlab sudo[3253]: pam_unix(sudo:auth): conversation failed
Nov 06 21:58:21 zgitlab sudo[3253]: pam_unix(sudo:auth): auth could not 
identify password for [git]
Nov 06 21:58:21 zgitlab sudo[3253]:  git : user NOT in sudoers ; 
PWD=/usr/share/gitlab ; USER=root ; COMMAND=/bin/true
Nov 06 21:58:21 zgitlab gitlab-sidekiq[3251]: Bundler requires sudo 
access to install at the moment. Try installing again,
Nov 06 21:58:21 zgitlab gitlab-sidekiq[3251]: granting Bundler sudo 
access when prompted, or installing into a different path.
Nov 06 21:58:21 zgitlab systemd[1]: gitlab-sidekiq.service: Control 
process exited, code=exited, status=30/n/a





OpenPGP_signature
Description: OpenPGP digital signature

Bug#997016: RFS: swtpm/0.7.0-rc2-1 [ITA] -- Libtpms-based TPM emulator


Control: tags -1 moreinfo

On Thu, 4 Nov 2021 17:35:23 +0900 Seunghun Han wrote:

Please check the pipeline result below.
https://salsa.debian.org/debian/swtpm/-/pipelines/310288

Anyway, there are still some problems with reprotest and cross-build.
Should I solve them, too?


No, that can be done later. But I don't like the raised issue about the 
manpages sections.
The *.conf and *.options belong to section 5 instead of 8. Please hand in a patch upstream and then 
import it as a quilt patch (if there is no upstream release in between).


The code is authored (mostly) by Stefan Berger but copyrighted by IBM. For the BSD-3-clause license, 
the copyright notices have to be documented, not the author notices. Please correct that in 
d/copyright. Also the copyright year seem to range from 2006 to 2021.


configure.ac is CPL-licensed. Please document this in d/copyright.

Else this looks good to me.

Bug#998707: pcs: autopkgtest needs update for new version of pacemaker: error and warning message text changed

Source: pcs
Version: 0.10.8-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, pacema...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:pacemaker

Dear maintainer(s),

With a recent upload of pacemaker the autopkgtest of pcs fails in
testing when that autopkgtest is run with the binary packages of
pacemaker from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
pacemaker  from testing2.1.1-2
pcsfrom testing0.10.8-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of pacemaker to
testing [1]. Of course, pacemaker shouldn't just break your autopkgtest
(or even worse, your package), but it seems to me that the change in
pacemaker was intended and your package needs to update to the new
situation.

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from pacemaker should really
add a versioned Breaks on the unfixed version of (one of your)
package(s). Note: the Breaks is nice even if the issue is only in the
autopkgtest as it helps the migration software to figure out the right
versions to combine in the tests.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=pacemaker

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pcs/16475622/log.gz


==
FAIL: test_fail_when_nonexisting_agent
(pcs_test.tier1.cib_resource.test_create.FailOrWarn)
--
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.pw0aw2ju/downtmp/build.FKF/src/pcs_test/tier1/cib_resource/test_create.py",
line 934, in test_fail_when_nonexisting_agent
self.assert_pcs_fail(
  File
"/tmp/autopkgtest-lxc.pw0aw2ju/downtmp/build.FKF/src/pcs_test/tools/assertions.py",
line 93, in assert_pcs_fail
self.assert_pcs_result(
  File
"/tmp/autopkgtest-lxc.pw0aw2ju/downtmp/build.FKF/src/pcs_test/tools/assertions.py",
line 162, in assert_pcs_result
self.fail(
AssertionError: Stdout does not match the expected regexp
command: ['resource', 'create', 'R', 'ocf:heartbeat:NoExisting']
regexp:
^Error: Agent 'ocf:heartbeat:NoExisting' is not installed or does not
provide valid metadata:( crm_resource:)? Metadata query for
ocf:heartbeat:NoExisting failed: (-5|Input/output error)(, Error
performing operation: Input/output error)?, use --force to override
$ (flags: MULTILINE, UNICODE)

Full stdout:
Error: Agent 'ocf:heartbeat:NoExisting' is not installed or does not
provide valid metadata: crm_resource: Metadata query for
ocf:heartbeat:NoExisting failed: No such device or address, Error
performing operation: No such object, use --force to override


==
FAIL: test_warn_when_forcing_noexistent_agent
(pcs_test.tier1.cib_resource.test_create.FailOrWarn)
--
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.pw0aw2ju/downtmp/build.FKF/src/pcs_test/tier1/cib_resource/test_create.py",
line 952, in test_warn_when_forcing_noexistent_agent
self.assert_effect(
  File
"/tmp/autopkgtest-lxc.pw0aw2ju/downtmp/build.FKF/src/pcs_test/tools/cib.py",
line 91, in assert_effect
self.assert_effect_single(
  File
"/tmp/autopkgtest-lxc.pw0aw2ju/downtmp/build.FKF/src/pcs_test/tools/cib.py",
line 60, in assert_effect_single
self.assert_pcs_success(
  File
"/tmp/autopkgtest-lxc.pw0aw2ju/downtmp/build.FKF/src/pcs_test/tools/assertions.py",
line 81, in assert_pcs_success
self.assert_pcs_result(
  File
"/tmp/autopkgtest-lxc.pw0aw2ju/downtmp/build.FKF/src/pcs_test/tools/assertions.py",
line 162, in assert_pcs_result
self.fail(
AssertionError: Stdout does not match the expected regexp
command: ['resource', 'create', 'R', 'ocf:heartbeat:NoExisting', '--force']
regexp:
^Warning: Agent 'ocf:heartbeat:NoExisting' is not installed or does not
provide valid metadata:( crm_resource:)? Metadata query for
ocf:heartbeat:NoExisting failed: (-5|Input/output error)(, Error
performing operation: Input/output error)?
$ (flags: MULTILINE, UNICODE)

Full stdout:
Warning: Agent 'ocf:heartbeat:NoExisting' is not installed or does not
provide valid metadata: crm_resource: Metadata query for
ocf:heartbeat:NoExisting failed: No such device or address, Error
performing operation: No such object


==
FAIL: test_error_when_not_valid_agent
(pcs_test.tier1.cib_resource.test_stonith_create.PlainStonith)

Bug#998706: git breaks mercurial autopkgtest: Failed test-convert-git.t: output changed

Source: git, mercurial
Control: found -1 git/1:2.33.1-1
Control: found -1 mercurial/5.9.3-1
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of git the autopkgtest of mercurial fails in
testing when that autopkgtest is run with the binary packages of git
from unstable. It passes when run with only packages from testing. In
tabular form:

   passfail
gitfrom testing1:2.33.1-1
mercurial  from testing5.9.3-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of git to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=git

https://ci.debian.net/data/autopkgtest/testing/amd64/m/mercurial/16479536/log.gz

---
/tmp/autopkgtest-lxc.z9mlql5c/downtmp/build.H05/src/tests/test-convert-git.t
+++
/tmp/autopkgtest-lxc.z9mlql5c/downtmp/build.H05/src/tests/test-convert-git.t.err
@@ -51,43 +51,40 @@
   $ commit -a -m t4.2
   $ git checkout master >/dev/null 2>/dev/null
   $ git pull --no-commit . other > /dev/null 2>/dev/null
+  [128]
   $ commit -m 'Merge branch other'
+  git commit error
   $ cd ..
   $ hg convert --config extensions.progress= --config
progress.assume-tty=1 \
   >   --config progress.delay=0 --config progress.changedelay=0 \
   >   --config progress.refresh=0 --config progress.width=60 \
   >   --config progress.format='topic, bar, number' --datesort git-repo
   \r (no-eol) (esc)
-  scanning [==> ] 1/6\r
(no-eol) (esc)
-  scanning [=>  ] 2/6\r
(no-eol) (esc)
-  scanning [=>  ] 3/6\r
(no-eol) (esc)
-  scanning [>   ] 4/6\r
(no-eol) (esc)
-  scanning [===>] 5/6\r
(no-eol) (esc)
-  scanning [===>] 6/6\r
(no-eol) (esc)
-  \r
(no-eol) (esc)
-  \r (no-eol) (esc)
-  converting [  ] 0/6\r
(no-eol) (esc)
+  scanning [===>] 1/5\r
(no-eol) (esc)
+  scanning [>   ] 2/5\r
(no-eol) (esc)
+  scanning [=>  ] 3/5\r
(no-eol) (esc)
+  scanning [==> ] 4/5\r
(no-eol) (esc)
+  scanning [===>] 5/5\r
(no-eol) (esc)
+  \r
(no-eol) (esc)
+  \r (no-eol) (esc)
+  converting [  ] 0/5\r
(no-eol) (esc)
   getting files [==>] 1/2\r
(no-eol) (esc)
   getting files [==>] 2/2\r
(no-eol) (esc)
   \r
(no-eol) (esc)
   \r (no-eol) (esc)
-  converting [==>   ] 1/6\r
(no-eol) (esc)
+  converting [===>  ] 1/5\r
(no-eol) (esc)
   getting files [==>] 1/1\r
(no-eol) (esc)
   \r
(no-eol) (esc)
   \r (no-eol) (esc)
-  converting [=>] 2/6\r
(no-eol) (esc)
+  converting [===>  ] 2/5\r
(no-eol) (esc)
   getting files [==>] 1/1\r
(no-eol) (esc)
   \r
(no-eol) (esc)
   \r (no-eol) (esc)
-  converting [> ] 3/6\r
(no-eol) (esc)
+  converting [> ] 3/5\r
(no-eol) (esc)
   getting files [==>] 1/1\r
(no-eol) (esc)
   \r
(no-eol) (esc)
   \r (no-eol) (esc)
-  converting [===>  ] 4/6\r
(no-eol) (esc)
-  getting files [==>] 1/1\r
(no-eol) (esc)
-  \r
(no-eol) (esc)
-  \r (no-eol) (esc)
-  converting [==>   ] 5/6\r
(no-eol) (esc)
+  converting [> ] 4/5\r
(no-eol) (esc)
   getting files [==>] 1/1\r
(no-eol) (esc)

Bug#998704: src:lintian-brush: fails to migrate to testing for too long: blocked by breezy

Source: lintian-brush
Version: 0.109
Severity: serious
Control: close -1 0.114
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as having a Release Critical bug in
testing [1]. Your package src:lintian-brush has been trying to migrate
for 61 days [2]. Hence, I am filing this bug.

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. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

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.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bookworm, 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.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=lintian-brush




OpenPGP_signature
Description: OpenPGP digital signature

Bug#998703: src:gnuastro: fails to migrate to testing for too long: ftbfs on mips64el

Source: gnuastro
Version: 0.14-1
Severity: serious
Control: close -1 0.15-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as having a Release Critical bug in
testing [1]. Your package src:gnuastro has been trying to migrate for 61
days [2]. Hence, I am filing this bug.

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. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

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.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bookworm, 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.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=gnuastro




OpenPGP_signature
Description: OpenPGP digital signature

Bug#934297: RFS: bibtexconv

2021-11-06 Thread Thomas Dreibholz

Hi,

version test3 makes the following updates:

  * changelog is merged, i.e. new entry + all old entries from unstable.
In the new entry, all items from the changes after the latest
"unstable" version are merged.
  * Installation of examples with dh_installexamples.
  * Installation of manpages with dh_installman.
  * Updated standards version
  * Removed empty test/control
  * Removed OpenSSL exception from debian/copyright. BibTeXConv uses
LibSSL's MD5 computation function (from shared library). In
addition, it uses (by default) libcurl with OpenSSL (from shared
library).

If the changes are okay, I would create an upstream release 1.3.1 (i.e.
without ~testX), and a new package.

Den 04.11.2021 22:54, skrev Bastian Germann:
> Control: tags -1 moreinfo
>
> On Thu, 02 Jan 2020 12:18:40 +0100 Tobias Frost  wrote:
>> - Can you please merge the d/changelog entries for (in Debian)
>> unreleased versions?
>> - The Debian changelog seems incomplete, I see (packaing) changes which
>> are not documented. Please also try to expand a bit on the changes, e.g
>> did the SV update require you add changes? (documenting "why has this
>> changed" is important as additional information to the "what")
>
> These were fixed.
>
>> - You do not need to specify the standards versions 4th digit, this
>> digit is for editorial changes only. So it is sufficient to declare
>> compatiblitliy with e.g 4.4.1 (which has been released since you put
>> this package to mentors)
>> - d/test/control is a empty file. I don't think that is right.
>>
>> nitpicks:
>> d/compat can be obsoleted. (
>> https://nthykier.wordpress.com/2019/01/04/debhelper-compat-12-is-now-released/
>>
>> )
>
> Please correct these.
>
> - Where do you get the OpenSSL exception from? I know you are the
> upstream but this exception should be present in the source as well or
> should be removed from d/copyright. Debian does not require it any
> longer.
>
> - Please change the version and the origtarxz to actually match the
> released version/file. No ~test0
>
> - Add "(Closes: #975076)" to d/changelog's "New upstream release." line.
>
> With these changes I am going to sponsor the package. Please untag
> moreinfo when you are done.
>
-- 
Best regards / Mit freundlichen Grüßen / Med vennlig hilsen

===
 Thomas Dreibholz

 SimulaMet -- Simula Metropolitan Centre for Digital Engineering
 Centre for Resilient Networks and Applications
 Pilestredet 52
 0167 Oslo, Norway
---
 E-Mail: dre...@simula.no
 Homepage:   http://simula.no/people/dreibh
===



OpenPGP_signature
Description: OpenPGP digital signature

Bug#998415: [Pkg-rust-maintainers] Bug#998415: With a recent upload of rust-serde the autopkgtest of rust-debcargo, fails in testing when that autopkgtest is run with the binary packages, of rust-serd

Hi Ximin,

On 05-11-2021 21:43, Ximin Luo wrote:
> In other words, I don't see what value these bug reports are adding.

Most maintainers appreciate them. I'll try to remember to *not* file
them for rust packages anymore.

Please remember to resolve these issues in a timely fashion thou. Being
out-of-sync between unstable and testing for more than 60 days *is*
considered an RC (serious) bug [1].

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html



OpenPGP_signature
Description: OpenPGP digital signature

Bug#998701: broken link to lintian user's manual

2021-11-06 Thread Lee Garrett

Package: maint-guide
Version: 1.2.46
Severity: normal
X-Debbugs-Cc: deb...@rocketjump.eu

Chapter 5.14 links to https://lintian.debian.org/manual/index.html, however that
links returns a 404. I'm guessing that it hosted what is available under 
/usr/share/doc/lintian/lintian.html when you have lintian installed.


-- System Information:
Debian Release: 11.1
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 
'stable'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.14.5 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

maint-guide depends on no packages.

maint-guide recommends no packages.

Versions of packages maint-guide suggests:
pn  debian-policy 
pn  developers-reference  
ii  devscripts2.21.3+deb11u1
ii  dh-make   2.202003
pn  doc-base  
ii  dput  1.1.0
ii  fakeroot  1.25.3-1.1
ii  lintian   2.104.0
pn  pbuilder  
ii  quilt 0.66-2.1

-- no debconf information

Bug#998696: freeipmi: systemd build-dependencies prevent the package from building on kfreebsd

2021-11-06 Thread Fabio Fantoni


Il 06/11/2021 19:16, Laurent Bigonville ha scritto:

Source: freeipmi
Version: 1.6.6-3
Severity: important

Hello,

Since systemd and libsystemd-dev have been added to the BD, freeipmi is not 
built on
kfreebsd anymore.

Are you sure these dependencies are really needed? I tried to rebuild
the package and it build fine (and without any differences)


Hi, on latest versions I removed init files and keep only systemd ones 
(fixing some small things about), if I remember good kfreebsd is not 
supported anymore, or I'm wrong?


if should still be supported can be put [linux-any] on systemd and 
libsystemd-dev BDs but I don't have time to re-enable init services, 
test and fix them recently




Kind regards,
Laurent Bigonville


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

Kernel: Linux 5.14.0-3-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy





OpenPGP_signature
Description: OpenPGP digital signature

Bug#998685: ITP: node-cross-fetch -- Universal WHATWG Fetch API for Node, Browsers and React Native

2021-11-06 Thread Nicolas Mora


Hi Andrius,

Le 2021-11-06 à 15 h 15, Andrius Merkys a écrit :


In one of my packages I managed to drop-in replace cross-fetch with 
node-fetch [1], and it seems to work, just FYI. But since you have 
packaged cross-fetch, I will probably switch back to it. Thanks!


Yes, I saw that too and thought doing the same in the first time, but 
after a quick try, I saw that packaging cross-fetch isn't that hard, so 
I preferred packaging cross-fetch instead.


/Nicolas

Bug#998700: python-trio: Please package new upstream version

2021-11-06 Thread Boyuan Yang

Source: python-trio
Severity: normal
Version: 0.13.0-2
Tags: sid bookworm
X-Debbugs-CC: robie.ba...@canonical.com

Dear Debian python-trio package maintainer,

As listed on https://tracker.debian.org/pkg/python-trio , package python-trio
has new upstream releases that should be packaged. Please consider updating
this package in Debian.

Thanks,
Boyuan Yang


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

Bug#998699: python-trio: Please package new upstream version

2021-11-06 Thread Boyuan Yang

Package: python-trio
Severity: normal
Version: 0.13.0-2
Tags: sid bookworm
X-Debbugs-CC: robie.ba...@canonical.com

Dear Debian python-trio package maintainer,

As listed on https://tracker.debian.org/pkg/python-trio , package python-trio
has new upstream releases that should be packaged. Please consider updating
this package in Debian.

Thanks,
Boyuan Yang


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

Bug#998248: libencode-perl 3.00-1+deb10u1 flagged for acceptance

package release.debian.org
tags 998248 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: libencode-perl
Version: 3.00-1+deb10u1

Explanation: fix a memory leak in Encode.xs

Bug#996929: python-virtualenv 15.1.0+ds-2+deb10u1 flagged for acceptance

package release.debian.org
tags 996929 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: python-virtualenv
Version: 15.1.0+ds-2+deb10u1

Explanation: avoid attempting to install pkg_resources from PyPI

Bug#996695: plib 1.8.5-8+deb10u1 flagged for acceptance

package release.debian.org
tags 996695 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: plib
Version: 1.8.5-8+deb10u1

Explanation: fix integer overflow issue [CVE-2021-38714]

Bug#998685: ITP: node-cross-fetch -- Universal WHATWG Fetch API for Node, Browsers and React Native

2021-11-06 Thread Andrius Merkys


Hi Nicolas,

On 2021-11-06 14:26, Nicolas Mora wrote:
This package is required to use node-i18next-http-backend, therefore to 
fix #997718


In one of my packages I managed to drop-in replace cross-fetch with 
node-fetch [1], and it seems to work, just FYI. But since you have 
packaged cross-fetch, I will probably switch back to it. Thanks!


[1] 
https://salsa.debian.org/js-team/node-wikibase-edit/-/blob/master/debian/patches/replace-cross-fetch-with-node-fetch.patch


Best,
Andrius

Bug#951831: Please update to 3.x

2021-11-06 Thread Toni Mueller




Hello,

I would also like to see groovy updated to the latest 3.x, because
several aspects of Jenkins pipelines do not work with Groovy 2.4, or at
least, not as documented.


Thanks,
Toni

Bug#998247: libencode-perl 3.08-1+deb11u2 flagged for acceptance

package release.debian.org
tags 998247 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: libencode-perl
Version: 3.08-1+deb11u2

Explanation: fix a memory leak in Encode.xs

Bug#996694: plib 1.8.5-8+deb11u1 flagged for acceptance

package release.debian.org
tags 996694 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: plib
Version: 1.8.5-8+deb11u1

Explanation: fix integer overflow issue [CVE-2021-38714]

Bug#996283: open3d 0.9.0+ds-5+deb11u1 flagged for acceptance

package release.debian.org
tags 996283 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: open3d
Version: 0.9.0+ds-5+deb11u1

Explanation: ensure that python3-open3d depends on python3-numpy

Bug#994393: cmake 3.18.4-2+deb11u1 flagged for acceptance

package release.debian.org
tags 994393 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: cmake
Version: 3.18.4-2+deb11u1

Explanation: add PostgreSQL 13 to known versions

Bug#987996: RFS: hipercontracer [ITP]


On 06.11.21 19:51, Thomas Dreibholz wrote:

Hi,

the remaining issues should be fixed in version test2:

  * The only remaining changelog item is the ITP closing #997090
  * Dependencies without BOOST version
  * dh_installexamples is now installing the example files

Already in version test1 were fixed:

  * Removal of compat file
  * Rewrite of the postinst/postrm scripts
  * Removed cmake3 dependency alternative
  * Commented the lintian override



This still leaves us with:

- manpages should not be installed via *.install but via *.manpages.
- drop the empty d/tests/control and d/changelog.dist files.

Bug#997798: ITP: dedalus -- Dedalus is a framework for solving PDEs useful for astrophysical and geophysical fluid dynamics

2021-11-06 Thread Thaddeus H. Black

Usually not available for immediate reply, I was online when your
email arrived.

On Sat, Nov 06, 2021 at 09:09:17AM -0700, Mac Lee wrote:
> I haven't gotten a sponsor yet. Could you be my sponsor?

I would be glad.

I'll have to review your package when it's ready.  A package that works
on your own machine is a starting point; but in most cases, several
changes are required to polish a private package up to Debian's usual
level for general distribution.  My sponsor, Giacomo Catenazzi, guided
me to make such changes to my first package when he sponsored me
in 2004, so I am to do likewise for you.

I am not a prolific sponsor, having done it only once, and that over a
decade ago, so I'll be a bit rusty on the procedure; but you and I will
work it out.

Meanwhile, several questions:

1.  Have you already packaged the software as a *.deb that successfully
installs on your own machine?  (If not, then let me know if and how I
can help.)

2.  Have you read or reviewed Debian's New Maintainers' Guide?  (It can
be found among other places in the Developers' corner of the debian.org
web site).  If not then, when you have time, you'll probably want to
do that.

3.  Does your software build and run on bullseye?  On sid?  On both?

4.  Have you already chosen a package builder?  If not, there are two
or three, and you can use whichever you prefer; but for information,
pbuilder is the one with which I happen to be familiar.

5.  Does your software access the display (as via GTK, for example)?

Incidentally, the extent to which to continue to Cc our correspondence
to bugs.debian.org is up to you; but you can drop the Cc at your
discretion if you wish.


signature.asc
Description: PGP signature

Bug#940382: ITA: golang-github-juju-version

retitle 940382 ITA: golang-github-juju-version
owner 940382 !
block 940382 by 998185

Aleaxandre,

  I am willing to adopt this package, as it is one of the dependencies
for packaging LXD (ITP #768073). This package will continue to be
maintained under the Debian Go Packaging Team umbrella.

Mathias


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

Bug#990877: FTBFS on kfreebsd

2021-11-06 Thread Laurent Bigonville


Hello,

Any hope somebody could have a look at this? The patch is pretty trivial.

Kind regards,

Laurent Bigonville

Bug#998698: qtwayland5 should always be installed along with Qt

2021-11-06 Thread Richard B. Kreckel

Package: qtwayland5
Severity: normal
Version: 5.15.2-4

This plugin is way too important. Without it, Qt applications cannot be
executed when running a Wayland session. People will run in circles
trying to find out what's wrong. It doesn't hurt installing it.

Please feel free to reassign this bug.

  -richy.
-- 
Richard B. Kreckel

Bug#998697: ITP: bees -- a btrfs deduplication agent

2021-11-06 Thread Alexander GQ Gerasiov

Package: wnpp
Severity: wishlist
Owner: Alexander GQ Gerasiov 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: bees
  Version : 0.7
  Upstream Author : Zygo Blaxell b...@furryterror.org
* URL : https://github.com/Zygo/bees
* License : GPL-3+
  Programming Lang: C++
  Description : a btrfs deduplication agent

Best-Effort Extent-Same, a btrfs deduplication agent.

bees is a block-oriented userspace deduplication agent designed for large
btrfs filesystems. It is an offline dedupe combined with an incremental data
scan capability to minimize time data spends on disk from write to dedupe.

Bug#998696: freeipmi: systemd build-dependencies prevent the package from building on kfreebsd

2021-11-06 Thread Laurent Bigonville

Source: freeipmi
Version: 1.6.6-3
Severity: important

Hello,

Since systemd and libsystemd-dev have been added to the BD, freeipmi is not 
built on
kfreebsd anymore.

Are you sure these dependencies are really needed? I tried to rebuild
the package and it build fine (and without any differences)

Kind regards,
Laurent Bigonville


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

Kernel: Linux 5.14.0-3-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Bug#993174: RFS: dtkcore/5.5.17.1-1~exp1 -- Deepin Tool Kit Core library (utilities)


Control: tags -1 moreinfo

FTBFS on i386:

   dh_makeshlibs -a
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libdtkcore5/DEBIAN/symbols doesn't match completely 
debian/libdtkcore5.symbols

--- debian/libdtkcore5.symbols (libdtkcore5_5.5.17.1-1~exp1_i386)
+++ dpkg-gensymbolsHhxspe   2021-11-06 18:56:43.685494275 +0100
@@ -43,18 +43,23 @@
  _ZN3Dtk4Core11DThreadUtil17FunctionCallProxyD0Ev@Base 5.5.17.1
  _ZN3Dtk4Core11DThreadUtil17FunctionCallProxyD1Ev@Base 5.5.17.1
  _ZN3Dtk4Core11DThreadUtil17FunctionCallProxyD2Ev@Base 5.5.17.1
- _ZN3Dtk4Core11DVtableHook10copyVtableEPPy@Base 5.5.17.1
- _ZN3Dtk4Core11DVtableHook11originalFunEPKvy@Base 5.5.17.1
+ _ZN3Dtk4Core11DVtableHook10copyVtableEPPj@Base 5.5.17.1-1~exp1
+#MISSING: 5.5.17.1-1~exp1# _ZN3Dtk4Core11DVtableHook10copyVtableEPPy@Base 
5.5.17.1
+ _ZN3Dtk4Core11DVtableHook11originalFunEPKvj@Base 5.5.17.1-1~exp1
+#MISSING: 5.5.17.1-1~exp1# _ZN3Dtk4Core11DVtableHook11originalFunEPKvy@Base 
5.5.17.1
  _ZN3Dtk4Core11DVtableHook11resetVtableEPKv@Base 5.5.17.1
  _ZN3Dtk4Core11DVtableHook12ensureVtableEPKvSt8functionIFvvEE@Base 5.5.17.1
- _ZN3Dtk4Core11DVtableHook13resetVfptrFunEPKvy@Base 5.5.17.1
+ _ZN3Dtk4Core11DVtableHook13resetVfptrFunEPKvj@Base 5.5.17.1-1~exp1
+#MISSING: 5.5.17.1-1~exp1# _ZN3Dtk4Core11DVtableHook13resetVfptrFunEPKvy@Base 
5.5.17.1
  _ZN3Dtk4Core11DVtableHook14objDestructFunE@Base 5.5.17.1
  _ZN3Dtk4Core11DVtableHook15autoCleanVtableEPKv@Base 5.5.17.1
  _ZN3Dtk4Core11DVtableHook15objToGhostVfptrE@Base 5.5.17.1
  _ZN3Dtk4Core11DVtableHook16clearGhostVtableEPKv@Base 5.5.17.1
- _ZN3Dtk4Core11DVtableHook16forceWriteMemoryEPvPKvm@Base 5.5.17.1
+ _ZN3Dtk4Core11DVtableHook16forceWriteMemoryEPvPKvj@Base 5.5.17.1-1~exp1
+#MISSING: 5.5.17.1-1~exp1# 
_ZN3Dtk4Core11DVtableHook16forceWriteMemoryEPvPKvm@Base 5.5.17.1
  _ZN3Dtk4Core11DVtableHook18objToOriginalVfptrE@Base 5.5.17.1
- _ZN3Dtk4Core11DVtableHook19getDestructFunIndexEPPySt8functionIFvvEE@Base 
5.5.17.1
+ _ZN3Dtk4Core11DVtableHook19getDestructFunIndexEPPjSt8functionIFvvEE@Base 
5.5.17.1-1~exp1
+#MISSING: 5.5.17.1-1~exp1# _ZN3Dtk4Core11DVtableHook19getDestructFunIndexEPPySt8functionIFvvEE@Base 
5.5.17.1

  _ZN3Dtk4Core11DVtableHook7resolveEPKc@Base 5.5.17.1
  _ZN3Dtk4Core11DVtableHook9hasVtableEPKv@Base 5.5.17.1
  _ZN3Dtk4Core12DFileWatcher11onFileMovedERK7QStringS4_S4_S4_@Base 5.5.17.1
@@ -580,18 +585,30 @@
  _ZTVN3Dtk4Core7DObjectE@Base 5.5.17.1
  _ZTVN3Dtk4Core9DSettingsE@Base 5.5.17.1
  
_ZTVSt23_Sp_counted_ptr_inplaceI9DDBusDataSaIS0_ELN9__gnu_cxx12_Lock_policyE2EE@Base
 5.5.17.1
- _ZThn16_N3Dtk4Core12DFileWatcherD0Ev@Base 5.5.17.1
- _ZThn16_N3Dtk4Core12DFileWatcherD1Ev@Base 5.5.17.1
- _ZThn16_N3Dtk4Core13DTrashManagerD0Ev@Base 5.5.17.1
- _ZThn16_N3Dtk4Core13DTrashManagerD1Ev@Base 5.5.17.1
- _ZThn16_N3Dtk4Core16DBaseFileWatcherD0Ev@Base 5.5.17.1
- _ZThn16_N3Dtk4Core16DBaseFileWatcherD1Ev@Base 5.5.17.1
- _ZThn16_N3Dtk4Core18DFileSystemWatcherD0Ev@Base 5.5.17.1
- _ZThn16_N3Dtk4Core18DFileSystemWatcherD1Ev@Base 5.5.17.1
- _ZThn16_N3Dtk4Core19DFileWatcherManagerD0Ev@Base 5.5.17.1
- _ZThn16_N3Dtk4Core19DFileWatcherManagerD1Ev@Base 5.5.17.1
- _ZThn16_N3Dtk4Core5DUtil18DExportedInterfaceD0Ev@Base 5.5.17.1
- _ZThn16_N3Dtk4Core5DUtil18DExportedInterfaceD1Ev@Base 5.5.17.1
+#MISSING: 5.5.17.1-1~exp1# _ZThn16_N3Dtk4Core12DFileWatcherD0Ev@Base 5.5.17.1
+#MISSING: 5.5.17.1-1~exp1# _ZThn16_N3Dtk4Core12DFileWatcherD1Ev@Base 5.5.17.1
+#MISSING: 5.5.17.1-1~exp1# _ZThn16_N3Dtk4Core13DTrashManagerD0Ev@Base 5.5.17.1
+#MISSING: 5.5.17.1-1~exp1# _ZThn16_N3Dtk4Core13DTrashManagerD1Ev@Base 5.5.17.1
+#MISSING: 5.5.17.1-1~exp1# _ZThn16_N3Dtk4Core16DBaseFileWatcherD0Ev@Base 
5.5.17.1
+#MISSING: 5.5.17.1-1~exp1# _ZThn16_N3Dtk4Core16DBaseFileWatcherD1Ev@Base 
5.5.17.1
+#MISSING: 5.5.17.1-1~exp1# _ZThn16_N3Dtk4Core18DFileSystemWatcherD0Ev@Base 
5.5.17.1
+#MISSING: 5.5.17.1-1~exp1# _ZThn16_N3Dtk4Core18DFileSystemWatcherD1Ev@Base 
5.5.17.1
+#MISSING: 5.5.17.1-1~exp1# _ZThn16_N3Dtk4Core19DFileWatcherManagerD0Ev@Base 
5.5.17.1
+#MISSING: 5.5.17.1-1~exp1# _ZThn16_N3Dtk4Core19DFileWatcherManagerD1Ev@Base 
5.5.17.1
+#MISSING: 5.5.17.1-1~exp1# 
_ZThn16_N3Dtk4Core5DUtil18DExportedInterfaceD0Ev@Base 5.5.17.1
+#MISSING: 5.5.17.1-1~exp1# 
_ZThn16_N3Dtk4Core5DUtil18DExportedInterfaceD1Ev@Base 5.5.17.1
+ _ZThn8_N3Dtk4Core12DFileWatcherD0Ev@Base 5.5.17.1-1~exp1
+ _ZThn8_N3Dtk4Core12DFileWatcherD1Ev@Base 5.5.17.1-1~exp1
+ _ZThn8_N3Dtk4Core13DTrashManagerD0Ev@Base 5.5.17.1-1~exp1
+ _ZThn8_N3Dtk4Core13DTrashManagerD1Ev@Base 5.5.17.1-1~exp1
+ _ZThn8_N3Dtk4Core16DBaseFileWatcherD0Ev@Base 5.5.17.1-1~exp1
+ _ZThn8_N3Dtk4Core16DBaseFileWatcherD1Ev@Base 5.5.17.1-1~exp1
+ _ZThn8_N3Dtk4Core18DFileSystemWatcherD0Ev@Base 5.5.17.1-1~exp1
+ _ZThn8_N3Dtk4Core18DFileSystemWatcherD1Ev@Base 5.5.17.1-1~exp1
+ _ZThn8_N3Dtk4Core19DFileWatcherManagerD0Ev@Base 5.5.17.1-1~exp1

Bug#998695: RFS: lebiniou/3.63.0-2 -- user-friendly, powerful music visualization / VJing tool

2021-11-06 Thread Olivier Girondel




Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "lebiniou":

  * Package name: lebiniou
Version : 3.63.0-2
Upstream Author : Olivier Girondel 
  * URL : https://biniou.net
  * License : GPL-2+
Section : graphics

It builds this binary package:

   lebiniou - user-friendly, powerful music visualization / VJing tool

The package appears to be lintian-clean.

To access further information about this package, please visit the
following URL:

   https://mentors.debian.net/package/lebiniou

Alternatively, one can download the package with dget using this command:

   dget -x
https://mentors.debian.net/debian/pool/main/l/lebiniou/lebiniou_3.63.0-2.dsc

Changes since the last upload:

  * debian/copyright: Updated. (Closes: #998617)

Regards,

--
Olivier Girondel

Bug#998694: Don't timeout if you haven't asked for password yet

2021-11-06 Thread 積丹尼 Dan Jacobson

Package: login
Version: 1:4.8.1-1.1

(/usr/share/doc/login/copyright says
This is Debian GNU/Linux's prepackaged version of the shadow utilities.

It was downloaded from: .
As of May 2007, this site is no longer available.)

OK, I'll report the bug here:

Let's say the system is so overloaded that...

Login: root

Login timed out after 60 seconds

Yes, that's right, even before the password prompt appeared!

So that timeout will prevent access to the whole system!

So: at least don't timeout if you haven't asked for password yet!

Thanks.

Bug#998693: gitlab: Upgrade to 14.2.6 fails with undefined method `install_monkey_patches'

2021-11-06 Thread Maximilian Stein

Package: gitlab
Version: 14.2.6+ds1-2~fto11+1
Severity: important

Dear Maintainer,

Today I tried to upgrade from gitlab version 14.1.7+ds1-2~fto11+1 to
14.2.6+ds1-3~fto11+1. This failed unfortunately (see log below).

Best,
Maximilian


rake aborted!
NoMethodError: undefined method `install_monkey_patches' for 
Gitlab::Database:Module
Did you mean?  instance_methods
/usr/share/gitlab/config/initializers/transaction_metrics.rb:3:in `'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.1/lib/rails/engine.rb:681:in
 `load'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.1/lib/rails/engine.rb:681:in
 `block in load_config_initializer'
/usr/share/rubygems-integration/all/gems/activesupport-6.1.4.1/lib/active_support/notifications.rb:205:in
 `instrument'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.1/lib/rails/engine.rb:680:in
 `load_config_initializer'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.1/lib/rails/engine.rb:634:in
 `block (2 levels) in '
/usr/share/rubygems-integration/all/gems/railties-6.1.4.1/lib/rails/engine.rb:633:in
 `each'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.1/lib/rails/engine.rb:633:in
 `block in '
/usr/share/rubygems-integration/all/gems/railties-6.1.4.1/lib/rails/initializable.rb:32:in
 `instance_exec'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.1/lib/rails/initializable.rb:32:in
 `run'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.1/lib/rails/initializable.rb:61:in
 `block in run_initializers'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.1/lib/rails/initializable.rb:50:in
 `each'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.1/lib/rails/initializable.rb:50:in
 `tsort_each_child'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.1/lib/rails/initializable.rb:60:in
 `run_initializers'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.1/lib/rails/application.rb:391:in
 `initialize!'
/usr/share/gitlab/config/environment.rb:7:in `'
/usr/share/rubygems-integration/all/gems/activesupport-6.1.4.1/lib/active_support/dependencies.rb:332:in
 `block in require'
/usr/share/rubygems-integration/all/gems/activesupport-6.1.4.1/lib/active_support/dependencies.rb:299:in
 `load_dependency'
/usr/share/rubygems-integration/all/gems/activesupport-6.1.4.1/lib/active_support/dependencies.rb:332:in
 `require'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.1/lib/rails/application.rb:367:in
 `require_environment!'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.1/lib/rails/application.rb:533:in
 `block in run_tasks_blocks'
/usr/share/rubygems-integration/all/gems/rake-13.0.3/exe/rake:27:in `'
Tasks: TOP => db:migrate => db:load_config => environment

Bug#998692: ITP: golang-github-mdlayher-netx -- A collection of small Go networking packages

Package: wnpp
Severity: wishlist
Owner: Mathias Gibbens 
X-Debbugs-CC: debian-de...@lists.debian.org, debian...@lists.debian.org

* Package name: golang-github-mdlayher-netx
  Version : 0.0~git20200512.669a06f-1
  Upstream Author : Matt Layher
* URL : https://github.com/mdlayher/netx
* License : Expat
  Programming Lang: Go
  Description : A collection of small Go networking packages

 A collection of small Go networking packages:
   * eui64 enables creation and parsing of Modified EUI-64 format
 interface identifiers, as described in RFC 4291, Section 2.5.1
   * multinet allows combining multiple package net types into one
   * rfc4193 implements Unique Local IPv6 Unicast Address prefix
 generation, as described in RFC 4193

This package is a dependency for packaging LXD (ITP #768073).

This package will be team-maintained within the Debian Go Packaging
Team.


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

Bug#998108: firefox freezes shortly after start

2021-11-06 Thread Marco d'Itri

On Nov 06, dirdi  wrote:

> As a first step it would be good to have a method - e.g. a crafted 
> HTML page - to crash firefox instantly and reproducible. This would 
> enable us to bisect the changes between 93.0-1 and 93.0-1+b1.
I do not think that this would be possible because after restarting 
Firefox and opening again the link which made it freeze the first time
then it works again.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#998664: Acknowledgement (libntl43: undefined reference to `NTL::sub(NTL::ZZ&, NTL::ZZ const&, long))

2021-11-06 Thread David George Henderson III

This calling/type signature worked with buster that had libntl version 
10.5.0. I'm faced with several workaround choices:


    a) custom install libntl 10.5.0 in /usr/local/lib and change the 
compiler and linker commands to search this directory first


    b) revert to buster which implements 10.5.0

    c) recode source to not use this calling signature

    d) run bullseye with libntl35 package installed; have not tried 
this since choice 1) is so much easier for me



On 11/5/21 4:03 PM, Debian Bug Tracking System wrote:

Thank you for filing a new Bug report with Debian.

You can follow progress on this Bug here: 998664: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998664.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

As you requested using X-Debbugs-CC, your message was also forwarded to
   d...@its.caltech.edu
(after having been given a Bug report number, if it did not have one).

Your message has been sent to the package maintainer(s):
  Debian Science Maintainers 


If you wish to submit further information on this problem, please
send it to 998...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.

Bug#993174: RFS: dtkcore/5.5.17.1-1~exp1 -- Deepin Tool Kit Core library (utilities)


Control: tags -1 - moreinfo

dtkcommon is in unstable now.

Bug#998676: RM: chromium/93.0.4577.82-1

2021-11-06 Thread Simon McVittie

On Sat, 06 Nov 2021 at 08:03:49 +0100, Salvatore Bonaccorso wrote:
> Within the security team we are considering to announce the end of
> security support for chromium for buster and bullseye. People can e.g.
> transition to using Chromium from Flathub.

Note that the version of Chromium on Flathub requires:

* Flatpak >= 1.8.2 (buster-backports or bullseye is suitable, buster is not)

* a kernel configured for unprivileged user namespaces (bullseye is
  suitable by default, buster is not, and I'm not sure about buster-backports)

* a non-setuid bubblewrap executable (bullseye is suitable,
  buster is not, buster-backports is currently not suitable but could
  be made suitable if the security team are OK with that)

The same is true for various Chrome-, Chromium-, CEF- and Electron-based
Flatpak apps.

For Flatpak, I think the only way we are likely to get a suitable version
in buster would be to copy version 1.10.x from buster-backports into buster.
This currently also requires a backport of libseccomp in order to avoid
becoming vulnerable to CVE-2021-41133 via a backported bullseye kernel,
although it would presumably be possible to do a targeted backport
of knowledge of the clone3() syscall into buster's libseccomp as a
stable-update.

For bubblewrap and unprivileged user namespaces, if necessary the
bubblewrap package could drop in a sysctl.d snippet to open up access
to unprivileged user namespaces while it is installed (as the version
in bullseye does, in order to provide a migration path from buster).
This is a tradeoff between kernel attack surface and ability to do
user-space sandboxing, as discussed on #898446.

I think that if we are going to encourage use of Flatpak apps for
things like browsers, we will probably have to be prepared to do more
major-version backporting of things in the Flatpak ecosystem (Flatpak,
bubblewrap, libostree, libseccomp, and maybe also xdg-desktop-portal
and xdg-desktop-portal-*) into oldstable, and maybe also stable. All
of these components are designed to have conservative dependencies
outside their "bubble" (for example they go to considerable lengths to
be compatible with old GLib and libsoup), so it is possible to backport
them surprisingly far, and for example Flatpak upstream[1] are still
maintaining a PPA for Ubuntu 16.04 with the latest 1.12.x stable releases;
but if major applications require newer functionality, we can't magic
that into existence in older Flatpak and xdg-desktop-portal branches.

I'm doing my best to keep all this working and secure across multiple
Debian suites, but there's a limit to what I can do, particularly while
constrained to make minimal changes.

smcv

[1] in practice this is also me, with some help from Alexander Larsson

Bug#998108: firefox: still broken

2021-11-06 Thread Leonardo Canducci

Package: firefox
Version: 94.0-1
Followup-For: Bug #998108

Problem is still here after dist-upgrade on sid. Firefox hangs and becomes
unresponsive. Had to downgrade to verison 93.0-1

Bug#998629: pipewire: No sound devices in Pulseaudio after recent pipewire update in bookworm

2021-11-06 Thread Cesare Leonardi

Package: pipewire
Version: 0.3.39-3
Followup-For: Bug #998629
X-Debbugs-Cc: celeo...@gmail.com

Same problem for me.
After upgrading from pipewire 0.3.38-2 to 0.3.39-3, audio is not working
anymore.

Thomas Hager wrote:
> Anyway, after downgrading pipewire et al to 0.3.38-2 and rebooting,
> sound worked perfectly again on both devices, so I very much assume the
> recent update of pipewire caused the issues.

I've found that "pipewire-media-session" was reintroduced in sid and
installing this instead of "wireplumber", resolves the problem for me.
While waiting that it enters testing, the ones that is trying to get
its audio working again, could find the following steps simpler than
downgrading pulseaudio and its dependencies.

- Leave pipewire at the current testing version (0.3.39-3).
- Uninstall "wireplumber".
- Download pipewire-media-session 0.4.1-1 from sid:
  https://packages.debian.org/sid/pipewire-media-session
- For amd64:
  dpkg -i pipewire-media-session_0.4.1-1_amd64.deb
- Reboot.

Cesare.

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

Kernel: Linux 5.14.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pipewire depends on:
ii  init-system-helpers  1.60
ii  libpipewire-0.3-modules  0.3.39-3
ii  pipewire-bin 0.3.39-3

pipewire recommends no packages.

pipewire suggests no packages.

-- no debconf information

Bug#936535: flup: Python2 removal in sid/bullseye

2021-11-06 Thread tony mancill

On Fri, Jan 10, 2020 at 07:28:01PM -0300, Emmanuel Arias wrote:
> Hi,
> 
> The last upstream release version was on 2009 [1]. Seems to be not longer
> supported.
> 
> And there is not python3 version.
> 
> I believe that should be use the forks mentioned on:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873492
> 
> [1] https://www.saddi.com/software/flup/dist/ChangeLog

Hello Arias Emmanuel,

As noted in the bug report for
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873492, I intend to
request removal of this package from unstable on November 14th if the
Debian Python Team (or some other maintainer) doesn't decide to take the
package and update it.

Cheers,
tony

signature.asc
Description: PGP signature

Bug#873492: python-flup: Please package a Python 3 version

2021-11-06 Thread tony mancill

On Mon, Aug 23, 2021 at 08:28:00PM +, Martin wrote:
> On 2021-08-23 18:59, tony mancill wrote:
> > I haven't heard from John and don't use flup myself.  If you think the
> > Debian Python Modules Team would still like to take over the package, I
> > am happy to assist with that.
> >
> > Otherwise, I propose that we remove it from the archive.  The last
> > update for the flup6 was in July 2015 and the bitbucket.org link for the
> > project homepage is now defunct.
> 
> My own (potential) use case for the package disappeared.
> If nobody else needs the package now, I support removal.

I am looping in the Debian Python Team on the cc: to ask if there is any
interest in team maintenance of this package.  Otherwise I will file the
RM bug one week from now, on November 14th.

(Also see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936535)


signature.asc
Description: PGP signature

Bug#997798: ITP: dedalus -- Dedalus is a framework for solving PDEs useful for astrophysical and geophysical fluid dynamics

2021-11-06 Thread Mac Lee


I haven't gotten a sponsor yet. Could you be my sponsor?

Mac

On 10/25/21 5:29 PM, Thaddeus H. Black wrote:

On Mon, Oct 25, 2021 at 03:20:07PM -0700, Mac Lee wrote:

No I don't have a sponsor yet.

All right.  Since I

   * seldom program in Python,
   * unlike many Debian Developers, do not code for a living, and
   * attend to Debian development admittedly inconsistently,

I might make a suboptimal sponsor; but if no more suitable sponsor
appears then I might be available, to the extent to which a suboptimal
sponsor is better than none.  At least I know a little about spectral
methods, for what that's worth; and I've been a Debian Developer, though
an obscure one, since 2005.

If you like, wait a week or so for a more suitable sponsor and then, if
none appears, at your discretion, let me know how I can help.

Meanwhile, one hadn't expected to encounter a high-performance,
serious-pedigree, heavy-duty MPI numerical code in Python, but rather
in C++ or the like, so this could be interesting.

Bug#940519: curl: Enable support for http3 protocol

2021-11-06 Thread mooff


Hearing that HTTP/3 is ratified now. This would be nice to have :-)

Bug#998108: Acknowledgement (firefox freezes shortly after start)

2021-11-06 Thread Adon Shapiro

I guess I just got lucky then. I can't think of anything that I've changed. For
the record, I still have not re-experienced this problem.

Adon

On Sat, Nov 06, 2021 at 03:43:09AM +0100, Christoph Anton Mitterer wrote:
> > I was also experiencing this problem and was monitoring this bug
> > report for potential solutions, but the problem seems to have
> > recently disappeared. 
> 
> I cannot confirm this.

Bug#998691: taskwarrior: loses tasks added when "task edit" was running

2021-11-06 Thread Jakub Wilk


Package: taskwarrior
Version: 2.6.1+dfsg-1

I was "task edit"ing a task, but I got distracted, "task add"ed another 
task, went back to the editor, saved and exited. Taskwarrior modified 
the task I was editing, as expected, but it also lost the other task 
I added. :-(


Here's how to reproduce it:

   $ task add foo
   Created task 1.

   $ EDITOR="sleep 1000; sed -i -e s/foo/FOO/" task edit foo &
   [1] 681
   Launching 'sleep 1000; sed -i -e s/foo/FOO/ "task.efd5dc74.task"' now...

   $ task add bar
   Created task 2.

   $ task

   ID Age   Description Urg
1 12s   foo0
2  1s   bar0
 
   2 tasks


   $ pkill sleep && fg
   Terminated
   EDITOR="sleep 1000; sed -i -e s/foo/FOO/" task edit foo
   Editing complete.
   Edits were detected.
   Description modified.
   
   $ task
   
   ID Age   Description Urg

1 19s   FOO0
   
   1 task

   Recently upgraded to 2.6.0. Please run 'task news' to read higlights about 
the new release.

Note that the "bar" task has disappeared.


-- System Information:
Architecture: i386

Versions of packages taskwarrior depends on:
ii  libc62.32-4
ii  libgcc-s111.2.0-10
ii  libgnutls30  3.7.2-2
ii  libstdc++6   11.2.0-10
ii  libuuid1 2.37.2-4

--
Jakub Wilk

Bug#998689: general: Screen with wrong resolution at boot and marked as disconnected after suspend

2021-11-06 Thread Isabelle Stévant

Package: general
Severity: important
X-Debbugs-Cc: zazo...@gmail.com

Dear Maintainer,

I have a Zotac ZBOX CI547 nano with an intel core i5-7200U and an intel HD
Graphics 620 card on which I installed Debian 11 and the linux-firmware package
(fresh install, kernel 5.10.0-9). It is connected to a monitor supporting
1920*1080 via HDMI.

On boot, the grub resolution is fine, then while booting, on 90% of the case,
the screen resolution is set at 1280*800 and once on Gnome I cannot change to a
higher resolution, even with xrandr:

zbox@black-box:~$ xrandr --verbose
Screen 0: minimum 16 x 16, current 1280 x 800, maximum 32767 x 32767
XWAYLAND0 connected primary 1280x800+0+0 (0x22) normal (normal left inverted
right x axis y axis) 510mm x 280mm
Identifier: 0x21
Timestamp:  26284
Subpixel:   unknown
Gamma:  1.0:1.0:1.0
Brightness: 0.0
Clones:
CRTC:   0
CRTCs:  0
Transform:  1.00 0.00 0.00
0.00 1.00 0.00
0.00 0.00 1.00
   filter:
non-desktop: 0
supported: 0, 1
  1280x800 (0x22) 83.500MHz -HSync +VSync *current +preferred
h: width  1280 start 1352 end 1480 total 1680 skew0 clock  49.70KHz
v: height  800 start  803 end  809 total  831   clock  59.81Hz



zbox@black-box:~$ cvt -v 1920 1080
# 1920x1080 59.96 Hz (CVT 2.07M9) hsync: 67.16 kHz; pclk: 173.00 MHz
Modeline "1920x1080_60.00"  173.00  1920 2048 2248 2576  1080 1083 1088 1120
-hsync +vsync
zbox@black-box:~$ xrandr --newmode "1920x1080_60.00"  173.00  1920 2048 2248
2576  1080 1083 1088 1120 -hsync +vsync
zbox@black-box:~$ xrandr --addmode XWAYLAND0 1920x1080_60.00
zbox@black-box:~$ xrandr --output XWAYLAND0 --mode 1920x1080_60.00
xrandr: Configure crtc 0 failed


Here is the full dmesg when the computer boot with the right resolution
(approximately 10% off the time):
http://pastebin.fr/97303

And here the dmesg when the resolution is wrong:
http://pastebin.fr/97302

Here are the relevant errors I could find when the resolution is wrong by
comparing the two files (line 860 of the file):

[3.918717] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful


And here is the full dmesg with the drm.debug=0x1e log_buf_les=10M boot options
when the resolution is wrong:
http://pastebin.fr/97304

Here are the relevant lines regarding the error:

[3.883899] i915 :00:02.0: [drm:intel_dp_start_link_train [i915]] Same
voltage tried 5 times
[3.883953] i915 :00:02.0: [drm:intel_dp_start_link_train [i915]]
[CONNECTOR:95:DP-1] Link Training failed at link rate = 162000, lane count = 1
[3.883955] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful



The second problem I have is that after suspend or hibernate, the display does
not come back but the system is fine (I can log on the machine by ssh). The
monitors says it does not receive any signal, and when I check with xrandr the
display is labeled as disconnected. This happens independently of the
resolution. I catch the following dmesg typing blindly on TTY mode.

Here is the full dmesg after suspend and wake, when the boot resolution is
right:
http://pastebin.fr/97306

And here is the full dmesg after suspend and wake, when the boot resolution is
wrong:
http://pastebin.fr/97305

And here is the dmesg with the drm.debug=0x1e log_buf_les=10M boot options when
the resolution is wrong:
http://pastebin.fr/97307

What I could see is this error appearing after suspend when the resolution is
right:
[code]
[  151.138095] i915 :00:02.0: [drm] *ERROR* failed to enable link training
[/code]

And this when the resolution is wrong:
[code]
[  854.422386] i915 :00:02.0: [drm] *ERROR* failed to enable link training
[  854.422390] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
[/code]

I tried to install Debian 10 to check is the problem existed before and I have
exactly the same problems, intermittent wrong resolution and no display after
suspend. I guess the two problems are related and something goes wrong with the
intel firmware.

Bug#998688: widelands: Please consider updating to V1.0 (released 2021-06-15)

2021-11-06 Thread waxhead

Package: widelands
Version: 1:21-1+b2
Severity: wishlist
X-Debbugs-Cc: waxh...@dirtcellar.net

Dear Maintainer,

Please update to V1.0 which was released 2021-06-15 and contains numerous 
bugfixes and improvements.
Thanks.

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

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

Versions of packages widelands depends on:
ii  libboost-regex1.74.0 [libboost-regex1.74.0-icu67]  1.74.0-9
ii  libc6  2.32-4
ii  libgcc-s1  11.2.0-10
ii  libgl1 1.3.4-2+b1
ii  libglew2.2 2.2.0-4
ii  libicu67   67.1-7
ii  libminizip11.1-8+b1
ii  libpng16-161.6.37-3
ii  libsdl2-2.0-0  2.0.16+dfsg1-5
ii  libsdl2-image-2.0-02.0.5+dfsg1-3
ii  libsdl2-mixer-2.0-02.0.4+dfsg1-4
ii  libsdl2-ttf-2.0-0  2.0.15+dfsg1-2
ii  libstdc++6 11.2.0-10
ii  widelands-data 1:21-1

widelands recommends no packages.

widelands suggests no packages.

-- no debconf information

Bug#998687: lld: --no-allow-shlib-undefined: Doesn't check recursively

2021-11-06 Thread Sylvestre Ledru

Hello

I think you should report this issue upstream directly.

It doesn't seem to be a packaging bug.

Thanks

Sylvestre


Le 06/11/2021 à 14:00, Alejandro Colomar a écrit :
> Package: lld
> Version: 1:13.0-53~exp1
> Severity: normal
> Tags: upstream
> X-Debbugs-Cc: alx.manpa...@gmail.com, Michael Kerrisk (man-pages) 
> , Diego Elio Pettenò , 
> 997...@bugs.debian.org
>
> Dear Maintainer,
>
> A week ago I detected a bug in ld.gold, where it differs from ld.bfd:
> .
>
> In the meantime, I've known about ld.lld, and wondered its behavior
> regarding --no-allow-shlib-undefined.  After some experiment, it's
> the same buggy behavior that ld.gold has, and differs from ld.bfd.
>
> I would expect --no-allow-shlib-undefined to search recursively through
> all of my dependencies and check if any of them has undefined symbols,
> and report an error if so.  ld.bfd has that behavior.
>
> Instead, ld.lld (and ld.gold) only check that my direct dependencies
> have their symbols resolved, but they do not check the dependencies
> of my dependencies.
>
> That creates the possibility that an unmet dependency will cause a run-time
> error, as I show in the example below.
>
> Commands to reproduce the bug:
>
> $ ll
> total 20
> -rw-r--r-- 1 user user 29 Oct 28 11:47 bar.c
> -rw-r--r-- 1 user user 60 Oct 28 13:47 foobar.c
> -rw-r--r-- 1 user user 83 Oct 28 11:46 foo.c
> -rw-r--r-- 1 user user 52 Oct 28 13:47 foovar.c
> -rw-r--r-- 1 user user 56 Oct 28 13:31 main.c
> $ 
> $ cat bar.c
>   int bar(void)
>   {
>   return 1;
>   }
> $ cat foo.c
>   int bar(void);
>
>   int foo(void)
>   {
>   return 1;
>   }
>
>   int foo_bar(void)
>   {
>   return bar();
>   }
> $ cat foobar.c
>   int foo_bar(void);
>
>   int foobar(void)
>   {
>   return foo_bar();
>   }
> $ cat foovar.c
>   int foo(void);
>
>   int foobar(void)
>   {
>   return foo();
>   }
> $ cat main.c
>   int foobar(void);
>
>   int main(void)
>   {
>   return foobar();
>   }
> $ 
> $ cc -c -fpic -Wall -Wextra -Werror main.c foo.c bar.c foobar.c foovar.c
> $ 
> $ cc -shared -Wl,--no-undefined -Wl,--no-allow-shlib-undefined 
> -Wl,--as-needed -Wl,--no-copy-dt-needed-entries -o libbar.so bar.o 
> -fuse-ld=bfd
> $ cc -shared -Wl,--no-undefined -Wl,--no-allow-shlib-undefined 
> -Wl,--as-needed -Wl,--no-copy-dt-needed-entries -o libbar.so bar.o 
> -fuse-ld=gold
> $ 
> $ cc -shared -Wl,--no-undefined -Wl,--no-allow-shlib-undefined 
> -Wl,--as-needed -Wl,--no-copy-dt-needed-entries -o libfoo.so foo.o 
> -fuse-ld=bfd
> /usr/bin/ld.bfd: foo.o: in function `foo_bar':
> foo.c:(.text+0x10): undefined reference to `bar'
> collect2: error: ld returned 1 exit status
> $ cc -shared -Wl,--no-undefined -Wl,--no-allow-shlib-undefined 
> -Wl,--as-needed -Wl,--no-copy-dt-needed-entries -o libfoo.so foo.o 
> -fuse-ld=gold
> foo.o:foo.c:function foo_bar: error: undefined reference to 'bar'
> collect2: error: ld returned 1 exit status
> $ 
> $ cc -shared -Wl,--no-allow-shlib-undefined -Wl,--as-needed 
> -Wl,--no-copy-dt-needed-entries -o libfoo.so foo.o -fuse-ld=bfd
> $ cc -shared -Wl,--no-allow-shlib-undefined -Wl,--as-needed 
> -Wl,--no-copy-dt-needed-entries -o libfoo.so foo.o -fuse-ld=gold
> $ 
> $ cc -shared -Wl,--no-undefined -Wl,--no-allow-shlib-undefined 
> -Wl,--as-needed -Wl,--no-copy-dt-needed-entries -o libfoobar.so foobar.o -L. 
> -lfoo -fuse-ld=bfd
> /usr/bin/ld.bfd: ./libfoo.so: undefined reference to `bar'
> collect2: error: ld returned 1 exit status
> $ cc -shared -Wl,--no-undefined -Wl,--no-allow-shlib-undefined 
> -Wl,--as-needed -Wl,--no-copy-dt-needed-entries -o libfoobar.so foobar.o -L. 
> -lfoo -fuse-ld=gold
> ./libfoo.so: error: undefined reference to 'bar'
> collect2: error: ld returned 1 exit status
> $ 
> $ cc -shared -Wl,--no-undefined -Wl,--as-needed 
> -Wl,--no-copy-dt-needed-entries -o libfoobar.so foobar.o -L. -lfoo 
> -fuse-ld=bfd
> $ cc -shared -Wl,--no-undefined -Wl,--as-needed 
> -Wl,--no-copy-dt-needed-entries -o libfoobar.so foobar.o -L. -lfoo 
> -fuse-ld=gold
> $ 
> $ cc -shared -Wl,--no-undefined -Wl,--no-allow-shlib-undefined 
> -Wl,--as-needed -Wl,--no-copy-dt-needed-entries -o libfoovar.so foovar.o -L. 
> -lfoo -fuse-ld=bfd
> /usr/bin/ld.bfd: ./libfoo.so: undefined reference to `bar'
> collect2: error: ld returned 1 exit status
> $ cc -shared -Wl,--no-undefined -Wl,--no-allow-shlib-undefined 
> -Wl,--as-needed -Wl,--no-copy-dt-needed-entries -o libfoovar.so foovar.o -L. 
> -lfoo -fuse-ld=gold
> ./libfoo.so: error: undefined reference to 'bar'
> collect2: error: ld returned 1 exit status
> $ 
> $ cc -shared -Wl,--no-undefined -Wl,--as-needed 
> -Wl,--no-copy-dt-needed-entries -o libfoovar.so foovar.o -L. -lfoo 
> -fuse-ld=bfd
> $ cc -shared -Wl,--no-undefined -Wl,--as-needed 
> -Wl,--no-copy-dt-needed-entries -o libfoovar.so foovar.o -L.

Bug#261028: Progress on "sql format syntax doesn't differentiate NULL values" ?


On Sat, 6 Nov 2021 14:48:15 +0100 Bastian Germann  wrote:

There is an equivalent patch on the current issue tracker.
It will probably not get any attention by upstream, so if you want it to be 
integrated please push it.


This went to the wrong bug.

Bug#261028: Progress on "sql format syntax doesn't differentiate NULL values" ?


Control: forwarded -1 https://github.com/cyrusimap/cyrus-sasl/issues/296

Bug#996419: gcc-11: Fails to compile the linux kernel on ARM

2021-11-06 Thread Salvatore Bonaccorso

For cross-reference:

On Mon, Oct 18, 2021 at 11:52:31AM +0200, Arnd Bergmann wrote:
[...]
> I'll send the kernel workaround soon, and that should make it into all
> stable kernels.
> 
> The compilers I build for kernel.org do not set a default -march value
> and end up with the default that gcc picks, which apparently is
> a softfloat -mcpu=arm10tdmi.

The mentioned kernel workaround/patch would be
https://lore.kernel.org/linux-arm-kernel/20211018140735.3714254-1-a...@kernel.org/
(not yet applied in mainline and other stable series).

Regards,
Salvatore

Bug#261028: Progress on "sql format syntax doesn't differentiate NULL values" ?