from:"c"

Bug#1080037: linux: ASUS Vivobook Go E1404GAB_E1404GA keyboard does not work

2024-08-29 Thread Fernando C. Estrada

Source: src:linux
Severity: wishlist
Tags: upstream

Dear Maintainer,

I am raising this report to help a user (Livi Toro) from the Debian
Spanish user support list [0].

Keyboard does not work on an Asus VivoBook Go 14 E1404GAB laptop [1], it
does not work in Debian stable (linux 6.1.106), and it doesn't work
either with the latest live-image (linux 6.10.6).

This issue was reported to upstream in bug 219212 [2] but it is also
submitted here to let you know (and other affected users) about it.

[0] https://lists.debian.org/debian-user-spanish/2024/08/msg00039.html
[1] https://linux-hardware.org/?probe=5a3dac80c0
[2] https://bugzilla.kernel.org/show_bug.cgi?id=219212

Thanks & have a nice day!

Bug#1079488: nm.debian.org: api status lists only people with legacy Debian SSO login

2024-08-23 Thread Ananthu C V

Package: nm.debian.org
Severity: important

Hi,

It seems that nm.d.o/api/status does not actually list everyone in NM,
but instead only a portion of them, presumably only those with a (legacy) Debian
SSO login. 

For example, the api currently lists ~172 DM (with or without guest accounts).
142 of the 172 have users.alioth.debian.org as the domain in mail id, 28 has
example.org and the remaining two has debian.org. There is no DM present in
the list with any other mail providers, which in all probability includes a
huge amount of people including myself.

This makes the currently available status incorrect and very unreliable for
any sort of usage. Please update the api to display the correct status.

Best,
Ananthu

Bug#1078593: Acknowledgement (appstream: asv-summary-too-long Warning needs more details)

2024-08-13 Thread c . buhtz


Please let me give additional information.

Using "appstreamcli validate foobar.xml" on my local machine do not give 
me a warning about the length of that field. That confuses me much more. 
Which check command is used on the Debian Build Servers to generate that 
warning message?


I opened a ticket at the AppStream project about their specificaton of 
that field. Currently their docu do not tell about a length limit.

Bug#1078475: ITP: python-tzdata -- provider of IANA time zone data

2024-08-11 Thread Ananthu C V

Package: wnpp
Severity: wishlist
Owner: Ananthu C V 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: python-tzdata
  Version : 2024.1
  Upstream Contact: Python Software Foundation 
* URL : https://github.com/python/tzdata
* License : Apache-2.0
  Programming Lang: Python
  Description : provider of IANA time zone data

This is a Python package containing zic-compiled binaries for the IANA time
zone database. It is intended to be a fallback for systems that do not have
system time zone data installed (or don't have it installed in a standard
location), as a part of PEP 615.

It is a dependency needed by pendulum 3.0.

Bug#1078333: [linux-board-support-package-dragonboard845c]

2024-08-09 Thread C

Package: linux-board-support-package-dragonboard845c
Version:
Severity: 
Tags: 
X-Debbugs-CC: 
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

* What led up to the situation?
* What exactly did you do (or not do) that was effective (orineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?

*** End of the template - remove these lines ***

Bug#1077165: ITP: python-mashumaro -- fast and well tested serialization library

2024-07-26 Thread Ananthu C V

Package: wnpp
Severity: wishlist
Owner: Ananthu C V 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: python-mashumaro
  Version : 3.13.1
  Upstream Contact: Alexander Tikhonov 
* URL : https://github.com/Fatal1ty/mashumaro
* License : Apache-2.0
  Programming Lang: python
  Description: fast and well tested serialization library

In Python, you often need to dump and load objects based on the schema you
have. It can be a dataclass model, a list of third-party generic classes
or whatever. Mashumaro not only lets you save and load things in different
ways, but it also does it super quick.

Dependency of python-tailscale python package.

Bug#1072474: backintime-common: "sshfs" should be "dep" instead of "sug"

2024-07-22 Thread c . buhtz

It gives an error message dialog: "sshfs not found. Please install it 
(e.g. via "apt install sshfs")"


I don't like that behavior. The GUI suggest that this functionality does 
exist, the user invest time in configuring it and near the end that 
error comes up. From a view point of usability it is not friendly to 
users.

But you are the maintainer. It is up to you of course. ;)

Bug#1072474: backintime-common: "sshfs" should be "dep" instead of "sug"

2024-07-22 Thread c . buhtz


Am 22.07.2024 12:23 schrieb Fabio Fantoni:

I think sshfs will be better in recommends instead depends as not all
use remote backup on ssh. Have it as depends also make unable to
uninstall it.

Is this okay or is there some other reason why it's better to be in 
depends?


SSH profiles is not an optional feature. It is in-build. BIT doesn't 
check if sshfs is installed or not. It will cause several unexpected 
errors and maybe exceptions. This increase maintenance burden and 
confuse users. And we also don't want to implement checks like this with 
extra code.
For example the GUI should reflect the fact that SSH is not installed, 
e.g. via disable the SSH entries in the drop-down menu. But we don't 
want to do that.


IMHO sshfs is not that exotic.

Bug#1076495: [Pkg-samba-maint] Bug#1076495: samba-common-bin: net usershare guest_ok paramter is parsed as a comment

2024-07-17 Thread c


Will report upstream then.

The man page explicitly states that the comment and acl parameters are 
optional, which implies it is sufficient to just specify guest_ok=y.  
But if only this parameter is passed, it is interpreted as being the 
comment parameter.  In other words, they are not optional.


Extract from net(8):

        The optional "comment" parameter is the comment that will 
appear on the share when browsed to by a client.


   The optional "acl" field specifies which users have read and 
write access to the entire share. 


   The default if no "acl" is given is "Everyone:R", which means 
any authenticated user has read-only access.


   The optional "guest_ok" has the same effect as the parameter of 
the same name in /etc/samba/smb.conf, in that it allows guest access to 
this user defined share. This parameter
   is only allowed if the global parameter "usershare allow guests" 
has been set to true in the /etc/samba/smb.conf.


I subsequently learned you can specify empty comment/acl parameters:

$ net usershare add sharename /path/to/dir "" "" guest_ok=y

But specifying empty parameters in quotes is not the same as them being 
optional.



On 17/7/24 18:47, Michael Tokarev wrote:

Control: severity -1 minor

17.07.2024 11:04, debian-report...@mx.brindabella.org wrote:

Package: samba-common-bin
Version: 2:4.17.12+dfsg-0+deb12u1
Severity: normal

Dear Maintainer,

On a fresh install of Debian, user enters the following command:

user@debian:~# net usershare add testing /home/user/myusershare/ 
guest_ok=y


The resulting usershare generated by Samba is as follows:

root@debian:~# cat /var/lib/samba/usershares/testing
#VERSION 2
path=/home/user/myusershare/
comment=guest_ok=y
usershare_acl=S-1-1-0:R
guest_ok=n
sharename=testing

Note that the 'guest_ok=y' parameter has been parsed as a comment not 
as specifying guest access.  This appears inconsistent with the man 
page for net(8), which suggests [comment] and [acl
] are *optional* parameters. The usershare is created with what are 
presumably default values for ACL and guest_ok.


USERSHARE ADD sharename path [comment] [acl] [guest_ok=[y|n]]

The only way to ensure the guest_ok=y parameter is correctly added to 
the usershare definition is to include both a comment and an ACL - eg:


net usershare add testing /home/user/myusershare mycomment 
S-1-1-0:f guest_ok=y


This is contrary to the man page which suggests [comment] and [acl] 
are optional.  This requires user to know what to specify for ACL, 
which would 


The net(8) manpage says:

 The usershare commands are:
 net usershare add sharename path [comment [acl] 
[guest_ok=[y|n]]] - to add or change a user defined share.

 net usershare delete sharename - to delete a user defined share.
 net usershare info [--long] [wildcard sharename] - to print 
info about a user defined share.
 net usershare list [--long] [wildcard sharename] - to list 
user defined shares.


   USERSHARE ADD sharename path [comment] [acl] [guest_ok=[y|n]]
   Add or replace a new user defined share, with name "sharename".
   

Note the list of all usershare commands just 4 lines above the line you
quoted.


Either way, please address this upstream.

Thanks,

/mjt

Bug#1076167: RFP: waveterm -- AI-native terminal built for seamless workflows

2024-07-11 Thread Fernando C. Estrada

Package: wnpp
Severity: wishlist

* Package name: waveterm
  Version : 0.7.6
  Upstream Contact: supp...@waveterm.dev
* URL : https://www.waveterm.dev/
* License : Apache-2.0
  Programming Lang: Go, TypeScript
  Description : AI-native terminal built for seamless workflows

Wave isn't just another terminal emulator; it's a rethink on how
terminals are built. Wave combines command line with the power of
the open web to help veteran CLI users and new developers alike.

Thanks!

Bug#1076165: RFP: zed -- High-performance multiplayer code editor

2024-07-11 Thread Fernando C. Estrada

Package: wnpp
Severity: wishlist

* Package name: zed
  Version : 0.143.6
  Upstream Contact: Zed Industries 
* URL : https://zed.dev/
* License : AGPL-3
  Programming Lang: Rust
  Description : High-performance multiplayer code editor

Zed is a modern open-source code editor, built from the ground
up in Rust with a GPU-accelerated renderer, from the creators
of Atom and Tree-sitter.

https://zed.dev/blog/zed-on-linux

P.S. Please validate if the name 'zed' will be valid for Debian.

https://tracker.debian.org/pkg/zed

Thanks!

Bug#1051785: workaround

2024-06-22 Thread C

> What dconf workaround would that be? I don't see one in the previous
messages to this bug.

Very sorry, I got confused: I read somewhere that creating a file in
/etc/dconf/[subdirectory I can't remember] would've solved this.
I can't find the place I read that anymore, and for some reason I believed
it was in this bug; however, I think it was exactly what the RedHat guide
you linked describes.

>  The intended way to change the settings of the Debian-gdm user is to
edit /etc/gdm3/greeter.dconf-defaults [...]

Understood, thank you; I'll keep this in mind.

> I personally think using smart cards as orthogonal to PAM authentication
> is likely to be more common than using them for PAM authentication [...]

Agreed; I also think there's more users tinkering with smart cards (or
installing smart card tooling as a dependency to some other software) than
there are users using them for authentication.

I don't know exactly what triggered this behaviour in GDM; I tried to
reproduce on a VM by installing opensc (which pulled in pcscd too) and
upgrading first to trixie and then sid, but nothing triggered it. It may be
another package, happy to test if you have suggestions.

> Or, perhaps enable-smartcard-authentication should be one of the fields
> that is included in our example /etc/gdm3/greeter.dconf-defaults ready
> for users to edit? The default could be either true or false, whichever
> seems more appropriate.

IMO this seems appropriate, and matches your intention of not touching
Marco's design; I would default to false and document this as a requirement
for using smart card authentication, but it may be considered a breaking
change (the current default is true, I believe) so I'm not sure how you
want to handle it.

On Fri, Jun 21, 2024 at 3:55 PM Simon McVittie  wrote:

> On Fri, 21 Jun 2024 at 12:55:34 +0200, C wrote:
> > Neither [...], nor setting the gsettings entry
> > on my user or as root, worked and I suspect it's because the value on the
> > Debian-gdm user takes precedence.
>
> Setting a gsettings entry for your user or for root is not expected to
> affect the behaviour of the gdm greeter, because the gdm greeter does not
> run as your user, or as root: it runs as Debian-gdm (or as gdm on Ubuntu).
> So that part is as working as designed: if you want to change the behaviour
> of the greeter, it is the Debian-gdm user's settings that must be changed,
> and no other user's personal settings are going to affect it.
>
> > Neither the dconf workaround suggested above, nor [...], worked
>
> What dconf workaround would that be? I don't see one in the previous
> messages to this bug.
>
> The intended way to change the settings of the Debian-gdm user is to edit
> /etc/gdm3/greeter.dconf-defaults. In this case I think the equivalent would
> be to locate the line "[org/gnome/login-screen]" and fill in
> "enable-smartcard-authentication=false" below it, so it looks
> something like this:
>
> ...
> [org/gnome/login-screen]
> enable-smartcard-authentication=false
> logo='/usr/share/images/vendor-logos/logo-text-version-64.png'
> ...
>
> And then restart gdm (the easiest/most reliable way is to reboot).
>
> However, if you have already used a workaround that edits the user's
> settings, like this one:
>
> > sudo -u Debian-gdm env -u XDG_RUNTIME_DIR -u DISPLAY DCONF_PROFILE=gdm
> > dbus-run-session gsettings set org.gnome.login-screen
> > enable-smartcard-authentication false
>
> then that is probably going to take a higher priority than whatever you
> write into /etc/gdm3/greeter.dconf-defaults.
>
> > For the record I didn't try the other suggestion in the bug (creating
> /etc/
> > pam.d/gdm-password and using update-alternatives to set that as the
> default for
> > gdm-smartcard), but maybe Debian should have this as an option for
> people that
> > run into this issue?
> > If that's a valid option then believe it would be a simple addition to
> have
> > that file (even called something else, like "gdm-no-smartcard",
> > "gdm-password-only", etc.) in place, even if it's not the default.
>
> Marco designed the smart card handling setup that is currently used in
> Debian, so I'm not going to make changes to it without understanding his
> design intentions.
>
> I personally think using smart cards as orthogonal to PAM authentication
> is likely to be more common than using them for PAM authentication, and
> if I understand correctly, using smart cards for authentication needs
> sysadmin configuration *anyway* to associate each smartcard with a user
> ID; so I would personally prefer it if the default was to use ordinary
> pass

Bug#1074002: ITP: python-graphene-directives -- schema directives implementation for graphene

2024-06-21 Thread Ananthu C V

Package: wnpp
Severity: wishlist
Owner: Ananthu C V 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: python-graphene-directives
  Version : 0.4.6
  Upstream Contact: Strollby 
* URL : https://github.com/strollby/graphene-directives
* License : Expat
  Programming Lang: python
  Description : schema directives implementation for graphene

Graphene directives provides the implementation of schema directives
needed for graphene.

This is a dependency for graphene-federation (#1073797).

Bug#1051785: workaround

2024-06-21 Thread C

I found myself here with the same issue (although it took a while to find
this bug): I have a YubiKey and suddenly at login my user would appear for
a split second and then be replaced by the blank username field.

After entering the username gdm3 would show "SSSD PAM module is not
installed. Smart card authentication is not supported, falling back to
default mechanism"
This started for me a few weeks ago, right around the time I installed
opensc for some smart card work I needed to do.

I managed to "fix" the behaviour (it's more of a workaround IMO) by running
this command

sudo -u Debian-gdm env -u XDG_RUNTIME_DIR -u DISPLAY DCONF_PROFILE=gdm
dbus-run-session gsettings set org.gnome.login-screen
enable-smartcard-authentication false

that Marco suggested on
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1933027/comments/17
(all I had to do was change the sudo username from gdm to Debian-gdm).
Neither the dconf workaround suggested above, nor setting the gsettings
entry on my user or as root, worked and I suspect it's because the value on
the Debian-gdm user takes precedence.

For the record I didn't try the other suggestion in the bug (creating
/etc/pam.d/gdm-password and using update-alternatives to set that as the
default for gdm-smartcard), but maybe Debian should have this as an option
for people that run into this issue?
If that's a valid option then believe it would be a simple addition to have
that file (even called something else, like "gdm-no-smartcard",
"gdm-password-only", etc.) in place, even if it's not the default.

Also of note, my installed alternative was "gdm-smartcard-sssd-exclusive"
and it was still falling back to password.

Hope this helps!

Bug#1073803: reopening zellij ITP

2024-06-18 Thread Ananthu C V

Control: reopen 1073803 =

Hello,

The zellij ITP I had opened has been closed not long after by bartm, with
no explanation whatsoever. I am reopening the ITP as such, so please provide
valid reasoning as to why this has been/have to be closed.

Best,
Ananthu

Bug#1073804: ITP: rust-leb128 -- read and write DWARF's little endian base 128 variable length integer encoding

2024-06-18 Thread Ananthu C V

Package: wnpp
Severity: wishlist
Owner: Ananthu C V 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-r...@lists.debian.org

* Package name: rust-leb128
  Version : 0.2.5
  Upstream Contact: Nick Fitzgerald 
* URL : https://github.com/gimli-rs/leb128
* License : Apache-2.0/MIT
  Programming Lang: rust
  Description : read and write DWARF's little endian base 128 variable 
length integer encoding

 Read and write DWARF's "Little Endian Base 128" (LEB128) variable length 
integer encoding.

 The implementation is a direct translation of the pseudocode in the DWARF 4 
standard's appendix C.

One of the many dependencies in the zellij (#1073803) dependencyu tree.

Bug#1073803: ITP: zellij -- terminal workspace with batteries included

2024-06-18 Thread Ananthu C V

Package: wnpp
Severity: wishlist
Owner: Ananthu C V 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-r...@lists.debian.org

* Package name: zellij
  Version : 0.40.1
  Upstream Contact: Aram Drevekenin 
* URL : https://github.com/zellij-org/zellij
* License : Expat
  Programming Lang: rust
  Description : terminal workspace with batteries included

 Zellij is a workspace aimed at developers, ops-oriented people
 and anyone who loves the terminal. Similar programs are sometimes
 called "Terminal Multiplexers".

 Zellij is designed around the philosophy that one must not sacrifice
 simplicity for power, taking pride in its great experience out of the
 box as well as the advanced features it places at its users' fingertips.

Packaging zellij requires packaging over a hundred crates in its dependency
tree and this number could only grow when it comes to packaging each of the
crates. I am not a DD, which means I need quite active sponsorship to make
packaging this possible. I have been on this effort for sometime now and
have ~50 crates packaged, of which about 20+ are uploaded and the rest are
awaiting upload with RFS. I am a DM, and I could take care of the packages
once they are uploaded to NEW and accepted. And I intend to maintain this
under the rust team umbrella.

Bug#1073797: ITP: python-graphene-federation -- federation implementation for graphene

2024-06-18 Thread Ananthu C V

Package: wnpp
Severity: wishlist
Owner: Ananthu C V 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: python-graphene-federation
  Version : 3.2.0
  Upstream Contact: Igor Kasianov 
* URL : https://github.com/graphql-python/graphene-federation
* License : Expat
  Programming Lang: python
  Description : federation implementation for graphene

 Federation support for Graphene, following the Apollo
 federation specifications.

 This is a dependency needed for python-graphene-mongo v0.4.4 update.

Bug#1073241: gdebi-gtk desktop file has NotShowIn=KDE

2024-06-14 Thread Ethan C


Package: gdebi

Version: 0.9.5.7+nmu2

GDebi historically maintained two GUIs, gdebi-gtk and gdebi-kde. Using 
the NotShowIn and OnlyShowIn fields of the desktop files, gdebi-gtk was 
shown in all non-KDE desktops and gdebi-kde was shown only in KDE. In 
2017 
, 
gdebi-kde was removed because it depended on pykde4, but gdebi was not 
updated so that the desktop file shows on KDE. This leads to the 
unexpected behavior where GDebi is installed but KDE users cannot use 
GDebi to handle .deb files they might wish to install or launch GDebi 
from the main menu, as the desktop file is hidden. I suggest that the 
line "NotShowIn=KDE;" in the file /usr/share/applications/gdebi.desktop 
is removed, so that gdebi-kde users could use GDebi from KDE. Recent 
versions of KDE for several years have handled Gtk applications well, so 
there is no point in preventing KDE users from using GDebi.

Bug#1072723: libvirt0: qemu:///session not connected after login

2024-06-12 Thread Francesco C

When upgrading to libvirt 10.4-0 I can confirm that if /usr/sbin is in
the PATH , the command : " virsh -c qemu:///session connect" works ;
virt-manager can connect only after launching the virsh command.

Bug#1072723: libvirt0: qemu:///session not connected after login

2024-06-10 Thread Francesco C

I can confirm that downgrading libvirt and almost all related packages
to version 10.3.0-3 restores the usual behaviour.

Bug#1072842: rust-async-lock: please update to version 3.0+

2024-06-08 Thread Ananthu C V

Source: rust-async-lock
Version: 2.6.0-4
Severity: wishlist

Hi,

I am trying to package async-dup and it requires version 3.1 of async-lock.
I tried to build it with the current v2.8 but that seems to be failing. Since
async-lock in debian is lagging behind the upstream version a bit, perhaps
updating the package is the right solution for this. Several packages seems to
depend on async-lock, so this might be a transition needing a bit of work.
Can you try finding some time to work on this?

Best,
Ananthu

-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Bug#1072723: libvirt0: qemu:///session not connected after login

2024-06-07 Thread Francesco C

> After upgrade to 10.4.0 I have to start my "local session" using

> virsh -c qemu:///session connect

This does not work for me ; it works only if a prepend sudo ; root is
the only user that has access to qemu:///session  which is a paradox
because users like me are using qemu:///session (for trying) to avoid
unwanted privileged access.

virsh -c qemu:///session connect
error: cannot connect to hypervisor
error: cannot receive data : connection reset by peer

I obtain this message with virt-manager :

Unable to connect to libvirt qemu:///session.

Cannot receive data : Connection reset by peer

Libvirt URI is: qemu:///session

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/connection.py", line 923,
in _do_open
self._backend.open(cb, data)
  File "/usr/share/virt-manager/virtinst/connection.py", line 171, in open
conn = libvirt.openAuth(self._open_uri,
   
  File "/usr/lib/python3/dist-packages/libvirt.py", line 147, in openAuth
raise libvirtError('virConnectOpenAuth() failed')
libvirt.libvirtError: Cannot receive data : Connection reset by peer

The wiki of libvirt treats some  "cannot connect to hypervisor" common
causes, but there's no reference to connection reset by peer.

Bug#1072128: ITP: ruby-omniauth-shibboleth-redux -- OmniAuth Shibboleth strategies for OmniAuth 2.x

2024-05-28 Thread Ananthu C V

Package: wnpp
Severity: wishlist
Owner: Ananthu C V 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: ruby-omniauth-shibboleth-redux
  Version : 2.0.0
  Upstream Contact: Bobby McDonald 
* URL : https://github.com/omniauth/omniauth-shibboleth-redux
* License : Expat
  Programming Lang: ruby
  Description : OmniAuth Shibboleth strategies for OmniAuth 2.x

OmniAuth Shibboleth strategy is an OmniAuth strategy for authenticating
through Shibboleth (SAML).

This is a dependency needed by gitlab 16.11.3.

Bug#1072050: ruby-grpc: update grpc to version 1.59

2024-05-27 Thread Ananthu C V

Package: ruby-grpc
Version: 1.51.1-3+b1
Severity: wishlist

Dear Maintainer,

I have a requirement for the version 1.59 of ruby-grpc, which is for packaging 
gapic-common (#1072048)
which is a dependency (and a dependency of several other dependencies) needed 
by gitlab 16.11.3.
The current debian version of grpc, which is 1.51, is already lagging quite 
behind the upstream
version (currently 1.64, I think), so it warrants an update sooner or later. 
Would you consider
updating the package so that this blocker will be removed?

Best,
Ananthu


-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-21-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ruby-grpc depends on:
ii  libc62.36-9+deb12u7
ii  libgrpc291.51.1-3+b1
ii  libruby3.1   3.1.2-7+deb12u1
ii  ruby-google-protobuf 3.21.12-3
ii  ruby-googleapis-common-protos-types  1.4.0-1
ii  ruby-googleauth  0.13.0-3

ruby-grpc recommends no packages.

ruby-grpc suggests no packages.

-- no debconf information

Bug#1072048: ITP: ruby-gapic-common -- common code for GAPIC-generated API clients

2024-05-27 Thread Ananthu C V

Package: wnpp
Severity: wishlist
Owner: Ananthu C V 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: ruby-gapic-common
  Version : 0.21.1
  Upstream Contact: Google LLC 
* URL : https://github.com/googleapis/gapic-generator-ruby
* License : Apache-2.0
  Programming Lang: ruby
  Description : common code for GAPIC-generated API clients

Generated API Client common code (gapic-common) is a set of modules which aids
the development of APIs for clients and servers based on gRPC and Google API.

This is a dependency needed by gitlab 16.11.3 and is also needed for packaging
several other dependencies of the same.

Bug#1072045: ITP: ruby-googleapis-common-protos -- common gRPC and protocol buffer classes used in Google APIs

2024-05-27 Thread Ananthu C V

Package: wnpp
Severity: wishlist
Owner: Ananthu C V 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: ruby-googleapis-common-protos
  Version : 1.5.0
  Upstream Contact: Google APIs <"googleapis-packa...@google.com">
* URL : https://github.com/googleapis/common-protos-ruby
* License : Apache-2.0
  Programming Lang: ruby
  Description : common gRPC and protocol buffer classes used in Google APIs

This package contains common gRPC and protocol buffer classes used in Google
APIs.

It is a dependency needed by GitLab 16.11.3.

Bug#1071968: ITP: ruby-cssbundling-rails -- Bundle and process CSS in Rails via Node.js

2024-05-26 Thread Ananthu C V

Package: wnpp
Severity: wishlist
Owner: Ananthu C V 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: ruby-cssbundling-rails
  Version : 1.4.0
  Upstream Contact: David Heinemeier Hansson 
* URL : https://github.com/rails/cssbundling-rails
* License : Expat
  Programming Lang: ruby
  Description : Bundle and process CSS in Rails via Node.js

 This gem provides installers to get you going with the bundler of your choice
 in a new Rails application, and a convention to use app/assets/builds to hold
 your bundled output as artifacts that are not checked into source control (the
 installer adds this directory to .gitignore by default).

This package is a dependency of gitlab.

Bug#1037133:

2024-05-23 Thread c . buhtz


Hello,

I want to give an update of the situation because I migrated from Debian 
11 to 12 (old-stable to stable). Stable now has ownCloud client 2.11.0. 
The described bug is still in this version.


As upstream reported (https://github.com/owncloud/client/issues/10071) 
it might be fixed in 2.11.1.


I am just a user and don't know much about Debian Maintenance. From my 
perspective it is not "normal" bug. It is a problem that significantly 
restricts usability and functionality.


If it is not possible to fix this in current stable because of policies 
it would help much if there would be an stable-backports package with 
2.11.1 or later. I am aware that this is not an easy thing. I just want 
to mention.


Thanks in advance,
Christian Buhtz

Bug#985257: Location of example scripts?

2024-05-16 Thread c . buhtz


Hello,

I do have a side question regarding to a possible solution of this 
issue.
Back In Time (BIT) still have eight example callback scripts in a 
separate repo [1]. I plan to integrate them into the primary repo. But I 
ask myself where to install them when "./configure && make && sudo make 
install" is called?


BIT does look in "~/.config/backintime" for a file named 
"user-callback".


I would propose to install the 8 example scripts in this folder with a 
naming pattern that backintime does treat them as not active in the 
first place.


~./config/user-callback.example.default
~./config/user-callback.example.apt-backup
~./config/user-callback.example.sendmail
~./config/user-callback.example.notify
...

So this scripts would become a part of the "backintime-commen" package.

Is this acceptable for you as Debian Maintainers?

Kind
Christian Buhtz

[1] --

Bug#1068945: ITP: rust-names -- generator for random names suitable for containers, projects, applications etc.

2024-04-13 Thread Ananthu C V

Package: wnpp
Severity: wishlist
Owner: Ananthu C V 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: rust-names
  Version : 0.14.0
  Upstream Contact: Fletcher Nichol 
* URL : https://crates.io/crates/names
* License : MIT
  Programming Lang: Rust
  Description : generator for random names suitable for containers, 
projects, applications etc.
   A random name generator with names suitable for use in container instances, 
project names,
   application instances, etc.

This is a dependency for zellij-utils, in turn a dependency that will be needed 
to package zellij.

Bug#1068726: ITP: rust-csv2svg -- Take a csv as input and outputs svg

2024-04-09 Thread Ananthu C V

Package: wnpp
Severity: wishlist
Owner: Ananthu C V 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: rust-csv2svg
  Version : 0.2.1
  Upstream Contact: dystroy 
* URL : https://crates.io/crates/csv2svg
* License : MIT
  Programming Lang: Rust
  Description : Take a csv as input and outputs svg
   Build a SVG graph from a csv document.

This is a dependency needed by glassbench, which comes the zellij
dependency tree.

Bug#1055655: rebuild fails with node-typescript 4.9.5 in experimental

2024-04-07 Thread Ananthu C V

Control: close 1055655

Bug#1055655: rebuild fails with node-typescript 4.9.5 in experimental

2024-04-07 Thread Ananthu C V

Control: close 1055655 node-js-sdsl/4.1.4-3

Hi Paul, only now after rebuidling the package and
coming to close the bug after noticing the issue is fixed did I notice
your mail. Thanks for the fix.

Best,
Ananthu

Bug#983870: Picking up webdriver-manager packaging

2024-03-21 Thread Ananthu C V

Hi Joost,

It seems that you are no longer intending to work on this.
I, on the other hand, require webdriver manager for packaging 
lightnovel-crawler.
So if you don't mind, can I pick this up?

Best,
Ananthu

Bug#1067029: closed by Thomas Lange (closing)

2024-03-17 Thread c . buhtz


Dear Thomas,

thanks for your your reply.

My report was not about how to find donation info because I am looking 
for them. My intention was to improve Debian.


I still recommend to add "Donations" as a term to the landing page. 
Doing a text search (CTRL+F) on that page for "Donation" has 0 hits.


IMHO such an info should be obvious and not hidden behind a search 
engine or a "more" button. It is to important.


But I am not the maintainer here. Of course I do accept your decision. I 
simply offered my point of view as a user.


Kind
Christian buhtz

Am 17.03.2024 18:42 schrieb Debian Bug Tracking System:

This is an automatic notification regarding your Bug report
which was filed against the www.debian.org package:

#1067029: www.debian.org: Landing page missing donation information

It has been closed by Thomas Lange .

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Thomas Lange
 by
replying to this email.

Bug#1017720: nfs-common: No such file or directory

2024-03-15 Thread Kenneth C. Schalk


I've been looking for an explanation for a similar kind of failure.  I
wonder if the core problem is the same as reported here:

https://bugzilla.opensuse.org/show_bug.cgi?id=1209457

Supposedly fixed by the patch posted to linux-nfs here (also attached
after extraction from the SuSE kernel build source RPM):

https://www.spinics.net/lists/linux-nfs/msg86343.html

And merged into the main-line kernel in 5.15.3, see the Changelog here
(specifically under commit "69e0be0efe53fb012f5db32bc328590745cf8f71"):

https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.15.3

I would be interested to hear whether it makes any difference for the
issue reported in this Debian bug.

--KenFrom 255fc6efacf25d954a986ff058fd9899f322e7d1 Mon Sep 17 00:00:00 2001
From: Trond Myklebust 
Date: Tue, 28 Sep 2021 11:15:53 -0400
Subject: [PATCH] NFS: Don't set NFS_INO_DATA_INVAL_DEFER and NFS_INO_INVALID_DATA
Git-commit: 488796ec1e39fb9194cc8175f770823d40fbf0ed
Patch-mainline: v5.16-rc1
References: stable-5.14.19

[ Upstream commit 488796ec1e39fb9194cc8175f770823d40fbf0ed ]

NFS_INO_DATA_INVAL_DEFER and NFS_INO_INVALID_DATA should be considered
mutually exclusive.

Fixes: 1c341b777501 ("NFS: Add deferred cache invalidation for close-to-open consistency violations")
Signed-off-by: Trond Myklebust 
Tested-by: Benjamin Coddington 
Reviewed-by: Benjamin Coddington 
Signed-off-by: Sasha Levin 
Acked-by: Takashi Iwai 

---
 fs/nfs/inode.c | 9 +++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/fs/nfs/inode.c b/fs/nfs/inode.c
index 6ea1bde33cb6..f9d3ad3acf11 100644
--- a/fs/nfs/inode.c
+++ b/fs/nfs/inode.c
@@ -210,10 +210,15 @@ void nfs_set_cache_invalid(struct inode *inode, unsigned long flags)
 		flags &= ~NFS_INO_INVALID_XATTR;
 	if (flags & NFS_INO_INVALID_DATA)
 		nfs_fscache_invalidate(inode);
-	if (inode->i_mapping->nrpages == 0)
-		flags &= ~(NFS_INO_INVALID_DATA|NFS_INO_DATA_INVAL_DEFER);
 	flags &= ~(NFS_INO_REVAL_PAGECACHE | NFS_INO_REVAL_FORCED);
+
 	nfsi->cache_validity |= flags;
+
+	if (inode->i_mapping->nrpages == 0)
+		nfsi->cache_validity &= ~(NFS_INO_INVALID_DATA |
+	  NFS_INO_DATA_INVAL_DEFER);
+	else if (nfsi->cache_validity & NFS_INO_INVALID_DATA)
+		nfsi->cache_validity &= ~NFS_INO_DATA_INVAL_DEFER;
 }
 EXPORT_SYMBOL_GPL(nfs_set_cache_invalid);
 
-- 
2.26.2

Bug#921239:

2024-03-07 Thread c . buhtz

I support this wish because of the low quality German translation of the 
current man page.


Translating it is waste of ressources.
It is also not clear where the translation comes from Upstream do not 
provide translations.
It is obvious that the German man page was translated by a machine or a 
none native speaker.


Kind

Bug#989775: OpenJPEG 2.5.2 fixes CVE-2021-3575

2024-02-28 Thread Andrew C Aitchison





CVE-2021-3575

OpenJPEG 2.5.1 has been released
  https://groups.google.com/g/openjpeg/c/othStX49Yc8
and includes a fix
  https://github.com/uclouvain/openjpeg/pull/1509
for CVE-2021-3575.


OpenJPEG 2.5.2 updates 2.5.1 with a minor bug fix.
https://github.com/uclouvain/openjpeg/blob/v2.5.2/NEWS.md

--
Andrew C. Aitchison  Kendal, UK
   and...@aitchison.me.uk

Bug#1064380: Aw: Re: Bug#1064380: RFS: jpeginfo/1.7.1-1 [Team] -- Prints information and tests integrity of JPEG/JFIF files

2024-02-28 Thread Darryl C. Carter

I'm not on your fucking team. And I said stop sending this fucking spam. 
Wannabee ninja motherfucker.


On 2/28/2024 3:40 AM, xiao sheng wen (肖盛文) wrote:



在 2024/2/27 16:26, Bastian Germann 写道:

The string " $Id: hash $" in "jpeginfo.h" file is almost not change in
upstream.
Even this string changed in upstream, it will not affect do deb package.

"almost no change" is a change and dpkg-source will not create a source package 
for me.

Do you meet this question?
How to reproduce it?

I don't understand it now.


How are you able to create one from the released tarball?

When upstream release a new version, do a tag on one commit,
The "jpeginfo.h" file is not change in this tag version, is it?
--
肖盛文 xiao sheng wen
https://www.atzlinux.com  《铜豌豆 Linux》基于 Debian 的 Linux 中文 桌面 操作系统
Debian QA page:https://qa.debian.org/developer.php?login=atzlinux%40sina.com
Debian salsa:https://salsa.debian.org/atzlinux-guest
GnuPG Public Key: 0x00186602339240CB

Bug#989775: CVE-2021-3575

2024-02-26 Thread Andrew C Aitchison




OpenJPEG 2.5.1 has been released
  https://groups.google.com/g/openjpeg/c/othStX49Yc8
and includes a fix
  https://github.com/uclouvain/openjpeg/pull/1509
for CVE-2021-3575.

--
Andrew C. Aitchison  Kendal, UK
   and...@aitchison.me.uk

Bug#1064278: xkb-data: Spanish (Macintosh) Layout removed from the list of keyboard distributions

2024-02-19 Thread Julio C. Ortega


Package: xkb-data
Version: 2.38-2
Severity: normal

Dear Maintainer,

In trixie, upon upgrading xkb-data from 2.38-2 to 2.41-2 the Spanish 
(Macintosh) Layout was removed from the list of distributions avaible 
for selection, as per:


diff /usr/share/X11/xkb-2.41/symbols/es xkb-2_38/xkb/symbols/es

1c1
< // Modified for a real Spanish keyboard by Jon Tombs.
---
> // Keyboard layouts for Spain.
2a3
> // Modified for a real Spanish keyboard by Jon Tombs.
15c16
< key     { [exclamdown, questiondown, dead_cedilla, 
dead_ogonek ]    };

---
> key     { [exclamdown, questiondown, dead_cedilla, 
dead_ogonek]};

44a46
> key     { [ j,  J, ezh,  EZH ] };
48c50
< key     { [ minus, underscore, dead_belowdot,    
abovedot ]};

---
> key     { [ minus, underscore, ellipsis, abovedot ]};
51c53
< // Spanish mapping (note R-H exchange)
---
> // Spanish Dvorak mapping (note R-H exchange)
133,138d134
< // Copied from macintosh_vndr/es
< partial alphanumeric_keys
< xkb_symbols "mac" {
< include "es"
< name[Group1]= "Spanish (Macintosh)";
< };

So i'm unable to select it.

Please add the layout back, it may have been removed due to changes 
upstream.



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

--
Julio C. Ortega

Bug#1064250: bbpager segfaults after a while of use

2024-02-18 Thread C. Petersen

Package: bbpager
Version: 0.4.7-10
Severity: important
X-Debbugs-Cc: c.peter...@firemail.de

Dear Maintainer,


bbpager, wether started seperately or from /home/me/.fluxbox/startup segfaults
after a while of not being idle. This is true for the package from the
repository or one built from debian source.


(gdb):
#0  std::_List_iterator::operator++ (this=0x7fffdac0)
at /usr/include/c++/12/bits/stl_list.h:297
__tmp = 
#1  0x55564ee6 in WMInterface::updateWindowList (this=0x555eb1c0)
at ./src/wminterface.cxx:84
it = 49
it_end = 49
pit = 
pit_end = 0x2
window_vect = std::vector of length 3, capacity 3 = {25165838,
27262990, 29360132}
pwindow = 0x555b0b30
#2  0x555653fc in WMInterface::propertyNotifyEvent
(this=0x555eb1c0, event=0x7fffdbc0)
at ./src/wminterface.cxx:185
No locals.
#3  0x77e465b0 in bt::Application::run() () from /lib/x86_64-linux-
gnu/libbt.so.0
No symbol table info available.
#4  0xe9a2 in main (argc=1, argv=0x7fffe168) at
./src/main.cxx:112
bbpager = { = {}, resource =
0x555e5620, desktop_nr = 4,
  wminterface = 0x555eb1c0, root_window = 963, pager_window_list =
std::__cxx11::list = {
[0] = 0x555b2950, [1] = 0x555b0b30}, desktop_window_list =
std::__cxx11::list = {
[0] = 0x555b0d40, [1] = 0x555ea1a0, [2] = 0x555ffa10,
[3] = 0x555ffc60},
  wm_init = false, number_of_desktops = 4, current_desktop_nr = 2,
iargv = 0x0, iargc = 0,
  row_last = 0, column_last = 0, _ewmh = 0x555b93d0,
xa_wm_delete_window = 338,
  xa_wm_state = 389, current_screen_info = @0x55587340,
current_screen = 0,
  frame_window = 0x555ef300, config = @0x7fffdda0}
i = 1
options = {withdrawn = false, decorated = false, shape = false, _argc =
1, _argv = 0x7fffe168,
  _geometry = "", rc_filename = "", blackbox_rc_filename = "", app_name
= "/usr/bin/bbpager",
  display_name = ""}

coredump:

Message: Process 140913 (bbpager) of user 1000 dumped core.

Stack trace of thread 140913:
#0  0x55f7f1d3c918
_ZNSt14_List_iteratorIP11PagerWindowEppEi (bbpager + 0x8918)
#1  0x55f7f1d44ee6 _ZN11WMInterface16updateWindowListEv
(bbpager + 0x10ee6)
#2  0x55f7f1d453fc
_ZN11WMInterface19propertyNotifyEventEPK14XPropertyEvent (bbpager + 0x113fc)
#3  0x7fabc86df5b0 _ZN2bt11Application3runEv (libbt.so.0 +
0x115b0)
#4  0x55f7f1d3e9a2 main (bbpager + 0xa9a2)
#5  0x7fabc824624a __libc_start_call_main (libc.so.6 +
0x2724a)
#6  0x7fabc8246305 __libc_start_main_impl (libc.so.6 +
0x27305)
#7  0x55f7f1d39791 _start (bbpager + 0x5791)
ELF object binary architecture: AMD x86-64

earlier strace (with the package from Debian):
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="\24\0\6\0\303\3\0\0W\1\0\0!\0\0\0\0\0\0\0\1\0\0\0",
iov_len=24}, {iov_base=NULL, iov_len=0}, {iov_base="", iov_len=0}], 3) = 24
poll([{fd=3, events=POLLIN}], 1, -1)= 1 ([{fd=3, revents=POLLIN}])
recvmsg(3, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\1
7\n\1\0\0\0!\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., iov_len=4096}],
msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 36
recvmsg(3, {msg_namelen=0}, 0)  = -1 EAGAIN (Die Ressource ist zur Zeit
nicht verfügbar)
recvmsg(3, {msg_namelen=0}, 0)  = -1 EAGAIN (Die Ressource ist zur Zeit
nicht verfügbar)
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="\16\0\2\0\3\0`\2", iov_len=8}, {iov_base=NULL,
iov_len=0}, {iov_base="", iov_len=0}], 3) = 8
poll([{fd=3, events=POLLIN}], 1, -1)= 1 ([{fd=3, revents=POLLIN}])
recvmsg(3, {msg_name=NULL, msg_namelen=0,
msg_iov=[{iov_base="\0\t8\n\3\0`\2\0\0\16\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
iov_len=4096}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 32
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3,
[{iov_base="\f\0\7\0\232\0\0\2\17\0\0\0\21\0\0\0\21\0\0\0\23\0\0\0\4\0\0\0\f\0\4\0"...,
iov_len=112}, {iov_base=NULL, iov_len=0}, {iov_base="", iov_len=0}], 3) = 112
poll([{fd=3, events=POLLIN}], 1, -1)= 1 ([{fd=3, revents=POLLIN}])
recvmsg(3, {msg_name=NULL, msg_namelen=0,
msg_iov=[{iov_base="\f\09\n\232\0\0\2\0\0\0\0\23\0\4\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
iov_len=4096}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 32
poll([{fd=3, events=POLLIN}], 1, -1)= 1 ([{fd=3, revents=POLLIN}])
recvmsg(3, {msg_name=NULL, msg_namelen=0,
msg_iov=[{iov_base="\f\0:\n\20\0\0\2$\0\21\0\2\0\4\0\1\0\0\0\0\0\0\0\0\0

Bug#1062827: RFP: pydevtool -- CLI dev tools powered by pydoit

2024-02-03 Thread c . buhtz


I checked upstream README.md.
I have no clue what this is.

Can someone explain please?

Am 03.02.2024 18:05 schrieb dpars...@debian.org:

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-pyt...@lists.debian.org
Control: affects -1 src:scipy

* Package name: pydevtool
  Version : 0.3.0
  Upstream Contact: Eduardo Schettino 
* URL : https://github.com/pydoit/pydevtool
* License : MIT
  Programming Lang: Python
  Description : CLI dev tools powered by pydoit

Python dev tool. doit powered, integration with:
- click and rich for custom CLI
- linters: pycodestlye, pyflakes

pydevtool is used by scipy's new dev.py developer script,
which upstream now intends us to use for running scipy tests, see
https://scipy.github.io/devdocs/dev/contributor/devpy_test.html

Until pydevtool is available, our scipy build will have to invoke
pytest directly, which means the debian test environment is discrepant
from that expected by scipy developers until pydevtool becomes
available.

Uses doit, so should be maintained by the Debian Python Team
alongside the doit package.

Bug#990343:

2024-01-30 Thread c . buhtz


The problem is fixed in version 1.4.2.

Bug#1061974:

2024-01-30 Thread c . buhtz


And also using "Package: backintime" do not work as expected.

A message like this result in new bugs and not in closing an existing 
one.


See this two examples:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061973
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061975

I am confused.

Kind

Bug#1060305: libifd-cyberjack6: Package is out of date. 3 new hardware devices are not supported, which are already supported in upstream

2024-01-08 Thread Oliver C.

Package: libifd-cyberjack6
Version: 3.99.5final.sp14-2
Severity: important
Tags: a11y upstream
X-Debbugs-Cc: s...@kernelport.com, siret...@tauware.de, kreuzritter2...@gmx.de

The current version available in the Debain Stable's (12) repository is
3.99.5final.sp14-2 and 3.99.5final.sp14-2+b1 in unstable (SID). But the
manufacturer's version is 3.99.5final.sp16.

See here for the upstream deb package:
https://support.reiner-sct.de/downloads/LINUX/V3.99.5_SP16/libifd-
cyberjack6_3.99.5final.sp16_amd64_d12.deb

And the source release:
https://support.reiner-sct.de/downloads/LINUX/V3.99.5_SP16/pcsc-
cyberjack-3.99.5final.SP16.tar.bz2

The changelog of this much newer version 3.99.5final.sp16 shows the following:

 Begin changelog:
pcsc-cyberjack (3.99.5final.sp16) unstable; urgency=low
  * add REINER SCT cyberJack RFID standard EN

 -- Frank Neuber   Thu, 26 Oct 2023 22:46:54 +0200

pcsc-cyberjack (3.99.5final.sp15) unstable; urgency=low
  * add REINER SCT cyberJack wave HUN
  * add REINER SCT cyberJack RFID komfort FON

 -- Frank Neuber   Fri, 01 Oct 2021 08:11:04 +

pcsc-cyberjack (3.99.5final.sp14) unstable; urgency=low
  * Update to the Reiner-SCT repository rev cyberJack@1454

 -- Frank Neuber   Mon, 02 Dec 2019 16:57:46 +0100
### End changelog

This means, that the devices:
* REINER SCT cyberJack RFID standard EN
* REINER SCT cyberJack wave HUN
and
* REINER SCT cyberJack RFID komfort FON
are not supported in the current version of Debian.

The device REINER SCT cyberJack RFID komfort FON device is for users with
disabilities.
As of now, all three devices are not supported by Debian 12 because this
package is out of date.

You should also read bug report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010675
It might be related to this bug #1010675, because the new upstream version
ships as .bz2 file and in the other
bug report has someone mentioned, that the old uscan filter does only search
for .tar.gz files.
But this is definitely not a minor bug, like the this other bug report claims,
when you can't use these new three devices.

The devices
* REINER SCT cyberJack wave HUN
and
* REINER SCT cyberJack RFID komfort FON
got a patch in upstream on Fri, 01 Oct 2021. Debian stable was released in June
10, 2023.

So it's high time that the new version is added to Debian SID and a Debian
backport version for Debian 12 or an update with the next Debian 12 point
release is added. After all, this is about driver support and support for new
hardware.


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

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

Versions of packages libifd-cyberjack6 depends on:
ii  libc6 2.36-9+deb12u3
ii  libgcc-s1 12.2.0-14
ii  libstdc++612.2.0-14
ii  libusb-1.0-0  2:1.0.26-1
ii  pcscd 1.9.9-2

libifd-cyberjack6 recommends no packages.

Versions of packages libifd-cyberjack6 suggests:
ii  pcsc-tools  1.6.2-1

-- no debconf information


changelog.Debian.gz
Description: application/gzip

Bug#1058794: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2024-01-04 Thread Ana C. Custura

Hi,

Thank you very much for looking into this, it is much appreciated and you can 
go ahead with the upload. 

Ana

On Thu, Jan 4, 2024, at 12:19 PM, Alexandre Detiste wrote:
> Le jeu. 4 janv. 2024 à 07:48, Andreas Tille  a écrit :
>> > @Vincent: this one package "gtextfsm" is yours
>> > do you green light an upload ?
>>
>> If you ask me the package is team maintained and a "Team upload"
>> should be fine.
>
> Hi, I just try to follow the rules I agreed on last month.
>
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#id2
>
> | Team in Uploaders is a weak statement of collaboration. Help in
> maintaining the package is appreciated,
> | commits to the Git repository are freely welcomed, but before
> uploading, please contact the Maintainer for the green light.
>
> There are not so many packages where "Uploader = DPT" to begin with,
> so this might not well a well-known practice...
>
> So I'm formally asking Ana & PaN for approval to upload "lexicon" and 
> "dioptas".
> (lexicon is a one line change, dioptas needs to package a new release)
>
> @Vincent: thanks.
>
> Greetings
>
> -
>
> Debian Python Team 
>dioptas (U)
>gtextfsm (U)
>lexicon (U)
>
> Ana Custura 
>lexicon
>
> Debian PaN Maintainers 
>dioptas

Bug#1059770: php-horde-core: Error "ReflectionMethod::__construct(): Argument #2 ($method) cannot be null"

2023-12-31 Thread Nicolas C.

Bug#1059571: php-horde-tree: Declaration of Horde_Tree_Renderer_Jquerymobile must be compatible with Horde_Tree_Renderer_Base

2023-12-28 Thread Nicolas C.

Package: php-horde-tree
Version: 2.0.5-6
Severity: important

Dear Maintainer,

While browsing Horde IMP with a mobile device, this error appears in the
logs while trying to access IMAP folders:

PHP Fatal error:  Declaration of 
Horde_Tree_Renderer_Jquerymobile::_buildTree($node_id, $special) must be 
compatible with Horde_Tree_Renderer_Base::_buildTree($id) in 
/usr/share/php/Horde/Tree/Renderer/Jquerymobile.php on line 46

On the device, folders aren't displayed.

Regards,

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

Kernel: Linux 6.1.0-16-cloud-amd64 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages php-horde-tree depends on:
ii  php-common   2:93
ii  php-horde-exception  2.0.8-10
ii  php-horde-url2.2.6-9
ii  php-horde-util   2.5.12-2

php-horde-tree recommends no packages.

php-horde-tree suggests no packages.

-- no debconf information

Bug#1055192: RFS: golang-github-apenella-go-ansible

2023-12-24 Thread Ananthu C V

On Sat, Dec 23, 2023 at 10:35:08PM +0530, Nilesh Patra wrote:
> I finally got some time to look at this. From what I see, this is just a 
> library
> package (and no binary) and this seems to be the final package you want to 
> get uploaded.
> 
> Generally, all go library packages 'are'/'should be' present in Debian 
> because they are needed
> for a target (binary) package which a user is interested in using. No-one 
> would be keen
> on apt installing golang libraries and fiddling with GOPATH/GOROOT
> rather than a simpler `go get -u` if they want to use them to write code.
> 
> Hence, unless you have any target packages for which these libs are needed, I 
> do not see
> a lot of use of getting this in. Let me know what you'd think. I *do* expect 
> your reponse on this.

It looks that this has been a clear oversight from my side. *I do find this a 
very useful library*
but as you mentioned, since go team convention does not include packaging 
libaries that are not
needed by any binaries, there is probably no real value in getting this in.

As such, please prune the corresponding repositories for the following:
- golang-github-apenella-go-ansible
- golang-github-apenella-go-common-utils
- golang-github-sosedoff-ansible-vault-go

> Thanks!
> 
> Best,
> Nilesh

I feel sincerely sorry that an oversight from my side has ended up taking some 
of your busy schedule
and I apologize for making you spend your time needlessly. I'll try my best to 
make sure such mishapas
does not occur in the future, since it is not beneficial to anyone. And 
regardless of the outcome of
this, thanks a lot for taking a look at the RFS.

Best,
Ananthu

Bug#1057885: mate-desktop-environment: File copy progress dialog shows wrong values on 32-bit Debian 12 MATE

2023-12-09 Thread M C

Package: mate-desktop-environment
Version: 1.26.0+1
Severity: normal
X-Debbugs-Cc: m...@mrdictionary.net

Dear Maintainer,

I installed Debian 12 32-bit x86 from the netinst CD image and selected
the MATE desktop environment.

Within MATE (caja), when copying large files (e.g. over 100MB) between local
folders or from an FTP remote host to a local drive, the file copy progress
dialogue gives highly incorrect numbers.

For example when copying the 200MB file PS3UPDAT.PUP (a Sony PS3 firmware
update) to a USB stick, the file progress copy dialogue reported that the
file was 881.6 PB in size (with a corresponding bizarre file transfer
speed shown). The file seemed to copy normally however. 

Screenshot

https://imgur.com/a/QDNjJtG

To reproduce, install x86 32-bit Debian 12 from the current netinst image
and copy a large file within caja after logging in.

CPU: Pentium(R) Dual-Core CPU T4300 @ 2.10GHz × 2

I've since reinstalled that system with 64-bit Debian 12 which doesn't
show this bug. (The bug was also not present on 32-bit Debian 10; I was using
up-to-date Debian 10 32-bit with MATE on that system up to October 2023.)

Apologies: please disregard the system specs/package automatically attached
as I am reporting from a different system from the one showing this bug.

Regards.

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

Kernel: Linux 6.1.0-13-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mate-desktop-environment depends on:
ii  mate-desktop-environment-core  1.26.0+1

Versions of packages mate-desktop-environment recommends:
ii  atril 1.26.0-2+b1
ii  desktop-base  12.0.6+nmu1~deb12u1
ii  engrampa  1.26.0-1
ii  eom   1.26.0-2
ii  ffmpegthumbnailer 2.2.2+git20220218+dfsg-1+b1
ii  libcanberra-pulse 0.30-10
ii  mate-applet-brisk-menu0.6.2-2
ii  mate-applets  1.26.1-1
ii  mate-backgrounds  1.26.0-1
ii  mate-calc 1.26.0-1
ii  mate-media1.26.0-2
ii  mate-notification-daemon  1.26.0-1+deb12u1
ii  mate-power-manager1.26.0-2+deb12u1
ii  mate-screensaver  1.26.1-1
ii  mate-system-monitor   1.26.0-1
ii  mate-user-guide   1.26.0-1
ii  mate-utils1.26.0-1
ii  pluma 1.26.0-1

Versions of packages mate-desktop-environment suggests:
pn  mail-reader | thunderbird
pn  mate-desktop-environment-extras  
ii  network-manager-gnome1.30.0-2
pn  x-www-browser | firefox  

-- no debconf information

Bug#1055930: ITP: yte -- YAML template engine with Python expressions

2023-11-14 Thread Ananthu C V

Package: wnpp
Severity: wishlist
Owner: Ananthu C V 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-pyt...@lists.debian.org

* Package name: yte
  Version : 1.5.1
  Upstream Author : Johannes K��ster 
* URL : https://github.com/yte-template-engine/yte
* License : Expat
  Programming Lang: Python
  Description : YAML template engine with Python expressions

Binary package names: python3-yte
 YTE is a template engine for YAML format that utilizes the YAML structure
 in combination with Python expressions for enabling to dynamically build
 YAML documents.
 .
 The key idea of YTE is to rely on the YAML structure to enable conditionals,
 loops and other arbitrary Python expressions to dynamically render YAML
 files. Python expressions are thereby declared by prepending them with a ?
 anywhere in the YAML. Any such value will be automatically evaluated by YTE,
 yielding plain YAML as a result. Importantly, YTE templates are still valid
 YAML files (for YAML, the ? expressions are just strings).

Bug#1055221: qemu-system is not compiled with pipewire audio support

2023-11-02 Thread Francesco C

> Personally I don't see value in pw support in qemu for now.

I didn't even know that qemu has introduced pipewire support in the
latest version.
I discovered it while trying to find an alternative for the audiodev
driver because of the issue I've experienced :

- pulse+vga , pulse+virgl , pulse without graphics -> audio stream
loses samples ( probably because of my low end hardware )

- the same with sdl

- alsa doesn't work for any reason

- dbus,jack not viable

- spice works perfectly but I have to use qxl driver for graphics that
suffers of a nasty bug on the host side that leads to an unrecoverable
crash of the guest graphics since a couple of months ("failed to
allocate VRAM BO"
:https://groups.google.com/g/linux.kernel/c/w7Ee-j9YonY ).

- pulse+spice the same as above

That's it.

Regards.

Bug#1055221: qemu-system is not compiled with pipewire audio support

2023-11-02 Thread Francesco C

Package: qemu-system
Version: 1:8.1.2+ds-1
Severity: normal

Dear Maintainer,

Qemu mainline version 8.1.2 claims supporting pipewire audio as host
audio driver , but debian packages is not compiled with that feature :

> qemu-system-amd64 -audiodev help
Available audio drivers:
none
alsa
dbus
jack
oss
pa
sdl
spice
wav

The changelog in the main site explains that pipewire support is
enabled when the build system detects libpipewire installed on the
system.

Debian package should (build-)depends on libpipewire-*-dev to enable
pipewire audio host support.

Bug#1055196: ITP: golang-github-apenella-go-common-utils -- Set of golang utilities

2023-11-01 Thread Ananthu C V

Package: wnpp
Severity: wishlist
Owner: Ananthu C V 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian...@lists.debian.org

* Package name: golang-github-apenella-go-common-utils
  Version : 0.5.1-1
  Upstream Author : Aleix Penella 
* URL : https://github.com/apenella/go-common-utils
* License : Expat
  Programming Lang: Go
  Description : Set of golang utilities

 Go-common-utils repository contains a set of helpers or common functions
 which could be used such a library from any Golang project.
 .
 Common utils are organized in:
 .
   data: Functions to manipulate data structures.
   errors: An error interface implementation that could have a
 context and a list of wrapped errors.
   logger: Manages log messages (no longer maintained)
   networking: Functions for networking purpose.
   os: Functions to interactuate with the system.
   transformer/string: Functions to manipulate messages
   types: Custom types definition.

This is a dependency for packaging go-ansble(#1055192).

Bug#1055195: ITP: golang-github-sosedoff-ansible-vault-go -- Go package to interact with Ansible Vault files

2023-11-01 Thread Ananthu C V

Package: wnpp
Severity: wishlist
Owner: Ananthu C V 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian...@lists.debian.org

* Package name: golang-github-sosedoff-ansible-vault-go
  Version : 0.2.0-1
  Upstream Author : Dan Sosedoff 
* URL : https://github.com/sosedoff/ansible-vault-go
* License : Expat
  Programming Lang: Go
  Description : Go package to interact with Ansible Vault files

 Go package to read/write Ansible Vault secrets.

This is a dependency for packaging go-ansible(#1055192).

Bug#1055192: ITP: golang-github-apenella-go-ansible -- Go package for executing ansible from Golang applications

2023-11-01 Thread Ananthu C V

Package: wnpp
Severity: wishlist
Owner: Ananthu C V 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian...@lists.debian.org

* Package name: golang-github-apenella-go-ansible
  Version : 1.2.0-1
  Upstream Author : Aleix Penella 
* URL : https://github.com/apenella/go-ansible
* License : Expat
  Programming Lang: Go
  Description : Go package for executing ansible from Golang applications

 Go-ansible is a Go package that enables the execution of ansible-playbooks
 and ansible commands directly from Golang applications. It supports a
 wide range of options for each command, enabling smooth integration of
 Ansible functionality into projects.

Debian currently does not seem to have any Ansible libaries for Golang.
It would be extremely helpful to have this one in debian.

Bug#1055191: ITP: golang-github-apenella-go-ansible -- Go package for executing ansible from Golang applications

2023-11-01 Thread Ananthu C V

Package: wnpp
Severity: wishlist
Owner: Ananthu C V 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian...@lists.debian.org

* Package name: golang-github-apenella-go-ansible
  Version : 1.2.0-1
  Upstream Author : Aleix Penella 
* URL : https://github.com/apenella/go-ansible
* License : Expat
  Programming Lang: Go
  Description : Go package for executing ansible from Golang applications

 Go-ansible is a Go package that enables the execution of ansible-playbooks
 and ansible commands directly from Golang applications. It supports a
 wide range of options for each command, enabling smooth integration of
 Ansible functionality into projects.

Debian currently does not seem to have any Ansible libaries for Golang.
It would be extremely helpful to have this one in debian.

Bug#1054136: ITP: node-prosemirror-tables -- enhances table support

2023-10-17 Thread Ananthu C V

Package: wnpp
Severity: wishlist
Owner: Ananthu C V 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: node-prosemirror-tables
  Version : 1.3.4
  Upstream Author : ProseMirror
* URL : https://github.com/prosemirror/prosemirror-tables
* License : Expat
  Programming Lang: JavaScript
  Description : enhances table support

 This module defines a schema extension to support tables with rowspan/colspan 
support,
 a custom selection class for cell selections in such a table, a plugin to 
manage such
 selections and enforce invariants on such tables, and a number of commands to 
work with
 tables.

This package is a dependency required to package tiptap (#963902), a dependency 
used by
gitlab.

I intend to package this myself and maintain it as part of the javascript team. 
But as I
hold no uploading rights, I will be needing a sponsor.

Bug#1053905: emacs-common-non-dfsg: not included among emacs 29 backported packages

2023-10-13 Thread Brandon C. Irizarry

Package: emacs-common-non-dfsg
Version: 1:28.2+1-2
Severity: wishlist
X-Debbugs-Cc: brandon.iriza...@gmail.com

Dear Maintainer,

I recently installed the Emacs 29 Bookworm backport; however, the
documentation is still at version 28. I tried to install
emacs-common-non-dfsg from backports, but no backport exists for it
yet. This message is a simple request for the backport to be made.

Thanks!

- Brandon

-- System Information:
Debian Release: 12.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.31-antix.1-amd64-smp (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: runit (via /run/runit.stopit)

Versions of packages emacs-common-non-dfsg depends on:
ii  dpkg  1.21.22
ii  install-info  6.8-6+b1

emacs-common-non-dfsg recommends no packages.

emacs-common-non-dfsg suggests no packages.

-- no debconf information

Bug#985260:

2023-10-13 Thread c . buhtz


Dear Francesco,

can you please have a look at the latest upstream release of Back In 
Time. Upstream assumes the problem is solved. Can you confirm this?


Kind
Christian

Bug#1053858: ITP: node-tiptap-core -- headless rich text editor

2023-10-12 Thread Ananthu C V

Package: wnpp
Severity: wishlist
Owner: Ananthu C V 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: node-tiptap-core
  Version : 2.1.12
  Upstream Author : Tiptap GmbH
* URL : https://tiptap.dev
* License : Expat
  Programming Lang: JavaScript
  Description : headless rich text editor

 A headless, framework-agnostic and extendable rich text editor, 
 based on ProseMirror.

@tiptap/core is one of the dependencies used by gitlab.

I am intending to maintain this as part of the javascript team.
As I do not have uploading rights, I will be needing a sponspor.

Bug#1053520: RFS: golang-github-ozeidan-fuzzy-patricia/3.0.0-1

2023-10-07 Thread Ananthu C V

Dear Go team,

I am looking for a sponsor for the package 
"golang-github-ozeidan-fuzzy-patricia".
This package is a prerequisite for upcoming package "lazygit" (#908894).

I pushed to our team's Salsa:

  https://salsa.debian.org/go-team/packages/golang-github-ozeidan-fuzzy-patricia

Could you please review/sponsor this?
Any kind of reviews and suggestions are appreciated

Bug#1053520: RFS: golang-github-ozeidan-fuzzy-patricia/3.0.0-1

2023-10-07 Thread Ananthu C V

Dear Go team,

I am looking for a sponsor for the package 
"golang-github-ozeidan-fuzzy-patricia".
This package is a prerequisite for upcoming package "lazygit" (#908894).

I pushed to our team's Salsa:

  https://salsa.debian.org/go-team/packages/golang-github-ozeidan-fuzzy-patricia

Could you please review/sponsor this?
Any kind of reviews and suggestions are appreciated

Bug#1053520: ITP: golang-github-ozeidan-fuzzy-patricia -- A generic patricia trie (also called radix tree) implemented in Go (Golang).

2023-10-05 Thread Ananthu C V

Package: wnpp
Severity: wishlist
Owner: Ananthu C V 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian...@lists.debian.org

* Package name: golang-github-ozeidan-fuzzy-patricia
  Version : 3.0.0
  Upstream Author : Omar Zeidan
* URL : https://github.com/ozeidan/fuzzy-patricia.git
* License : Expat 
  Programming Lang: Go
  Description : A generic patricia trie (also called radix tree) 
implemented in Go (Golang).

A generic patricia trie (also called radix tree) implemented in Go (Golang).

The patricia trie as implemented in this library enables fast visiting of items 
in some particular ways:

visit all items saved in the tree,
visit all items matching particular prefix (visit subtree), or
given a string, visit all items matching some prefix of that string.

[]byte type is used for keys, interface{} for values.

Trie is not thread safe. Synchronize the access yourself.

This package is in the dependency tree of Lazygit (#908894)

Bug#1037133:

2023-09-19 Thread c . buhtz


Upstream responded to my questions about how this was fixed.
They pointed to two PullRequests.

https://github.com/owncloud/client/pull/10058
https://github.com/owncloud/client/pull/10065

My apologize. I'm not experienced enough to provide this as a patch to 
the current Debian version. Hope someone else can go this way.


Kind
Christian

Bug#1043124: zfs-dkms: module fails to build for Linux 6.5: None of the expected "bops->release()" interfaces were detected.

2023-09-16 Thread Francesco C

>(Completely unrelated, but browsing the issues it popped up that encryption is
>very broken above 6.3,
>and it has been somewhat broken on older kernels too; not one people lost their
>data due to upgrading
> beyond 6.3, so beware.

"Encryption is very broken" seems too generic : it seems (to me) that
the reported issue affects zfs "native" encryption , not luks with
[(plain) zfs].

Bug#1051921: CVE-2023-1393 and TigerVNC

2023-09-14 Thread Andrew C Aitchison


Package: tigervnc-standalone-server
Version: 1.12.0+dfsg-8

RedHat have released updates to tigervnc to address CVE-2023-1393, e.g.
  https://access.redhat.com/errata/RHSA-2023:1592
but https://security-tracker.debian.org/tracker/CVE-2023-1393
does not mention tigervnc, and the latest version predates the CVE.

I guess this relates to the binary package tigervnc-standalone-server
but the fix might be needed in one or more of the other tigervnc binary
packages.

Upstream discussion at
https://groups.google.com/g/tigervnc-users/c/5dq5O2OAoQI

--
Andrew C. Aitchison  Kendal, UK
   and...@aitchison.me.uk

Bug#940319: [#940319 backintime] run test suite during build" : Request for maintainer feedback

2023-08-23 Thread c . buhtz


Dear Jonathan,
before investing my ressources into a solution can you please give me 
feedback about my proposal.

Would this fit to your needs as DM and solve this bug?

Kind
Christian

Bug#1050203: bsd-mailx and selinux not co-operating

2023-08-21 Thread Bhasker C V


Package: bsd-mailx

Version: 8.1.2-0.20220412cvs-1


In follow-up to https://groups.google.com/g/linux.debian.user/c/vsYHlu728Ig


$ echo hello | mail -s test xx...@yyy.xyz <https://groups.google.com/>
2023-08-20 14:39:30 1qXieQ-000Bpa-1P 1qXieQ-000Bpa-1P no recipients 
found in headers

Can't send mail: sendmail process failed with error code 1


however the same works fine when I put selinux in permissive state (no 
warnings shown in audit/dmesg).

This is NOT a configuration issue but looks like selinux compatibility issue

A quick ltrace says

1qXia0-000BPb-0a Failed to create spool file 
/var/spool/exim4//input//1qXia0-000BPb-0a-D: Permission denied



However there are no avc: messages for me to allow this through in my 
selinux module

I even tried a custom policy

allow unconfined_t exim_spool_t:file { open read write create };
allow unconfined_t exim_spool_t:dir { open read write };


since /var/spool/exim4/input has exim_spool_dir set in it
ls -lZd

drwxr-x---. 2 Debian-exim Debian-exim system_u:object_r:exim_spool_t:s0 
4096 Aug 22 00:10 /var/spool/exim4/input


I cant fine any booleans either ..

Many scripts including chkrootkit and tripwire are failing because mail 
cannot send mails(becauses debian uses bsd-mailx as default)


--
Bhasker C V
Secure Mails:http://keys.gnupg.net/pks/lookup?op=get&search=0x4D05FEEC54E47413
Registered Linux User: #306349

Bug#1024501: Can we close this bug report?

2023-08-20 Thread Roberto C . Sánchez

Since it is evident that the Code of Conduct does not apply to the
content of packages in this way (nor can it), and absent a clear policy
permitting the removal of a package based on its content not being
agreeable, can we close this bug report?

Regards,

-Roberto
-- 
Roberto C. Sánchez

Bug#1043046:

2023-08-08 Thread c . buhtz


Dear Armin,
maybe you can save the time generating all the diagnostic output I asked 
for.


I'm not absolute sure about this point but based on my research it is 
not possible to configure Back In Time (BIT) that way that it run "Every 
Day" and at boot. "Every Day" do result in a crontab line like "0 12 * * 
* cmd" (or another value for minute and hour). And as we know cron does 
not catch up jobs.


My hypothesis is that you might have configured your Debian 11 machines 
explicit and without using BIT in a way that the described behavior is 
possible. You might have created an anacron job?
The behavior you describe for Debian 12 is usual and the expected. There 
is nothing wrong with it.


Kind
Christian

Bug#1043046:

2023-08-07 Thread c . buhtz


Please show the output of

cat /etc/anacrontab

Please also think hard about if you have configured something on your 
Debian 11 machines in the past?
I'm not an expert in cron and anacron but in my understanding anacron do 
not start cron-jobs after their scheduled time (in hours in minutes). 
But I might be wrong.


Maybe you manually configured your Debian 11 in the past that way and 
forgot it then?
The upgrade to Debian 12 might overwrite your anacron/cron config with 
some default behavior?


It is just an idea and I'll investigate further. It is also possible 
that there is a BIT bug.

Bug#1043046:

2023-08-07 Thread c . buhtz


Dear Armin,

thanks for reporting this. I'm member of the upstream maintainer team 
and not a Debian person. Please be aware that the current maintainer 
team is quit new to BIT and we are not yet familiar with all parts of 
the code and the behavior of BIT. But I'll try to assist you. I need to 
investigate the issue.


Let me try to rephrase. You have a snapshot profile schedule "Every 
day". This results in a crontab line like "00 12 * * *"


In Debian 11 (Bullseye, oldstable) the job was started at the first boot 
on each day and at a specified time (e.g. 12 o'clock). Correct?
In Debian 12 (Bookworm, stable) the job do not start at boot but only at 
the specified time (e.g. 12 o'clock).


This makes me wonder. I would assume that the Debian 12 behavior is 
"correct". I wonder why Debian 11 to run that job at boot when there is 
just a crontab line. On GNU Linux it is often that cron and anacron are 
somehow connected in several ways. Anacron is often involved while 
booting. Maybe something here changed between 11 and 12. I'll 
investigate that.


On Debian 11 you run BIT 1.2.1-3 from the official Debian repository?

Do you still have a working Debian 11 machine? Or did you updated all 
your machines?
If you have Debian 11 and 12 available please provide the following 
information from both machines. If not Debian 12 only is also OK.


Run "backintime --diagnostics" (only with BIT 1.3.4) in a terminal and 
give the output.


Show roots crontab with "sudo crontab -l" (as user) or "crontab -l" (as 
root).


Show the users crontab entries related to BIT with "crontab -l | grep 
backintime".


How did you verify (via "journalctl" ?) if BIT was run or not? Maybe it 
run but decided nothing changed and there is no need for a new snapshot.


Maybe you can provide the relevant syslog entries via

journalctl --since "two weeks" | grep -i -e backintime -e boot

Kind
Christian

Bug#1042682: mongo-c-driver: FTBFS with Sphinx 7.1, docutils 0.20: make[3]: *** [src/libbson/doc/CMakeFiles/bson-html.dir/build.make:554: src/libbson/doc/html/api.html] Error 2

2023-08-02 Thread Roberto C . Sánchez

tags 1042682 + fixed-upstream pending
thanks

I have confirmed that this is fixed on the upstream master branch
(commit ba5ab6de26a874d33b0abc3d2b46961a69380e7a seems like the most
likely, but I did not bisect to confirm).

When the upstream 1.25.0 release is made and then packaged for Debian,
this fix will land in unstable.

Regards,

-Roberto

-- 
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com

Bug#1042428: qa.debian.org: Missing description for lintian warning tags (https://udd.debian.org/lintian/?packages=)

2023-07-28 Thread c . buhtz


Dear Sebastiaan,

thanks for reporting back.

Am 28.07.2023 10:00 schrieb Sebastiaan Couwenberg:

You can get the tag description from lintian-explain-tags:


I know that. The bug report wasn't a support question but a feature 
request.


The infos about the meaning of the tags need to be part of the linked 
website or somehow should linked there.

Bug#940319:

2023-07-21 Thread c . buhtz


No response to my questions.
I also asked on the debian python team mailing list.

Without response I'll close the ticket on next iteration.

Bug#1040423: golang-yaml.v2: Build (tests) fail on 32-bit arch

2023-07-05 Thread Roberto C. Sanchez

Source: golang-yaml.v2
Version: 2.2.2-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

In working on golang-yaml.v2 for an LTS update, I noticed that the build
fails on 32-bit arch (i386 and armhf, in this specific case).

https://salsa.debian.org/lts-team/packages/golang-yaml.v2/-/pipelines/548358

The specific failure is:

   dh_auto_test -O--buildsystem=golang
cd obj-i686-linux-gnu && go test -vet=off -v -p 2 gopkg.in/yaml.v2
# gopkg.in/yaml.v2_test [gopkg.in/yaml.v2.test]
src/gopkg.in/yaml.v2/decode_test.go:134:33: constant -9223372036854775808 
overflows int
FAILgopkg.in/yaml.v2 [build failed]

The source lines in that vicinity are:

}, {
"bin: 
-0b1000",
map[string]interface{}{"bin": -9223372036854775808},
}, {

The source is the same in the latest version (on the debian/sid branch).

It seems like since the binary packages in this source package are
"Architecture: all" and that since the buildds selected to build
"Architecture: all" packages are 64-bit systems, that this failure is
not one that is encountered in practice for official Debian builds.

However, it might be good to detect when the build is running on a
32-bit system and either not run the tests, or conditionally patch the
source to exclude that particular overflow problem.

Regards,

- -Roberto

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEIYZ1DR4ae5UL01q7ldFmTdL1kUIFAmSlt6UACgkQldFmTdL1
kUK1aBAAxLomEtEKbZN0JlMA0U3BJVBdNpnD+jfyjeVfIJU//mQoWYQKv7JDWh2x
MCC+HmMZ7wgWNdzNR0/VE2BRqTamIYrgmF1gZ7QhiUIZ4UYt+TmNbyK6kb716trO
u4exL5v8r0d7yCdvHgm/GWElg5GlzXz66TEQTOswibRdluTrf6t8441lCZDTGCNE
XZq045nYHSa9NG1HgSbkTlAyzGwZnD2vgxLk27JIEoy8T3zVLP5495NmSkiuK+ig
tnBCyX65POpUa3WFy5XvyxNPjrfv1gNkBhQIRCvRDqt3f04rtNlXPfF0QghWZkC4
CQVGnNA8U1YyUwCQq+TQ/eAxRRVsgJ0Az+gkCtF5iitutnlurLL+QgcTuz6EfKKs
j9NUJzuY8gr71z2Bv+WWRcqwIVlK5+X83Tj3GwfJF8lbpiNib9vqJzo3lLqJU9TS
bw2BgkxZ9SsEZj1U/0NCca6fdHOeRHZpVDBWlB4vpKIwkzNNZVGciAQ1Z79YrFrl
xGqbXJQO2FdF+hh3gDfwlfaMsUMKaJz6hPoHIOC3NBKmCJi6R2hPF+HYmgpVb5cr
C/F9lgO8+N8V6azeU2LO+HDZjV1HQI6T9A2c5gp5NfE8ZNupzSnLC1OUdrJXY36J
t0afOewuYoBC8mGDDZ9TJMV+9DmCsyqwSK3KRANpP1EtsaKW/GQ=
=Waos
-END PGP SIGNATURE-

Bug#1035972: isc-dhcp EOL'ed

2023-07-04 Thread Roberto C . Sánchez

On Fri, Jun 16, 2023 at 10:12:22PM +0200, Moritz Muehlenhoff wrote:
> On Fri, Jun 16, 2023 at 01:29:28PM -0400, Roberto C. Sánchez wrote:
> > On Wed, May 17, 2023 at 10:50:34AM +0200, Moritz Muehlenhoff wrote:
> > > 
> > > My take would be to mark it as unsupported after the trixie development 
> > > cycle
> > > has started (this flags awareness, but has no impact on stable releases)
> > > and then revisit the support situation before the trixie freeze (Kea 
> > > might be
> > > a full replacment by then or maybe it turns out the patch support is 
> > > ensured
> > > despite upstream's EOL)
> > > 
> > Hi Moritz,
> > 
> > Now that bookworm is out and (AFAICT) that the trixie development cycle
> > has started, are able to go ahead with marking isc-dhcp as unsupported?
> 
> Ultimately it's the maintainer(s) call, but sounds good to me.
> 
Are you referring to the maintainer of debian-security-support, or the
maintainer of isc-dhcp?

Regards,

-Roberto

-- 
Roberto C. Sánchez

Bug#1040169: smplayer: Smplayer hangs when starting video

2023-07-02 Thread Edward C. Jones

()]
   can't load config client.conf: No such file or directory
[E][14041.464827] pw.conf  | [  conf.c:  963
   pw_conf_load_conf_for_context()] can't load default config client.conf: No
   such file or directory
AO: [pulse] 44100Hz stereo 2ch float
VO: [x11] 854x480 yuv420p
[vo/x11/x11] X11 error: BadDrawable (invalid Pixmap or Window parameter)
[vo/x11/x11] Type: 0, display: 0x7f7bd80456b0, resourceid: 8, serial: 29
[vo/x11/x11] Error code: 9, request code: e, minor code: 0
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7f7bd80456b0, resourceid: 8, serial: 2a
[vo/x11/x11] Error code: 3, request code: 28, minor code: 0
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7f7bd80456b0, resourceid: 1a2, serial: 2b
[vo/x11/x11] Error code: 3, request code: c, minor code: 0
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7f7bd80456b0, resourceid: 1a2, serial: 2d
[vo/x11/x11] Error code: 3, request code: 12, minor code: 0
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7f7bd80456b0, resourceid: 1a2, serial: 2e
[vo/x11/x11] Error code: 3, request code: 2, minor code: 0
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7f7bd80456b0, resourceid: 1a2, serial: 2f
[vo/x11/x11] Error code: 3, request code: 2, minor code: 0
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7f7bd80456b0, resourceid: 1a2, serial: 30
[vo/x11/x11] Error code: 3, request code: 3, minor code: 0
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7f7bd80456b0, resourceid: 1a2, serial: 32
[vo/x11/x11] Error code: 3, request code: 8, minor code: 0
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7f7bd80456b0, resourceid: 1a2, serial: 33
[vo/x11/x11] Error code: 3, request code: 12, minor code: 0
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7f7bd80456b0, resourceid: 1a2, serial: 36
[vo/x11/x11] Error code: 3, request code: 3, minor code: 0
[vo/x11/x11] X11 error: BadDrawable (invalid Pixmap or Window parameter)
[vo/x11/x11] Type: 0, display: 0x7f7bd80456b0, resourceid: 8, serial: 38
[vo/x11/x11] Error code: 9, request code: e, minor code: 0
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7f7bd80456b0, resourceid: 8, serial: 39
[vo/x11/x11] Error code: 3, request code: 28, minor code: 0
INFO_VIDEO_DSIZE=854x480
[vo/x11/x11] X11 error: BadDrawable (invalid Pixmap or Window parameter)
[vo/x11/x11] Type: 0, display: 0x7f7bd80456b0, resourceid: 1a2, serial: 3f
[vo/x11/x11] Error code: 9, request code: 82, minor code: 3
[vo/x11/x11] X11 error: BadDrawable (invalid Pixmap or Window parameter)
[vo/x11/x11] Type: 0, display: 0x7f7bd80456b0, resourceid: 1a2, serial: 40
vo/x11/x11] Error code: 9, request code: 82, minor code: 3
MPV_VERSION=mpv 0.35.1
INFO_VIDEO_WIDTH=854
INFO_VIDEO_HEIGHT=480
INFO_VIDEO_ASPECT=1.779167
INFO_VIDEO_FPS=29.954546
INFO_VIDEO_FORMAT=h264
INFO_VIDEO_CODEC=h264 (H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10)
INFO_DEMUX_ROTATION=
INFO_AUDIO_FORMAT=aac
INFO_AUDIO_CODEC=aac (AAC (Advanced Audio Coding))
INFO_AUDIO_RATE=44100
INFO_AUDIO_NCH=2
INFO_LENGTH=20.664000
INFO_DEMUXER=lavf
INFO_SEEKABLE=yes
INFO_TITLES=
INFO_CHAPTERS=0
INFO_TRACKS_COUNT=2
METADATA_TITLE=
METADATA_ARTIST=
METADATA_ALBUM=
METADATA_GENRE=
METADATA_DATE=
METADATA_TRACK=
METADATA_COPYRIGHT=
INFO_MEDIA_TITLE=chris vs mikey.flv
INFO_STREAM_PATH=/data/pics/videos/trever/chris vs mikey.flv
[vo/x11] can't keep up! Waiting for XShm completion events...
INFO_TRACK_0: video 1 '' '' yes
INFO_TRACK_1: audio 1 '' '' yes
Exiting... (Quit)


=

-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/6 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages smplayer depends on:
ii  libc6   2.36-9
ii  libgcc-s1   12.2.0-14
ii  libqt5core5a5.15.8+dfsg-11
ii  libqt5dbus5 5.15.8+dfsg-11
ii  libqt5gui5  5.15.8+dfsg-11
ii  libqt5network5  5.15.8+dfsg-11
ii  libqt5widgets5  5.15.8+dfsg-11
ii  libqt5xml5  5.15.8+dfsg-11
ii  libstdc++6  12.2.0-14
ii  libx11-62:1.8.4-2+deb12u1
ii  mplayer 2:1.5+svn38408-1
ii  mpv 0.35.1-4
ii  zlib1g  1:1.2.13.dfsg-1

Versions of packages smplayer recommends:
ii  smplayer-l10n22.7.0~ds0-1
ii  smplayer-themes  1:20.11.0-1

smplayer suggests no packages.

-- no debconf information

Bug#1034867: smplayer always crashes in Debian 12

2023-06-21 Thread Edward C. Jones

: 0x7febb40456b0, resourceid: 322, serial: 25
[vo/x11/x11] Error code: 9, request code: 37, minor code: 0
[W][83392.728217] pw.conf  | [  conf.c:  939 try_load_conf()] can't 
load config client.conf: No such file or directory
[E][83392.728272] pw.conf  | [  conf.c:  963 
pw_conf_load_conf_for_context()] can't load default config client.conf: No such 
file or directory
AO: [pulse] 44100Hz mono 1ch float
VO: [x11] 640x480 yuv420p
[vo/x11/x11] X11 error: BadDrawable (invalid Pixmap or Window parameter)
[vo/x11/x11] Type: 0, display: 0x7febb40456b0, resourceid: 8, serial: 29
[vo/x11/x11] Error code: 9, request code: e, minor code: 0
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7febb40456b0, resourceid: 8, serial: 2a
[vo/x11/x11] Error code: 3, request code: 28, minor code: 0
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7febb40456b0, resourceid: 322, serial: 2b
[vo/x11/x11] Error code: 3, request code: c, minor code: 0
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7febb40456b0, resourceid: 322, serial: 2d
[vo/x11/x11] Error code: 3, request code: 12, minor code: 0
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7febb40456b0, resourceid: 322, serial: 2e
[vo/x11/x11] Error code: 3, request code: 2, minor code: 0
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7febb40456b0, resourceid: 322, serial: 2f
[vo/x11/x11] Error code: 3, request code: 2, minor code: 0
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7febb40456b0, resourceid: 322, serial: 30
[vo/x11/x11] Error code: 3, request code: 3, minor code: 0
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7febb40456b0, resourceid: 322, serial: 32
[vo/x11/x11] Error code: 3, request code: 8, minor code: 0
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7febb40456b0, resourceid: 322, serial: 33
[vo/x11/x11] Error code: 3, request code: 12, minor code: 0
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7febb40456b0, resourceid: 322, serial: 36
[vo/x11/x11] Error code: 3, request code: 3, minor code: 0
[vo/x11/x11] X11 error: BadDrawable (invalid Pixmap or Window parameter)
[vo/x11/x11] Type: 0, display: 0x7febb40456b0, resourceid: 8, serial: 38
[vo/x11/x11] Error code: 9, request code: e, minor code: 0
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7febb40456b0, resourceid: 8, serial: 39
[vo/x11/x11] Error code: 3, request code: 28, minor code: 0
INFO_VIDEO_DSIZE=640x480
[vo/x11/x11] X11 error: BadDrawable (invalid Pixmap or Window parameter)
[vo/x11/x11] Type: 0, display: 0x7febb40456b0, resourceid: 322, serial: 3f
[vo/x11/x11] Error code: 9, request code: 82, minor code: 3
[vo/x11/x11] X11 error: BadDrawable (invalid Pixmap or Window parameter)
[vo/x11/x11] Type: 0, display: 0x7febb40456b0, resourceid: 322, serial: 40
[vo/x11/x11] Error code: 9, request code: 82, minor code: 3
MPV_VERSION=mpv 0.35.1
INFO_VIDEO_WIDTH=640
INFO_VIDEO_HEIGHT=480
INFO_VIDEO_ASPECT=1.33
INFO_VIDEO_FPS=30.00
INFO_VIDEO_FORMAT=vp8
INFO_VIDEO_CODEC=vp8 (On2 VP8)
INFO_DEMUX_ROTATION=
INFO_AUDIO_FORMAT=vorbis
INFO_AUDIO_CODEC=vorbis (Vorbis)
INFO_AUDIO_RATE=44100
INFO_AUDIO_NCH=1
INFO_LENGTH=421.60
INFO_DEMUXER=mkv
INFO_SEEKABLE=yes
INFO_TITLES=
INFO_CHAPTERS=0
INFO_TRACKS_COUNT=2
METADATA_TITLE=
METADATA_ARTIST=
METADATA_ALBUM=
METADATA_GENRE=
METADATA_DATE=
METADATA_TRACK=
METADATA_COPYRIGHT=
INFO_MEDIA_TITLE=trever and chris grappling part 3.webm
INFO_STREAM_PATH=/data/pics/videos/trever/trever and chris grappling part 3.webm
[vo/x11] can't keep up! Waiting for XShm completion events...
INFO_TRACK_0: video 1 '' '' yes
INFO_TRACK_1: audio 1 '' '' yes
Exiting... (Quit)
=
End of log

-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/6 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages smplayer depends on:
ii  libc6   2.36-9
ii  libgcc-s1   12.2.0-14
ii  libqt5core5a5.15.8+dfsg-11
ii  libqt5dbus5 5.15.8+dfsg-11
ii  libqt5gui5  5.15.8+dfsg-11
ii  libqt5network5  5.15.8+dfsg-11
ii  libqt5widgets5  5.15.8+dfsg-11
ii  libqt5xml5  5.15.8+dfsg-11
ii  libstdc++6  12.2.0-14
ii  libx11-62:1.8.4-2+deb12u1
ii  mpv

Bug#1037998: Re : gost-crypto-dkms: module fails to build for Linux 6.3: error: implicit declaration of function 'crypto_tfm_ctx'

2023-06-16 Thread Francesco C

A google search of 'crypto_tfm_ctx' will show that the declaration of
this function is located in 'include/crypto/algapi.h' in the linux
6.3.x series.

So this is not complicated to solve : it's enough to add '#include
' into the magma_generic.c file , after the '#include
' line.

Bug#1035972: isc-dhcp EOL'ed

2023-06-16 Thread Roberto C . Sánchez

On Wed, May 17, 2023 at 10:50:34AM +0200, Moritz Muehlenhoff wrote:
> 
> My take would be to mark it as unsupported after the trixie development cycle
> has started (this flags awareness, but has no impact on stable releases)
> and then revisit the support situation before the trixie freeze (Kea might be
> a full replacment by then or maybe it turns out the patch support is ensured
> despite upstream's EOL)
> 
Hi Moritz,

Now that bookworm is out and (AFAICT) that the trixie development cycle
has started, are able to go ahead with marking isc-dhcp as unsupported?

Regards,

-Roberto

-- 
Roberto C. Sánchez

Bug#1033829:

2023-06-16 Thread c . buhtz


Hello,

upstream maintainer here.

I just want to inform. I don't know how Debian would handle this 
usually.


The problem is fixed in upstream but unreleased. And this NMU tries to 
backport the fix.
The next Debian release will come in around 2 years. Until then upstream 
will do a new release.


Because of that and to my understanding there is no need anymore for 
that NMU and it can be removed from the system.


Kind
Christian

Bug#963849:

2023-06-16 Thread c . buhtz


Dear Felix,

can you please try to reproduce the problem with a newer release.
Debian 12 now has 1.3.3 on board which is the latest upstream version. 
This version is also available via an Ubuntu PPA or directly via git 
clone.


Feel free to ask if you need further help with installing.

Kind
Christian Buhtz

Bug#940319:

2023-06-16 Thread c . buhtz


Hello,

I try to learn here and that is why I asked.

Do I get it right that the problem is that BIT do write and read from 
the users home folder. And that is not possible or not recommended on 
Debian's own build and test system. Am I right so far?


To my knowledge as upstream maintainer this problem is not solved in 
upstream.


So how do you do it on the Debian side? Does our BIT still write to 
Debians build system's users home folder or not?

If not, how did you solved or worked around it?

Thanks for your reply.

Kind
Christian Buhtz

Bug#1037456: RFP: Publii -- Static CMS for privacy-focused, SEO-optimized websites

2023-06-12 Thread Fernando C. Estrada

Package: wnpp
Severity: wishlist

* Package name: Publii
  Version : 0.42.1
  Upstream Contact: TidyCustoms 
* URL : https://getpublii.com
* License : GPL-3.0
  Programming Lang: JavaScript
  Description : Static CMS for privacy-focused, SEO-optimized websites.

Unlike static-site generators that are often unwieldy and difficult to use,
Publii provides an easy-to-understand UI much like server-based CMSs such as
WordPress or Joomla!, where users can create posts and other site content, and
style their site using a variety of built-in themes and options. Users can
enjoy the benefits of a super-fast and secure static website, with all the
convenience that a CMS provides.

What makes Publii even more unique is that the app runs locally on your desktop
rather than on the site's server. Available for Windows, Mac, Linux once the
app has been installed you can create a site in minutes, even without internet
access; since Publii is a desktop app you can create, update and modify your
site offline, then upload the site changes to your server at the click of a
button. Publii supports multiple upload options, including standard HTTP/HTTPS
servers, Netlify, Amazon S3, GitHub Pages and Google Cloud or SFTP.

--
Fernando C. Estrada

Bug#1036631: procps: [ps] segmentation fault ps:src/ps/display.c:75

2023-05-23 Thread C Seys

Package: procps
Version: 2:4.0.3-1
Severity: important

Dear Maintainer,

Running the command:
# ps -wwlmfjAF

leads to a partial listing along with a segmentation fault message:
  F S 
UID  PIDPPIDPGID SID  C PRI  NI ADDR SZ WCHANRSS PSR 
STIME TTY  TIME CMD
4 - root   1   0   1   1  0   -   - - 42369 -  13784   
- May10 ?00:26:24 /sbin/init
4 S root   -   -   -   -  0 597548028 - - -   - 
597547968 May10 -  00:26:24 -
1 - root   2   0   0   0  0   -   - - 0 -  0   
- May10 ?00:00:01 [kthreadd]
Signal 11 (SEGV) caught by ps (4.0.3).
1 S root   -   -   -   -  0  60   0 - 
-ps:src/ps/display.c:75: please report this bug
Segmentation fault

Thanks for your time!
C.

-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-8-amd64 (SMP w/2 CPU threads; PREEMPT)
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 not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages procps depends on:
ii  init-system-helpers  1.65.2
ii  libc62.36-9
ii  libncursesw6 6.4-4
ii  libproc2-0   2:4.0.3-1
ii  libtinfo66.4-4

Versions of packages procps recommends:
ii  psmisc  23.6-1

procps suggests no packages.

-- no debconf information

Bug#1036630: procps: unowned /usr/bin/ps on filesystem after upgrade to bookworm

2023-05-23 Thread C Seys

Package: procps
Version: 2:4.0.3-1
Severity: normal

Dear Maintainer,

After upgrading to bookworm there is an unowned /usr/bin/ps on the filesystem:

# dpkg -S /usr/bin/ps
dpkg-query: no path found matching pattern /usr/bin/ps

There is also /bin/ps owned by procps:

# dpkg -S /bin/ps
procps: /bin/ps

I wasn't able to find a /usr/bin/ps in on non-upgraded versions of Debian (only 
/bin/ps).

Thanks for your efforts!
C.


-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-8-amd64 (SMP w/2 CPU threads; PREEMPT)
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 not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages procps depends on:
ii  init-system-helpers  1.65.2
ii  libc62.36-9
ii  libncursesw6 6.4-4
ii  libproc2-0   2:4.0.3-1
ii  libtinfo66.4-4

Versions of packages procps recommends:
ii  psmisc  23.6-1

procps suggests no packages.

-- no debconf information

Bug#1033750: glib-networking libproxy fails

2023-03-31 Thread Casey C

Package: glib-networking
Version: 2.74.0-4

An issue with glib-networking causes GStreamer to abort streams.
The "environment-libproxy" test from glib-networking-tests fails:
"$ /usr/libexec/installed-tests/glib-networking/environment-libproxy
# random seed: R02Scaabc7588fed22ec43e9b4138b1e372f
1..3
# Start of proxy tests
# Start of environment tests
ok 1 /proxy/environment/uri
ok 2 /proxy/environment/socks
# child process (/proxy/environment/ignore [2843]) exit status: 1 (error)
# child process (/proxy/environment/ignore [2843]) stdout: ""
# child process (/proxy/environment/ignore [2843]) stderr:
"**\nGLib-Net:ERROR:../proxy/tests/common.c:192:test_proxy_ignore_common:
assertion failed (proxies[0] == ignore_tests[i].proxy): (\"
http://localhost:8080\"; == \"direct://\")\n"
**
GLib-Net:ERROR:../proxy/tests/environment.c:72:test_proxy_ignore: child
process (/proxy/environment/ignore [2843]) failed unexpectedly
Bail out! GLib-Net:ERROR:../proxy/tests/environment.c:72:test_proxy_ignore:
child process (/proxy/environment/ignore [2843]) failed unexpectedly
Aborted"

Other tests complete without error.

Debian GStreamer Bug Report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029618
GStreamer Bug Report:
https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/-/issues/1008

Architecture is powerpc. Running 32-bit userland on 64-bit kernel
(6.0.0-6-powerpc64). Please let me know if I can provide any additional
information.

Bug#1029618: GStreamer & glib-networking

2023-03-31 Thread Casey C

I submitted a bug report to GStreamer about this issue. See
https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/-/issues/1008. The
GStreamer dev that helped out with my bug report found that the fault
originates with libproxy in glib-networking. I ran the
"environment-libproxy" test from glib-networking-tests and the result was:
"$ /usr/libexec/installed-tests/glib-networking/environment-libproxy
# random seed: R02S5b1dc0abfabd6b943121bee035468cde
1..3
# Start of proxy tests
# Start of environment tests
ok 1 /proxy/environment/uri
ok 2 /proxy/environment/socks
# child process (/proxy/environment/ignore [2067]) exit status: 1 (error)
# child process (/proxy/environment/ignore [2067]) stdout: ""
# child process (/proxy/environment/ignore [2067]) stderr:
"**\nGLib-Net:ERROR:../proxy/tests/common.c:192:test_proxy_ignore_common:
assertion failed (proxies[0] == ignore_tests[i].proxy): (\"
http://localhost:8080\"; == \"direct://\")\n"
**
GLib-Net:ERROR:../proxy/tests/environment.c:72:test_proxy_ignore: child
process (/proxy/environment/ignore [2067]) failed unexpectedly
Bail out! GLib-Net:ERROR:../proxy/tests/environment.c:72:test_proxy_ignore:
child process (/proxy/environment/ignore [2067]) failed unexpectedly
Aborted"

The rest of the glib-networking tests complete without errors. I will
submit a bug report for glib-networking.

Bug#998105:

2023-03-29 Thread c . buhtz


Do I see it correct that the commit was done but not yet uploaded?

In result there should be a 1.3.3-5, right?

Bug#940319:

2023-03-17 Thread c . buhtz


Dear Jonathan,
what is the current situation about that issue?

There where some new releases of Back In Time in Debian. Do you 
workaround that problem on your Debian side? And how?


Kind
Christian

Bug#859115:

2023-03-17 Thread c . buhtz


Initial report based on a very old version of Back In Time.
No feedback from reporter.
Not able to reproduce.

Bug#1030726: marked as pending in intelrdfpmath

2023-02-13 Thread Roberto C . Sánchez

On Sun, Feb 12, 2023 at 09:32:55PM +0100, Stephen Kitt wrote:
> 
> Given how late we are in the Bookworm release process, I’ve updated the
> package description to mention that the library is only fully functional on
> x86 architectures and ia64, but may be sufficient on others (for free42, it
> is, at least on ARM), and haven’t restricted the architectures. That doesn’t
> help on MIPS of course...
> 
> Does libdfp work on MIPS? I got the impression it’s mainly supported on IBM
> platforms (POWER and S/390) but perhaps that’s outdated!
> 
After having talked with the developer who has implemented the new
DFP-dependent features in libmongocrypt, it seems that portability
(beyond amd64, arm64, ppc64el, and s390x) was in view for him.  He did
look at libdfp and concluded that it has some benefits over Intel DFP,
but clearly building on MIPS family architectures is not achievable even
with libdfp.

As far as it being outdated, I am not certain but I think that upstream
might have gone away from tagged/versioned releases and more to a model
of "clone master and build from that".  In that sense, it wouldn't be
outdated, but the version in Debian would be about ~18 months out of
date by that measure.

In any event, upstream decided that rather than implement support for
libdfp they would implement a switch to enable/disable building with
Intel DFP (and thus the features that depend on it).  That will allow
for libmongocrypt to be able to build on all of the release
architectures for bookworm.  That new upstream release is due out today
or tomorrow.

The upstream CI gives sufficient coverage with testing that I am
confident in all the 64-bit non-MIPS arches and I would be surprised if
32-bit ARM were an issue given the fairly robust upstream tests.

In any event, thanks for leaving the architectures as they are for the
moment.

Regards,

-Roberto
-- 
Roberto C. Sánchez

Bug#1030726: marked as pending in intelrdfpmath

2023-02-07 Thread Roberto C . Sánchez

On Tue, Feb 07, 2023 at 08:44:50PM +0100, Stephen Kitt wrote:
> 
> Yes, it seems like we’d really need a mips_macros.h implementation on MIPS.
> 
That was my suspicion as well.

> I enabled the test suite, and the result is basically that the library only
> works fully on amd64, i386 (nearly, with two test failures out of ~120,000
> test cases), and ia64, which matches the architectures which the library
> claims to support. On other architectures, the number of failures varies, up
> to 12.5% of test cases on s390x.
> 
> So really I should change the library to [amd64 i386 ia64]...
> 
That's unfortunate.

> Do you have a good way of validating whether the library is good enough for
> libmongocrypt’s purposes on non-Intel architectures?
> 
libmonogocrypt has a test suite, which we don't execute as part of the
package build because of upstream's robust CI.  However, we could
definitely enable it and it would be sufficient to let us know that the
library is adequate for what libmongocrypt needs.

That said, upstream is quite close validating that libmongocrypt works
with libdfp, so that might provide a near-term alternative if you decide
that the best thing to do from a quality perspective is to restrict the
architecture list of intelrdfpmath.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Bug#1030726: marked as pending in intelrdfpmath

2023-02-06 Thread Roberto C . Sánchez

And even with the build continuing on mips64el I see this:

float128/dpml_ux_trig.c: In function '__dpml_bid_ux_degree_reduce__':
float128/dpml_ux_trig.c:254:9: warning: implicit declaration of function 
'UMULH' [-Wimplicit-f
unction-declaration]
  254 | UMULH((UX_FRACTION_DIGIT_TYPE) exponent, RECIP_TWELVE, k);
  | ^


When I build libmongocrypt against the resulting libintelrdfp-math, the
libmongocrypt will then fail at link time:

/usr/bin/ld: 
/home/roberto/mips64el/intelrdfpmath-2.0u2/debian/libintelrdfpmath-dev/usr/lib/mips64el-linux-gnuabi64/libbidgcc000.a(dpml_ux_ops_64.o):
 in function `__eval_pos_poly':
(.text+0xe4): undefined reference to `UMULH'
/usr/bin/ld: (.text+0xfc): undefined reference to `UMULH'
/usr/bin/ld: (.text+0x144): undefined reference to `UMULH'
/usr/bin/ld: (.text+0x160): undefined reference to `UMULH'
/usr/bin/ld: (.text+0x168): undefined reference to `UMULH'
/usr/bin/ld: 
/home/roberto/mips64el/intelrdfpmath-2.0u2/debian/libintelrdfpmath-dev/usr/lib/mips64el-linux-gnuabi64/libbidgcc000.a(dpml_ux_ops_64.o):(.text+0x17c):
 more undefined references to `UMULH' follow

It might be better to simply declare intelrdfpmath '[!mipsel
!mips64el]'.  Sadly, my experience with Intel libraries (I maintained
TBB in Debian for several years) is that they only put effort into the
architectures that are important to them and that you can't assume that
their code will work on other architectures.  That could well be the
case here.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Bug#1030726: marked as pending in intelrdfpmath

2023-02-06 Thread Roberto C . Sánchez

This patch is broken.  I attempted a build and this is what happened:

(sid_mips64el-dchroot)roberto@eller:~/mips64el/intelrdfpmath-2.0u2$ 
dpkg-buildpackage
dpkg-buildpackage: info: source package intelrdfpmath
dpkg-buildpackage: info: source version 2.0u2-6
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Stephen Kitt 
dpkg-buildpackage: info: host architecture mips64el
 dpkg-source --before-build .
 debian/rules clean
dh clean
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/home/roberto/mips64el/intelrdfpmath-2.0u2'
/usr/bin/make -C LIBRARY clean
make[2]: Entering directory '/home/roberto/mips64el/intelrdfpmath-2.0u2/LIBRARY'
makefile.iml_head:356: *** Unknown host architecture mips64.  Stop.
make[2]: Leaving directory '/home/roberto/mips64el/intelrdfpmath-2.0u2/LIBRARY'
make[1]: *** [debian/rules:16: override_dh_auto_clean] Error 2
make[1]: Leaving directory '/home/roberto/mips64el/intelrdfpmath-2.0u2'
make: *** [debian/rules:13: clean] Error 2
dpkg-buildpackage: error: debian/rules clean subprocess returned exit status 2

I have attached an updated patch that seems to resolve this issue and
allows the build to execute on mips64el and mipsel.

Regards,

-Roberto

On Mon, Feb 06, 2023 at 08:58:44PM +, Stephen Kitt wrote:
> Control: tag -1 pending
> 
> Hello,
> 
> Bug #1030726 in intelrdfpmath reported by you has been fixed in the
> Git repository and is awaiting an upload. You can see the commit
> message below and you can check the diff of the fix at:
> 
> https://salsa.debian.org/debian/intelrdfpmath/-/commit/758574be1ed3ce30ec26c6e5136fdb1691d5213a
> 
> 
> Fix MIPS support
> 
> Closes: #1030726
> 
> 
> (this message was generated automatically)
> -- 
> Greetings
> 
> https://bugs.debian.org/1030726
> 
> -- 
> To unsubscribe, send mail to 1030726-unsubscr...@bugs.debian.org.

-- 
Roberto C. Sánchez
Description: Fix MIPS support
Author: Stephen Kitt 

This removes references to files which aren't shipped, and adds
support for 64-bit MIPS.

Based on a patch by Roberto Sánchez .

Index: intelrdfpmath-2.0u2/LIBRARY/float128/architecture.h
===
--- intelrdfpmath-2.0u2.orig/LIBRARY/float128/architecture.h
+++ intelrdfpmath-2.0u2/LIBRARY/float128/architecture.h
@@ -128,14 +128,22 @@
 #	undef  MULTIPLE_ISSUE
 #	undef  UNSIGNED_TO_FLOAT
 #	define UNSIGNED_MULTIPLY 1
-#	define ENDIANESS little_endian
+#	if defined(_MIPSEL)
+#		define ENDIANESS little_endian
+#	elif defined(_MIPSEB)
+#		define ENDIANESS big_endian
+#	endif
 #	define SCALE_METHOD by_int
 #	define CVT_TO_HI_LO_METHOD by_flt

 #	define BITS_PER_CHAR8
 #	define BITS_PER_SHORT  16
 #	define BITS_PER_INT32
-#	define BITS_PER_LONG   32
+#	if (_MIPS_SIM == _ABIO32) || (_MIPS_SIM == _ABIN32)
+#		define BITS_PER_LONG   32
+#	elif _MIPS_SIM == _ABI64
+#		define BITS_PER_LONG   64
+#	endif

 #	define BITS_PER_FLOAT  32
 #	define BITS_PER_DOUBLE 64
@@ -144,22 +152,31 @@
 #	define INT_8  signed char
 #	define INT_16 signed short
 #	define INT_32 signed int
-#	undef  INT_64
+#	define INT_64 long long
 #	undef  INT_128
 #	define U_INT_8  unsigned char
 #	define U_INT_16 unsigned short
 #	define U_INT_32 unsigned int
-#	undef  U_INT_64
+#	define U_INT_64 unsigned long long
 #	undef  U_INT_128

-#	define WORD  INT_32
-#	define U_WORD  U_INT_32
-#	define BITS_PER_WORD 32
-
-#	define HALF_WORD  INT_16
-#	define U_HALF_WORD  U_INT_16
-#	define BITS_PER_HALF_WORD 16
-
+#	if (_MIPS_SIM == _ABIO32) || (_MIPS_SIM == _ABIN32)
+#		define WORD  INT_32
+#		define U_WORD  U_INT_32
+#		define BITS_PER_WORD 32
+
+#		define HALF_WORD  INT_16
+#		define U_HALF_WORD  U_INT_16
+#		define BITS_PER_HALF_WORD 16
+#	elif _MIPS_SIM == _ABI64
+#		define WORD  INT_64
+#		define U_WORD  U_INT_64
+#		define BITS_PER_WORD 64
+
+#		define HALF_WORD  INT_32
+#		define U_HALF_WORD  U_INT_32
+#		define BITS_PER_HALF_WORD 32
+#	endif

 #elif (defined(hp_pa) || defined(HP_PA) || defined(__hppa) || defined(__HPPA))
Index: intelrdfpmath-2.0u2/LIBRARY/float128/dpml_exception.h
===
--- intelrdfpmath-2.0u2.orig/LIBRARY/float128/dpml_exception.h
+++ intelrdfpmath-2.0u2/LIBRARY/float128/dpml_exception.h
@@ -325,7 +325,6 @@ typedef struct {
 #	define PROCESS_DENORMS 1
 #	define DPML_EXCEPTION_HANDLER DPML_EXCEPTION_NAME
 #	define EXCEPTION_ARGUMENTS( error_code ) error_code
-#	define PLATFORM_SPECIFIC_HEADER_FILE "mips_exception.c"

 #   elif ARCHITECTURE == hp_pa
 #	define PROCESS_DENORMS 1
Index: intelrdfpmath-2.0u2/LIBRARY/float128/dpml_private.h
==

Bug#1030726: marked as pending in intelrdfpmath

2023-02-06 Thread Roberto C . Sánchez

As a further note, even with the update patch that I supplied, there is
still a later failure on 32-bit mipsel:

float128/dpml_ux_cbrt.c: In function 'bid_f128_cbrt':
float128/dpml_ux_cbrt.c:136:27: error: 'lsd' undeclared (first use in this 
function); did you mean 'msd'?
  136 || (lsd >> D_EXP_WIDTH);
  |   ^~~
  |   msd
float128/dpml_ux_cbrt.c:136:27: note: each undeclared identifier is reported 
only once for each function it appears in

Regards,

-Roberto

-- 
Roberto C. Sánchez

1 2 3 4 5 6 7 8 9 10 >

1 - 100 of 1686 matches

Mail list logo