Bug#1067569: RFS: libsmb2/4.0.0-1 [ITP]-- SMB2/3 client library

2024-08-14 Thread Joe Mondloch
On Aug 6, 2024, at 7:33 AM, Phil Wyett  wrote:
> 
> On Sat, 6 Apr 2024 00:42:04 +0500 Andrey Rakhmatullin 
> wrote:
>> Control: tags -1 + moreinfo
>> 
>> You should provide a separate -dev package, currently the development
>> files are shipped in the library package.
>> There is a hardcoded Depends: libkrb5-3, why is this needed?
>> There are unused files in debian/, such as libsmb2-dev.* and libsmb21.*.
>> You should remove the .la file instead of fixing it, unless something
>> needs it.
>> You shouldn't call dh_installexamples in override_dh_install.
>> 
>> Please remove the moreinfo tag after these are addressed.
>> 
>> 
>> -- 
>> WBR, wRAR
> 
> Hi Joe,
> 
> It has now bee some time with no updates or feedback from you as the
> submitter to the reuest for more information by Andrey. Is there still
> motivation to move forward getting this package ready and into
> Debian?
> 
> Regards
> 
> Phil


Hi Phil,

Yes, I do believe there is benefit to having libsmb2 in Debian. It’d allow me 
to release a new version of Medusa which now has a dependency on the library. 
I’ll revisit the requests.

Joe



Bug#1075771: kanboard: Kanboard is throwing an exception in EventDispatcher while trying to logout

2024-07-23 Thread Joe Nahmias
On Tue, Jul 23, 2024 at 08:17:12PM +0900, Carsten Schoenert wrote:
> Hello Joe,
Hi Carsten,

> I tried to reach you but your eamil system seems to not accept emails at
> least from my side.
> 
> ---%<---
> This message was created automatically by mail delivery software.
> 
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
> 
>   j...@nahmias.net
> host skippy.nahmias.net [162.243.209.86]
> retry timeout exceeded
> 
> 
> Reporting-MTA: dns; mitropoulos.debian.org
> 
> Action: failed
> Final-Recipient: rfc822;j...@nahmias.net
> Status: 5.0.0
> Remote-MTA: dns; skippy.nahmias.net
> --->%---

That's quite odd. I've been receiving mail from bendel.d.o quite
consistently for the past 48+ hours. If you can send more details, I'd be
happy to troubleshoot

> I was asking if you are fine if I work together with Kalyani on fixing
> the current outstanding CVE issues together with this issue and finalize
> a upload to s-propused-updates.

Sure, no issues on my end -- that's why I'm on LowThresholdNMU list and I
put the code on Salsa in the debian namespace. I just ask that you keep
the repo on salsa current with any changes. I use gbp with pristine-tar
and the standard DEP-14 branch structure.

> I'll wait for some days before going to work on this.

Much appreciated,

> Regards
> Carsten

--Joe

> Am Thu, Jul 04, 2024 at 11:43:30PM +0530 schrieb Kalyani Kenekar:
> > Package: kanboard
> > Severity: important
> > Tags: upstream
> > 
> > Dear Maintainer,
> > 
> > If I am trying to logout from the kanboard UI, I am not able to logout 
> > because
> > I am getting a "HTTP ERROR 500".
> > 
> > When I look into the error log of my webserver (nginx) I see the following
> > stack trace:
> > 
> > Stack trace:
> > #0 /usr/share/kanboard/app/Core/Session/SessionManager.php(62): 
> > Symfony\Component\EventDispatcher\EventDispatcher->dispatch()
> > #1 /usr/share/kanboard/app/Controller/AuthController.php(61): 
> > Kanboard\Core\Session\SessionManager->close()
> > #2 /usr/share/kanboard/app/Core/Controller/Runner.php(77): 
> > Kanboard\Controller\AuthController->logout()
> > #3 /usr/share/kanboard/app/Core/Controller/Runner.php(31): 
> > Kanboard\Core\Controller\Runner->executeController()
> > #4 /usr/share/kanboard/index.php(9): 
> > Kanboard\Core\Controller\Runner->execute()
> > #5 {main}
> >   thrown in 
> > /usr/share/php/Symfony/Component/EventDispatcher/EventDispatcher.php on 
> > line 48" while reading response header from upstream, client: 
> > 192.168.122.1, server: kanboard, request: "GET /logout HTTP/1.1", upstream: 
> > "fastcgi://unix:/var/run/php/php-fpm.sock:", host: "kanboard"
> > 2024/07/04 20:22:17 [error] 2890#2890: *59 FastCGI sent in stderr: "PHP 
> > message: PHP Fatal error:  Uncaught TypeError: 
> > Symfony\Component\EventDispatcher\EventDispatcher::dispatch(): Argument #1 
> > ($event) must be of type object, string given, called in 
> > /usr/share/kanboard/app/Core/Session/SessionManager.php on line 62 and 
> > defined in 
> > /usr/share/php/Symfony/Component/EventDispatcher/EventDispatcher.php:48
> > 
> > 
> > This is known bug it was fixed in upstream version 1.2.32.
> > The PR 5309 in detail was fixing this issue: 
> > https://github.com/kanboard/kanboard/pull/5309/files
> > 
> > 
> > -- System Information:
> > Debian Release: bookworm/sid
> >   APT prefers jammy-updates
> >   APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 
> > 'jammy'), (100, 'jammy-backports')
> > Architecture: amd64 (x86_64)
> > Foreign Architectures: i386
> > 
> > Kernel: Linux 6.5.0-41-generic (SMP w/4 CPU threads; PREEMPT)
> > Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en
> > Shell: /bin/sh linked to /usr/bin/dash
> > Init: systemd (via /run/systemd/system)
> > LSM: AppArmor: enabled
> 



Bug#1075811: autokey-qt can be installed but will nor run

2024-07-05 Thread Joe
Package: autokey-qt
Version: 0.95.10-2.1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Autokey is loaded on login, but not always used. Today I found it did
not function, and had not been loaded. I believe it has been used
within the last three weeks.

Installing autokey-qt after purging autokey-qt and autokey-common
appears to work normally, no errors are shown.
Running it from the GUI menu does nothing, running from the terminal
produces these python errors:

joe@jrenewsid:~$ autokey-qt
Traceback (most recent call last):
  File "/usr/bin/autokey-qt", line 33, in 
sys.exit(load_entry_point('autokey==0.95.10', 'console_scripts',
'autokey- qt')())
^
  File "/usr/bin/autokey-qt", line 25, in importlib_load_entry_point
return next(matches).load()
   
  File "/usr/lib/python3.12/importlib/metadata/__init__.py", line 205,
in load module = import_module(match.group('module'))
 
  File "/usr/lib/python3.12/importlib/__init__.py", line 90, in
import_module return _bootstrap._gcd_import(name[level:], package,
level) 
  File "", line 1387, in _gcd_import
  File "", line 1360, in _find_and_load
  File "", line 1331, in
_find_and_load_unlocked File "", line 935,
in _load_unlocked File "", line
995, in exec_module File "", line 488, in
_call_with_frames_removed File
"/usr/lib/python3/dist-packages/autokey/qtui/__main__.py", line 23, in
 from autokey.qtapp import Application
  File "/usr/lib/python3/dist-packages/autokey/qtapp.py", line 37, in
 from autokey import service, monitor
  File "/usr/lib/python3/dist-packages/autokey/monitor.py", line 24, in

from pyinotify import WatchManager, Notifier, EventsCodes,
ProcessEvent File "/usr/lib/python3/dist-packages/pyinotify.py", line
71, in  import asyncore
ModuleNotFoundError: No module named 'asyncore'



It appears the asyncore module has been deprecated and removed from
python. I have tried autokey-gtk but it also uses asyncore.
I can find no Debian bug reports for autokey-qt, possibly there are not
many users.

Is there a workaround?


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

Kernel: Linux 6.9.7-amd64 (SMP w/4 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 autokey-qt depends on:
ii  autokey-common   0.95.10-2.1
ii  python3  3.12.2-1
ii  python3-pyqt55.15.10+dfsg-1+b3
ii  python3-pyqt5.qsci   2.14.1+dfsg-1+b3
ii  python3-pyqt5.qtsvg  5.15.10+dfsg-1+b3

autokey-qt recommends no packages.

Versions of packages autokey-qt suggests:
pn  gnome-shell-extension-appindicator  

-- no debconf information

Best regards,
Joe



Bug#1061519: shim 15.8-1~deb12u1 missing

2024-06-18 Thread Joe Groocock
Hi,

We've been awaiting the patched build of shim/shim-unsigned to appear in
bookworm, but despite this commit last month, only the buster package seems
to be available in the repos still
https://salsa.debian.org/efi-team/shim/-/commit/9047a8e8ec4d769b2cb405d109270639096dbde7
Is this expected? Do we know when the patched package might be available?

Thanks, and regards,

*Joe Groocock*  |  System Reliability Engineer
jgrooc...@cloudflare.com
FF8B 8059 B7FA 3FD4 3C05 CB99 0657 91BB A2C6 56A6
<https://pgp.mit.edu/pks/lookup?op=get&search=0xFF8B8059B7FA3FD43C05CB99065791BBA2C656A6>
<https://www.cloudflare.com/>

1 888 99 FLARE  |  www.cloudflare.com


Bug#1025825: More information on bug

2024-05-15 Thread Joe Pfeiffer
See this discussion, including a patch, on google groups:
https://groups.google.com/g/linux.debian.bugs.dist/c/FzL7OUmy8jw
-- 



Bug#1068113: ITP: libsmb2 -- SMB2/3 client library

2024-03-30 Thread Joe Mondloch
ITP: libsmb2 -- SMB2/3 client library
Package: wnpp
Severity: wishlist
Owner: Joe Mondloch 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: libsmb2
  Version : 4.0.0
  Upstream Authors: Ronnie Sahlberg 
  URL : https://github.com/sahlberg/libsmb2
* License : LGPL-2.1+
  Description : SMB2/3 client library
 Libsmb2 is a userspace client library for accessing SMB2/SMB3 shares on a
 network. It is high performance and fully async. It supports both zero-copy
 for SMB READ/WRITE commands as well as compounded commands.



Bug#987227: php-defaults: Consider changing php sapi dependency order

2024-03-27 Thread Joe Cooper
Is there some way to get some movement on making this change?

mod_php has been discouraged for well over a decade by the PHP project
developers. It has security implications (applications run as www-data
instead of a less privileged user), it has a performance and memory-usage
cost, and increased attack surface, even if the user isn't using it to run
PHP applications (it is loaded by default by configuration in
/etc/apache2/mods-enabled/php8.2.load when installed). There's no reason to
ever prefer mod_php, so the default here is guiding users in a bad
direction on multiple fronts (security, performance, and memory usage).

Installing mod_php also prevents configuring http2 in Apache, because it
depends on mpm_prefork.

Upstream recommends FPM and strongly discourages mod_php, so the package
should prefer FPM. Merely changing the order of dependencies to put fpm
first, would resolve this problem.

Is there anything blocking this change, or has it just not gotten the
attention of the right folks?

On Mon, 19 Apr 2021 15:43:32 -0600 Jesse Rhodes  wrote:
> Source: php-defaults
> Severity: wishlist
> X-Debbugs-Cc: je...@sney.ca
>
> Dear Maintainer,
>
> The top-level versioned php metapackage (php7.4 at the time of writing)
has the following Depends field:
>
> Depends: libapache2-mod-php7.4 | php7.4-fpm | php7.4-cgi, php7.4-common
>
> Thus, a user who runs 'apt install php' will get libapache2-mod-php7.4,
along with apache2 itself.
>
> Apache upstream considers prefork to be specific to "sites requiring
stability or compatibility with older software"[1]. And in the modern era,
best practices for hosting websites with dynamic content include using
either a threaded MPM in apache, or a different httpd such as nginx.
>
> Because of this, it seems that libapache2-mod-php is no longer a sane
default when installing php. It makes sense to keep it available, both for
the legacy reasons cited above and for environments like a low traffic
application that requires apache features, but it should not be the first
choice of sapi to install.
>
> Please consider making this change.
>
> Thanks,
>
> Jesse (sney)
>
> [1] https://httpd.apache.org/docs/2.4/en/mpm.html
>
> -- System Information:
> Debian Release: bullseye/sid
> APT prefers testing
> APT policy: (990, 'testing'), (500, 'testing-security'), (500,
'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.10.0-6-amd64 (SMP w/8 CPU threads)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
> Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8),
LANGUAGE=en_CA:en
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
>


Bug#1067569: RFS: libsmb2/4.0.0-1 [ITP]-- SMB2/3 client library

2024-03-23 Thread Joe Mondloch
Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

Dear mentors,

I am looking for a sponsor for my package “libsmb2":

* Package name : libsmb2
   Version  : 4.0.0-1
   Upstream contact : Ronnie Sahlberg https://github.com/sahlberg/libsmb2
* License  : LGPL-2.1+
* Vcs  : https://mentors.debian.net/package/libsmb2/
   Section  : libs

The source builds the following binary packages:

  libsmb2 - SMB2/3 client library

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/libs/libsmb2/libsmb2_4.0.0-1.dsc

Changes since the last upload:

Regards,
Joe


Bug#1061124: lmms-vst-server:i386 plug-in not compatible with lmms:amd64

2024-01-18 Thread Joe
Package: lmms-vst-server
Version: 1.2.2+dfsg1-6
Severity: important
X-Debbugs-Cc: shanny...@yahoo.fr

Dear Maintainer,
loading and running VST is an important part of a music software, unfortunately
it seems impossible on the 64-bit version of LMMS due to architecture
incompatibility between the software and the plug-in provided by the package
lmms-vst-server, which just wouldn't show up in LLMS.

An incompatibility I wasn't initially aware off and online search only had
everyone recommending to use the appimage version.

Uninstalling the amd64 version and installing the i386 allowed both LMMS and
the VeSTige plug-in to work properly. I don't think most amd64 users people
think of that.

Until a amd64 compatible plug-in is released you might want to add a note to
lmms-vst-server's package description that it isn't compatible with lmms:amd64
and VST support is only available for lmms:i386 .

Best regards. -Joe


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

Kernel: Linux 6.1.0-17-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 lmms-vst-server depends on:
ii  libc6 2.36-9+deb12u3
ii  libqt5core5a [qtbase-abi-5-15-8]  5.15.8+dfsg-11
ii  libqt5gui55.15.8+dfsg-11
ii  libqt5widgets55.15.8+dfsg-11
ii  libqt5x11extras5  5.15.8-2
ii  libqt5xml55.15.8+dfsg-11
ii  libstdc++612.2.0-14
ii  libx11-6  2:1.8.4-2+deb12u2
ii  libxcb1   1.15-1
ii  wine [wine]   8.0~repack-4
ii  wine328.0~repack-4

Versions of packages lmms-vst-server recommends:
ii  lmms  1.2.2+dfsg1-6

lmms-vst-server suggests no packages.

-- no debconf information



Bug#1057920: libasound2: segmentation violation playing sound using ALC272 sound card

2023-12-10 Thread Joe Pfeiffer
Package: libasound2
Version: 1.2.10-1
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

I'm getting a segmentation violation attempting to play sound with libasound2 
1.2.10-1.  Reverting to 1.2.8-1+b1 fixes it.
More information about my configuration:
% aplay -l
 List of PLAYBACK Hardware Devices 
card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

% aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
lavrate
Rate Converter Plugin Using Libav/FFmpeg Library
samplerate
Rate Converter Plugin Using Samplerate Library
speexrate
Rate Converter Plugin Using Speex Resampler
jack
JACK Audio Connection Kit
oss
Open Sound System
pulse
PulseAudio Sound Server
speex
Plugin using Speex DSP (resample, agc, denoise, echo, dereverb)
upmix
Plugin for channel upmix (4,6,8)
vdownmix
Plugin for channel downmix (stereo) with a simple spacialization
soft0
soft1
soft2
soft3
hw:CARD=Intel,DEV=0
HDA Intel, ALC272 Analog
Direct hardware device without any conversions
plughw:CARD=Intel,DEV=0
HDA Intel, ALC272 Analog
Hardware device with all software conversions
default:CARD=Intel
HDA Intel, ALC272 Analog
Default Audio Device
sysdefault:CARD=Intel
HDA Intel, ALC272 Analog
Default Audio Device
front:CARD=Intel,DEV=0
HDA Intel, ALC272 Analog
Front output / input
surround21:CARD=Intel,DEV=0
HDA Intel, ALC272 Analog
2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=Intel,DEV=0
HDA Intel, ALC272 Analog
4.0 Surround output to Front and Rear speakers
surround41:CARD=Intel,DEV=0
HDA Intel, ALC272 Analog
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=Intel,DEV=0
HDA Intel, ALC272 Analog
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=Intel,DEV=0
HDA Intel, ALC272 Analog
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=Intel,DEV=0
HDA Intel, ALC272 Analog
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
dmix:CARD=Intel,DEV=0
HDA Intel, ALC272 Analog
Direct sample mixing device
usbstream:CARD=Intel
HDA Intel
USB Stream Output

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


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (700, 'testing'), (650, 'stable'), (600, 'unstable'), (550, 
'experimental'), (500, 'oldstable')
Architecture: i386 (i686)

Kernel: Linux 6.5.0-5-686-pae (SMP w/2 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 libasound2 depends on:
ii  libasound2-data  1.2.10-1
ii  libc62.37-12

libasound2 recommends no packages.

Versions of packages libasound2 suggests:
ii  libasound2-plugins  1.2.7.1-1+b1

-- no debconf information



Bug#1056597: ffmpeg: drawtext filter missing from ffmpeg binaries

2023-11-23 Thread Slim Joe
Package: ffmpeg
Version: 7:6.1-4
Severity: normal

Dear Maintainer,

The FFmpeg binaries (i.e. ffplay and ffmpeg) no longer
provides the drawtext filter, useful for embedding text (such
as subtitles and time codes) into a video.

Here's a simple test command using a legally available video.

$ ffplay -i 
https://static.fsf.org/nosvn/videos/escape-to-freedom/videos/escape-to-freedom-720p.webm
 -vf "drawtext=x=20:y=20:fontsize=24:fontcolor=gold:text='%{localtime \: %T 
%Z%n(%F)}'"

The relevant portion of stderr from this command is this:

[AVFilterGraph @ 0x7f6ae4003e40] No such filter: 'drawtext'
[AVFilterGraph @ 0x7f6ae4003e40] Error processing filtergraph: Filter not found

A shallow search for a similar bug turns up the following link
from the ArchLinux bug tracker ("drawtext filter not available",
dated "Wednesday, 22 November 2023, 15:17 GMT"):

https://bugs.archlinux.org/task/80327

The recommended solution is to recompile FFmpeg with the
"--enable-libharfbuzz" option. There is a libharfbuzz-dev
package in Debian, so this should not be a problem (assuming
the ArchLinux bug report is correct).

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (900, 'testing'), (90, 'unstable')
Architecture: amd64 (x86_64)

Versions of packages ffmpeg depends on:
ii  libavcodec607:6.1-3
ii  libavdevice60   7:6.1-3
ii  libavfilter97:6.1-3
ii  libavformat60   7:6.1-3
ii  libavutil58 7:6.1-3
ii  libc6   2.37-12
ii  libpostproc57   7:6.1-3
ii  libsdl2-2.0-0   2.28.5+dfsg-2
ii  libswresample4  7:6.1-3
ii  libswscale7 7:6.1-3



Bug#1056321: elogind conflicts with same version libelogind0

2023-11-20 Thread Slim Joe
Package: elogind
Version: 246.10-1debian1
Severity: normal

Dear Maintainer,

The systemd alternative, elogind, appears to conflict with its apparent support 
library (libelogind0). Is this a packaging oversight? Or this part of a plan to 
eventually deprecate elogind as an install option?

Below is a prettifed shell output showing the conflict between the version of 
elogind vs. libelogind in Testing (also Unstable).

$ apt show elogind/testing libelogind0/testing | grep -E 
'^(Package|Version|Depend|Conflicts)' 

Package: elogind
Version: 252.9-1debian2
Depends: libacl1 (>= 2.2.23), libc6 (>= 2.34), libcap2 (>= 1:2.10), libmount1 
(>= 2.19.1), libpam0g (>= 0.99.7.1), libselinux1 (>= 3.1~), libudev1, 
libsystemd0, dbus (>= 1.9.14)
Conflicts: libelogind0, systemd

Package: libelogind0
Version: 252.9-1debian2
Depends: libc6 (>= 2.34), libcap2 (>= 1:2.10)
Conflicts: libsystemd0, systemd

A casual look at the Conflicts field for "elogind" suggests
a possible fix. Maybe you could add a "versioned" conflict
for libelogind, something like: libelogind (>= xxx.xx)?

If elogind is to be phased out, maybe an appropriate notice
should be posted and perhaps a transitional dummy package
should be made?

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (900, 'testing'), (90, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.4.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages elogind depends on:
ii  dbus   1.14.10-3
ii  debconf1.5.82
ii  init-system-helpers1.65.2
ii  libacl12.3.1-3
ii  libc6  2.37-12
ii  libcap21:2.66-4
ii  libelogind0246.10-1debian1
ii  libpam0g   1.5.2-9.1
ii  libselinux13.5-1
ii  libudev1   254.5-1
ii  lsb-base   11.6
ii  sysvinit-utils [lsb-base]  3.08-3

Versions of packages elogind recommends:
ii  libpam-elogind  246.10-1debian1
pn  polkitd 

elogind suggests no packages.

-- no debconf information



Bug#1040265: fixing CVE-2023-36813 in kanboard/bookworm

2023-07-15 Thread Joe Nahmias
On Fri, Jul 14, 2023 at 11:47:18PM +0200, Moritz Mühlenhoff wrote:
> Am Wed, Jul 12, 2023 at 08:32:56PM -0400 schrieb Joe Nahmias:
> > Please see attached proposed debdiff for fixing CVE-2023-36813 in bookworm.
> > 
> > --Joe
> 
> > diff -Nru kanboard-1.2.26+ds/debian/changelog 
> > kanboard-1.2.26+ds/debian/changelog
> > --- kanboard-1.2.26+ds/debian/changelog 2023-06-15 23:02:33.0 
> > -0400
> > +++ kanboard-1.2.26+ds/debian/changelog 2023-07-12 20:13:20.0 
> > -0400
> > @@ -1,3 +1,13 @@
> > +kanboard (1.2.26+ds-2+deb12u2) bookworm; urgency=high
>   
> 
> This should be bookworm-security, with that change please upload to 
> security-master,
> I'll take care of the DSA.

Done.

> Cheers,
> Moritz
--Joe



Bug#1040265: fixing CVE-2023-36813 in kanboard/bookworm

2023-07-12 Thread Joe Nahmias
Please see attached proposed debdiff for fixing CVE-2023-36813 in bookworm.

--Joe
diff -Nru kanboard-1.2.26+ds/debian/changelog kanboard-1.2.26+ds/debian/changelog
--- kanboard-1.2.26+ds/debian/changelog	2023-06-15 23:02:33.0 -0400
+++ kanboard-1.2.26+ds/debian/changelog	2023-07-12 20:13:20.0 -0400
@@ -1,3 +1,13 @@
+kanboard (1.2.26+ds-2+deb12u2) bookworm; urgency=high
+
+  * backport fix for CVE-2023-36813: Multiple Authenticated SQL Injections
+https://github.com/kanboard/kanboard/security/advisories/GHSA-9gvq-78jp-jxcx
+Fix picked from kanboard v1.2.31
+https://github.com/kanboard/kanboard/commit/25b93343baeaf8ad
+(Closes: #1040265)
+
+ -- Joseph Nahmias   Wed, 12 Jul 2023 20:13:20 -0400
+
 kanboard (1.2.26+ds-2+deb12u1) bookworm; urgency=high
 
   * Cherry-pick security fixes from kanboard_1.2.26+ds-[34] for bookworm.
diff -Nru kanboard-1.2.26+ds/debian/patches/CVE-2023-36813.patch kanboard-1.2.26+ds/debian/patches/CVE-2023-36813.patch
--- kanboard-1.2.26+ds/debian/patches/CVE-2023-36813.patch	1969-12-31 19:00:00.0 -0500
+++ kanboard-1.2.26+ds/debian/patches/CVE-2023-36813.patch	2023-07-12 19:58:45.0 -0400
@@ -0,0 +1,34 @@
+From 25b93343baeaf8ad018dcd87b094e47a5c6a3e0a Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Fr=C3=A9d=C3=A9ric=20Guillot?= 
+Date: Fri, 30 Jun 2023 21:08:11 -0700
+Subject: [PATCH] Avoid potential SQL injections without breaking compatibility
+ with plugins
+
+---
+ libs/picodb/lib/PicoDb/Database.php | 6 ++
+ 1 file changed, 6 insertions(+)
+
+diff --git a/libs/picodb/lib/PicoDb/Database.php b/libs/picodb/lib/PicoDb/Database.php
+index 22c9d2fb61..df017ed82b 100644
+--- a/libs/picodb/lib/PicoDb/Database.php
 b/libs/picodb/lib/PicoDb/Database.php
+@@ -5,6 +5,7 @@
+ use Closure;
+ use PDOException;
+ use LogicException;
++use PicoDb\SQLException;
+ use PicoDb\Driver\Mssql;
+ use PicoDb\Driver\Sqlite;
+ use PicoDb\Driver\Mysql;
+@@ -215,6 +216,11 @@ public function escapeIdentifier($value, $table = '')
+ return $value;
+ }
+ 
++// Avoid potential SQL injection
++if (preg_match('/^[a-z0-9_]+$/', $value) === 0) {
++throw new SQLException('Invalid identifier: '.$value);
++}
++
+ if (! empty($table)) {
+ return $this->driver->escape($table).'.'.$this->driver->escape($value);
+ }
diff -Nru kanboard-1.2.26+ds/debian/patches/series kanboard-1.2.26+ds/debian/patches/series
--- kanboard-1.2.26+ds/debian/patches/series	2023-06-15 23:01:14.0 -0400
+++ kanboard-1.2.26+ds/debian/patches/series	2023-07-12 19:59:09.0 -0400
@@ -10,3 +10,4 @@
 CVE-2023-33956.patch
 CVE-2023-33970.patch
 CVE-2023-33968.patch
+CVE-2023-36813.patch


Bug#1039928: ifupdown2: set-fec encoding auto not supported

2023-06-29 Thread Joe Botha
Package: ifupdown2
Version: 3.0.0-1.1
Severity: normal
Tags: upstream

Dear Maintainer,

When using the latest ifupdown2 in Debian I get this error on an Nvidia SN2010 
switch:

ifreload -a
error: swp4: cmd '/sbin/ethtool --set-fec swp4 encoding auto' failed: returned 
83 (netlink error: Operation not supported)

It seems this attempts to set Forward Error Correction to Auto.

ifupdown2 version 3.0.0-1.1
ethtool version 6.1 

The Spectrum (mlxsw) driver does not support --set-fec encoding auto

I can make the error go away by commenting this line:

/usr/share/ifupdown2/addons/ethtool.py

if feccmd:
   try:
   feccmd = ('%s --set-fec %s %s' %
  (utils.ethtool_cmd, ifaceobj.name, feccmd))
   #utils.exec_command(feccmd)

I asked the mlxsw developers and they responded with:

"The problem needs to be solved in ifupdown2, which should not assume that 
every net device
implements these optional operations."

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

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

Versions of packages ifupdown2 depends on:
ii  iproute2  6.1.0-3
ii  python3   3.11.2-1+b1

ifupdown2 recommends no packages.

Versions of packages ifupdown2 suggests:
pn  bridge-utils 
ii  ethtool  1:6.1-1
ii  isc-dhcp-client  4.4.3-P1-2
pn  python3-gvgen
pn  python3-mako 

-- no debconf information



Bug#1038212: SOLVED

2023-06-17 Thread Joe Fiallo

Thank

After you confirm, I removed information about the previous package:

rm  /var/lib/dpkg/info/libsasl2-2*


The update process has been completed without errors

.


GRAZIE MILLE


Joe



Bug#1038212: Aggiornamento a Debian 12 interrotto

2023-06-17 Thread Joe Fiallo

Buongiorno

Scaricando il pacchetto libsasl2-2 singolarmente da un repository 
diverso  il messaggio cambia leggermente ma l'errore rimane



wget 
http://ftp.us.debian.org/debian/pool/main/c/cyrus-sasl2/libsasl2-2_2.1.28+dfsg-10_arm64.deb


sudo dpkg -i libsasl2-2_2.1.28+dfsg-10_arm64.deb

(Lettura del database... 76693 file e directory attualmente installati.)
Preparativi per estrarre libsasl2-2_2.1.28+dfsg-10_arm64.deb...
dpkg: errore nell'elaborare l'archivio 
libsasl2-2_2.1.28+dfsg-10_arm64.deb (--install):
 il file dei trigger "ci" contiene una direttiva "cctsvite-noawai0" 
sconosciuta

Si sono verificati degli errori nell'elaborazione:
 libsasl2-2_2.1.28+dfsg-10_arm64.deb

Grazie

    Joe



Bug#1038212: Aggiornamento a Debian 12 interrotto

2023-06-16 Thread Joe Fiallo

Package:    libsasl2-2

Version:    /stable 2.1.28+dfsg-10 arm64 [aggiornabile da: 
2.1.27+dfsg-2.1+deb11u1]


Durante l'aggiornamento da Debian 11.7   a 12.0  la procedura di 
full-upgrade si interrompe.


Il package che non si può aggiornare è  libsasl2-2



Il tentativo di proseguire con "apt --fix-broken install"

produce il seguente output

Preparativi per estrarre .../libsasl2-2_2.1.28+dfsg-10_arm64.deb...
dpkg: errore nell'elaborare l'archivio 
/var/cache/apt/archives/libsasl2-2_2.1.28+dfsg-10_arm64.deb (--unpack):
 il file dei trigger "ci" contiene una direttiva "bct{vate-noaw��0" 
sconosciuta

Si sono verificati degli errori nell'elaborazione:
 /var/cache/apt/archives/libsasl2-2_2.1.28+dfsg-10_arm64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Il sistema con aggiornamento parziale risponde a uname:

Linux pigreco4 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023 
aarch64 GNU/Linux




Grazie per la vostra importante attività


Joe



Bug#1037444: bookworm-pu: package kanboard/1.2.26+ds-4

2023-06-15 Thread Joe Nahmias
Attached is a revised debdiff between -2 and -2+deb12u1.
--Joe
diff -Nru kanboard-1.2.26+ds/debian/changelog 
kanboard-1.2.26+ds/debian/changelog
--- kanboard-1.2.26+ds/debian/changelog 2023-05-16 22:49:38.0 -0400
+++ kanboard-1.2.26+ds/debian/changelog 2023-06-15 23:02:33.0 -0400
@@ -1,3 +1,24 @@
+kanboard (1.2.26+ds-2+deb12u1) bookworm; urgency=high
+
+  * Cherry-pick security fixes from kanboard_1.2.26+ds-[34] for bookworm.
+  * backport fix for CVE-2023-32685 from kanboard v1.2.29
+
https://github.com/kanboard/kanboard/security/advisories/GHSA-hjmw-gm82-r4gv
+Based on upstream commits 26b6eeb & c9c1872.
+(cherry picked from commit d9b8d854f2d35831b04b84cfdda41cc7b49e3a28)
+(Closes: #1036874)
+  * backport security fixes from kanboard v1.2.30.
+ > CVE-2023-33956: Parameter based Indirect Object Referencing leading
+   to private file exposure
+ > CVE-2023-33968: Missing access control allows user to move and
+   duplicate tasks to any project in the software
+ > CVE-2023-33969: Stored XSS in the Task External Link Functionality
+ > CVE-2023-33970: Missing access control in internal task links feature
+(cherry picked from commit 4ad0ad220613bbf04bef559addba8c363fdf0dfa)
+(Closes: #1037167)
+  * point gbp & salsa at bookworm
+
+ -- Joseph Nahmias   Thu, 15 Jun 2023 23:02:33 -0400
+
 kanboard (1.2.26+ds-2) unstable; urgency=medium
 
   * properly test for lighty-enable-mod.
diff -Nru kanboard-1.2.26+ds/debian/gbp.conf kanboard-1.2.26+ds/debian/gbp.conf
--- kanboard-1.2.26+ds/debian/gbp.conf  2023-05-09 06:27:15.0 -0400
+++ kanboard-1.2.26+ds/debian/gbp.conf  2023-06-15 23:02:33.0 -0400
@@ -1,3 +1,3 @@
 [DEFAULT]
-debian-branch = debian/latest
+debian-branch = debian/bookworm
 pristine-tar = True
diff -Nru kanboard-1.2.26+ds/debian/patches/CVE-2023-32685.patch 
kanboard-1.2.26+ds/debian/patches/CVE-2023-32685.patch
--- kanboard-1.2.26+ds/debian/patches/CVE-2023-32685.patch  1969-12-31 
19:00:00.0 -0500
+++ kanboard-1.2.26+ds/debian/patches/CVE-2023-32685.patch  2023-06-15 
23:00:52.0 -0400
@@ -0,0 +1,111 @@
+Description: fix for CVE-2023-32685
+ Clipboard based cross-site scripting (blocked with default CSP)
+ https://github.com/kanboard/kanboard/security/advisories/GHSA-hjmw-gm82-r4gv
+Author: Frédéric Guillot 
+Origin: upstream
+Last-Update: 2023-05-24
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+diff --git a/assets/js/components/screenshot.js 
b/assets/js/components/screenshot.js
+index a8acd64..1130bd2 100644
+--- a/assets/js/components/screenshot.js
 b/assets/js/components/screenshot.js
+@@ -1,5 +1,4 @@
+ KB.component('screenshot', function (containerElement) {
+-var pasteCatcher = null;
+ var inputElement = null;
+ 
+ function onFileLoaded(e) {
+@@ -7,7 +6,6 @@ KB.component('screenshot', function (containerElement) {
+ }
+ 
+ function onPaste(e) {
+-// Firefox doesn't have the property e.clipboardData.items (only 
Chrome)
+ if (e.clipboardData && e.clipboardData.items) {
+ var items = e.clipboardData.items;
+ 
+@@ -24,69 +22,13 @@ KB.component('screenshot', function (containerElement) {
+ }
+ }
+ }
+-} else {
+-
+-// Handle Firefox
+-setTimeout(checkInput, 100);
+ }
+ }
+ 
+ function initialize() {
+-destroy();
+-
+-if (! window.Clipboard) {
+-// Insert the content editable at the top to avoid scrolling down 
in the board view
+-pasteCatcher = document.createElement('div');
+-pasteCatcher.id = 'screenshot-pastezone';
+-pasteCatcher.contentEditable = true;
+-pasteCatcher.style.opacity = 0;
+-pasteCatcher.style.position = 'fixed';
+-pasteCatcher.style.top = 0;
+-pasteCatcher.style.right = 0;
+-pasteCatcher.style.width = 0;
+-document.body.insertBefore(pasteCatcher, 
document.body.firstChild);
+-
+-pasteCatcher.focus();
+-
+-// Set the focus when clicked anywhere in the document
+-document.addEventListener('click', setFocus);
+-
+-// Set the focus when clicked in screenshot dropzone
+-
document.getElementById('screenshot-zone').addEventListener('click', setFocus);
+-}
+-
+ window.addEventListener('paste', onPaste, false);
+ }
+ 
+-function destroy() {
+-if (KB.exists('#screenshot-pastezone')) {
+-KB.find('#screenshot-pastezone').remove();
+-}
+-
+-document.removeEventListener('click', setFocus);
+-pasteCatcher = null;
+-}
+-
+-function setFocus() {
+-if (pasteCatcher !== null) {
+-

Bug#1033278: wine: Battle.Net: The application failed to start because no Qt platform plugin could be initialized

2023-03-21 Thread Joe Nahmias
On Mon, Mar 20, 2023 at 11:38:23PM -0400, Joseph Nahmias wrote:
> I just upgraded from bullseye to bookworm and now Battle.Net / Hearthstone
> refuses to start. Instead it shows this error message:
> 
> The application failed to start because no Qt
> platform plugin could be initialized. Reinstalling
> the application may fix this problem.
> 
> Was there some change in the wine packaging that would cause this error?
> Would additional logs/debug info be useful to troubleshoot?

False alarm. Seems to be related to an update of the Battle.Net client -- not
wine itself. See https://bugs.winehq.org/show_bug.cgi?id=53826 and
https://gitlab.winehq.org/wine/wine/-/merge_requests/1148 for details.

Thanks,
--Joe



Bug#1030920: src:ipyparallel unsatisfied build dependency: python-distributed-doc

2023-02-09 Thread Joe Nahmias
On Thu, Feb 09, 2023 at 09:09:12AM +0100, Paul Gevers wrote:
> Source: ipyparallel
> Version: 7.1.0-4
> Severity: serious
> Tags: sid bookworm
> User: debian...@lists.debian.org
> Usertags: edos-uninstallable
> 
> Dear maintainer(s),

Hello,

> Can you please investigate the situation and figure out how to resolve
> it? Regularly, if the build dependency is available in unstable,
> helping the maintainer of your Build-Depends to enable migration to
> testing is a great way to solve the issue. If your build dependency is
> gone from unstable and testing, you'll have to fix the build process
> in some other way. dask.distributed was removed from testing because of bug
> 1030096.

According to [2], dask.distributed 2022.02.0+ds.1-3 was removed due to a
hint from ginggs:

  Hint: <https://release.debian.org/britney/hints/ginggs>
# 20230125
# allow pandas and dask to migrate

And now version 2022.12.1+ds.1-2 is blocked from migrating due to 1030096.
Have I understood the situation correctly?

How does this relate to the impending soft freeze? My understanding is
that we only have until 2023-02-12 to fix dask.distributed and have it
migrated -- a very tight deadline.

> Paul
--Joe



Bug#1016588: ITP: sqlfluff -- A SQL linter and auto-formatter for Humans

2023-01-23 Thread Joe Nahmias
On Wed, Aug 03, 2022 at 05:18:34PM +, Felix Delattre wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Felix Delattre 
> 
> * Package name: sqlfluff
>   Version : 1.2.1
>   Upstream Author : sqlfluff contributors
> * URL : https://github.com/sqlfluff/sqlfluff/
> * License : MIT
>   Programming Lang: Python
>   Description : A SQL linter and auto-formatter for Humans
> 
> SQLFluff is a dialect-flexible and configurable SQL linter. Designed with
> ELT applications in mind, SQLFluff also works with Jinja templating and dbt.
> SQLFluff will auto-fix most linting errors, allowing you to focus your time
> on what matters.

Hello Felix,

Are you still planning on packaging this for Debian?

Thanks,
--Joe



Bug#1028982: metakernel: autopkgtest regression on s390x: AssertionError

2023-01-15 Thread Joe Nahmias
On Sun, Jan 15, 2023 at 07:37:01PM +0100, Paul Gevers wrote:
> With a recent upload of metakernel the autopkgtest of metakernel fails in
> testing when that autopkgtest is run with the binary packages of metakernel
> from unstable on s390x. It passes when run with only packages from testing.
> In tabular form:
> 
>passfail
> metakernel from testing0.29.4-1
> versioned deps [0] from testingfrom unstable
> all others from testingfrom testing
> 
> Currently this regression is blocking the migration to testing [1]. Can you
> please investigate the situation and fix it?
> 
> More information about this bug and the reason for filing it can be found on
> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
> 
> Paul

Hello Paul,

Thanks for the report. I ran the following to try and reproduce this using
unstable:

ssh zelenka.debian.org
schroot -b -c sid -n $LOGNAME-metakernel
dd-schroot-cmd -c $LOGNAME-metakernel apt-get update
dd-schroot-cmd -c $LOGNAME-metakernel apt-get dist-upgrade
dd-schroot-cmd -c $LOGNAME-metakernel apt-get build-dep metakernel
dd-schroot-cmd -c $LOGNAME-metakernel apt-get install python3-metakernel 
python-metakernel-doc autopkgtest autodep8 pybuild-plugin-autopkgtest
schroot -r -c $LOGNAME-metakernel
/usr/bin/autopkgtest --shell-fail metakernel -- null
exit
schroot -e -c $LOGNAME-metakernel

However, all the tests passed for both python 3.10 & 3.11.

> [0] You can see what packages were added from the second line of the log
> file quoted below. The migration software adds source package from unstable
> to the list if they are needed to install packages from metakernel/0.29.4-1.
> I.e. due to versioned dependencies or breaks/conflicts.
> [1] https://qa.debian.org/excuses.php?package=metakernel
> 
> https://ci.debian.net/data/autopkgtest/testing/s390x/m/metakernel/30188929/log.gz

I tried to look for this list of packages on the second line of the log.gz URL,
but second line I see is:

autopkgtest [16:36:08]: version 5.27

In any case, to the best of my knowledge, there aren't any direct versioned
deps from metakernel.

Moreover, I don't know how to inject metakernel/0.29.4-1 into a bookworm
schroot on zelenka, so I'm a bit stuck here :(

Any ideas on how to proceed?

--Joe



Bug#1028574: Please remove joehe...@gmail.com as an uploader

2023-01-12 Thread Joe Healy
Package: salt
Version: 3004.1+dfsg-2.2

As I no longer use Salt or have regular access to a debian system, I am
unable to continue as an uploader/maintainer for the salt packages. This
has been the case for some time and is unlikely to change.

As such, please remove me from the uploaders for the package.

I wish you all the best for the future.

Thanks and Regards,

Joe


Bug#1028477: php-odbc: regression - login failed with php 8.2, works under 8.1

2023-01-11 Thread Joe Nahmias
Package: php8.2-odbc
Version: 8.2.1-1
Severity: grave
X-Debbugs-Cc: j...@nahmias.net

Hello,

There seems to be a regression with php8.2-odbc, compared to php8.1-odbc:

$ cat /tmp/test-php_odbc.php
setAttribute(\PDO::ATTR_ERRMODE, \PDO::ERRMODE_EXCEPTION);
print("Connected!\n");

$ php8.1 /tmp/test-php_odbc.php
Connected!

$ php8.2 /tmp/test-php_odbc.php
PHP Fatal error:  Uncaught PDOException: SQLSTATE[42000] SQLDriverConnect: 
18456 [FreeTDS][SQL Server]Login failed for user 'kbUnitTests'. in 
/tmp/test-php_odbc.php:7
Stack trace:
#0 /tmp/test-php_odbc.php(7): PDO->__construct()
#1 {main}
  thrown in /tmp/test-php_odbc.php on line 7

$ dpkg -l php\* | grep ^i
ii  php-common 2:92+nmu1all  Common files for PHP packages
ii  php8.1-cli 8.1.12-1+b1  amd64command-line interpreter for 
the PHP scripting language
ii  php8.1-common  8.1.12-1+b1  amd64documentation, examples and 
common module for PHP
ii  php8.1-odbc8.1.12-1+b1  amd64ODBC module for PHP
ii  php8.1-opcache 8.1.12-1+b1  amd64Zend OpCache module for PHP
ii  php8.1-readline8.1.12-1+b1  amd64readline module for PHP
ii  php8.2-cli 8.2.1-1  amd64command-line interpreter for 
the PHP scripting language
ii  php8.2-common  8.2.1-1  amd64documentation, examples and 
common module for PHP
ii  php8.2-odbc8.2.1-1  amd64ODBC module for PHP
ii  php8.2-opcache 8.2.1-1  amd64Zend OpCache module for PHP
ii  php8.2-readline8.2.1-1  amd64readline module for PHP

Please let me know if you need any additional information!
--Joe



Bug#1028297: python3-freezegun: ships a copy of python3-arrow: /usr/lib/python3/dist-packages/arrow/*.py

2023-01-09 Thread Joe Nahmias
On Mon, Jan 09, 2023 at 11:59:42AM +0100, Andreas Beckmann wrote:
> Package: python3-freezegun
> Version: 1.2.1-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> during a test with piuparts I noticed your package failed to install
> because it tries to overwrite other packages files.

Actually, it looks like the upstream source tarball for arrow v1.2.1 got
imported into the freezegun salsa repo by mistake -- instead of freezegun
v1.2.1.  The (arrow) code was then subsequently built and uploaded (as
freezegun) -- without noticing the change.

This breaks anything that needs freezegun, as that python module is not
provided by this (version of the) package (anymore).

--Joe



Bug#1023952: libfluidsynth-dev: Package should not depend on libsystemd-dev and/or libsystemd0

2022-11-12 Thread Joe Werner
Package: libfluidsynth-dev
Version: 2.3.0-1
Severity: important
X-Debbugs-Cc: j...@pro-kevin.de

Dear Maintainer,

the package depends on systemd, which (seems) not strictly neccessary, nor 
would it be wanted by several people (myself included - hence the bug report). 
I know the subject is a potential minefield and I do not wish to open the old 
discussions again[*]

Problem: When installing libsdl-mixer2-dev (to build some software) it pulls in 
libfluidsynth-dev. This depends on libsystemd-dev and libsystemd0 - and this in 
turn collides with liblogind-compat.
This makes it difficult to develop (or test) said software on 
non-systemd-systems.

To remedy I did this:
- Got the source via apt-get
- removed systemd-dependencies from debian/control (very ham-fisted, I know)
- rebuilt package and installed it

Apparently this works, at least the software (Widelands) compiled against this 
new package works. Thus my guess is that the whole of systemd is not needed 
here, and it could be remedied with dependencies on alternative packages (like 
liblogind-compat, maybe?).

Cheers,
Joe

[*] And I am very grateful to all developers and maintainers, and submit this 
with the utmost respect for your work.


-- System Information:
Debian Release: bookworm/sid
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-2-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: runit (via /run/runit.stopit)
LSM: AppArmor: enabled

Versions of packages libfluidsynth-dev depends on:
ii  libasound2-dev1.2.7.2-1
ii  libdbus-1-dev 1.14.4-1devuan1
ii  libfluidsynth32.3.0-1
ii  libinstpatch-dev  1.1.6-1
ii  libjack-jackd2-dev [libjack-dev]  1.9.21~dfsg-1
ii  libpulse-dev  16.1+dfsg1-2+b1
ii  libreadline-dev   8.2-1
ii  libsdl2-dev   2.24.1+dfsg-1
ii  libsndfile1-dev [libsndfile-dev]  1.1.0-3+b1

libfluidsynth-dev recommends no packages.

libfluidsynth-dev suggests no packages.

-- no debconf information



Bug#1022252: fuse3: update-initramfs fails on fuse hook

2022-10-29 Thread Joe Pfeiffer
Update -- it appears mount.fuse has already been added to the initramfs
before this hook is called, so the call to copy_exec fails.  Replacing
the failing line with

copy_exec /sbin/mount.fuse3 /sbin || true

enables the initramfs to be created, though I doubt it's the optimal
solution.

On Sat, 22 Oct 2022 12:16:16 -0600 Joe Pfeiffer  
wrote:
> Package: fuse3
> Version: 3.11.0-1
> Severity: important
> 
> Dear Maintainer,
> 
> Attempting to upgrade my system, I get the following in the output for
> every kernel:
> 
> E: /usr/share/initramfs-tools/hooks/fuse failed with return 1.
> 
> Trying to get a little more information, I ran
> 
> update-initramfs -u -v -k all
> 
> and after many lines of output, got:
> 
> Adding binary /usr/lib/x86_64-linux-gnu/libe2p.so.2.3
> Calling hook fuse
> Adding binary /sbin/mount.fuse3
> E: /usr/share/initramfs-tools/hooks/fuse failed with return 1.
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>* What was the outcome of this action?
>* What outcome did you expect instead?
> 
> *** End of the template - remove these template lines ***
> 
> 
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers testing
>   APT policy: (700, 'testing'), (650, 'stable'), (600, 'unstable'), (550, 
> 'experimental'), (500, 'oldstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 5.18.0-3-amd64 (SMP w/12 CPU threads; PREEMPT)
> Kernel taint flags: 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 fuse3 depends on:
> ii  adduser3.129
> ii  libc6  2.35-3
> ii  libfuse3-3 3.11.0-1
> ii  lsb-base   11.4
> ii  mount  2.38.1-1.1+b1
> ii  sed4.8-1
> ii  sysvinit-utils [lsb-base]  3.05-6
> 
> fuse3 recommends no packages.
> 
> fuse3 suggests no packages.
> 



Bug#1022252: fuse3: update-initramfs fails on fuse hook

2022-10-22 Thread Joe Pfeiffer
Package: fuse3
Version: 3.11.0-1
Severity: important

Dear Maintainer,

Attempting to upgrade my system, I get the following in the output for
every kernel:

E: /usr/share/initramfs-tools/hooks/fuse failed with return 1.

Trying to get a little more information, I ran

update-initramfs -u -v -k all

and after many lines of output, got:

Adding binary /usr/lib/x86_64-linux-gnu/libe2p.so.2.3
Calling hook fuse
Adding binary /sbin/mount.fuse3
E: /usr/share/initramfs-tools/hooks/fuse failed with return 1.

*** Reporter, please consider answering these questions, where appropriate ***

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

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


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (700, 'testing'), (650, 'stable'), (600, 'unstable'), (550, 
'experimental'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.18.0-3-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: 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 fuse3 depends on:
ii  adduser3.129
ii  libc6  2.35-3
ii  libfuse3-3 3.11.0-1
ii  lsb-base   11.4
ii  mount  2.38.1-1.1+b1
ii  sed4.8-1
ii  sysvinit-utils [lsb-base]  3.05-6

fuse3 recommends no packages.

fuse3 suggests no packages.

-- no debconf information



Bug#1014887: Followup:

2022-07-13 Thread Joe Kesselman
Looking at the source code in 
https://github.com/cz172638/v4l-utils/blob/master/utils/ir-ctl/ir-ctl.c:


The file-read buffer is in read_file, at line 192:
char line[1024];

and when input is fetched in line 212,

while (fgets(line, sizeof(line), input)) {

the loop assumes that each call returns a complete line. It does *NOT* 
allow for the possibility that the line is longer than this buffer. (See 
https://en.cppreference.com/w/c/io/fgets for an illustration of this 
truncation and continuation.)


The most common fixes can be seen at 
https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87152445
Note that using the POSIX getline() function instead of fgets() 
automagically deals with this for you (though it does put the buffer in 
the heap rather than on the stack, so you're responsible for free()ing it).


Is that sufficient to get this fixed, or do you need me to submit a 
formal pull request?


--
  /_  Joe Kesselman (he/him/his)
-/ _) My Alexa skill for New Music/New Sounds fans:
  /   https://www.amazon.com/dp/B09WJ3H657/

() Plaintext Ribbon Campaign
/\ Stamp out HTML mail!



Bug#1014603: iusql fails if password contains semicolon

2022-07-08 Thread Joe Nahmias
Package: unixodbc
Version: 2.3.11-2
Severity: normal
File: /usr/bin/iusql
X-Debbugs-Cc: j...@nahmias.net

Hello,

I was trying to connect to an MSSQL database using unixodbc/iusql with
the FreeTDS driver. The password for the login was randomly generated
and contained a semicolon ";" in it. This worked fine when using the
FreeTDS tools tsql and fisql. However, the iusql tool from unixodbc
failed as follows:

$ iusql myDSN myLogin 'Y&MI%4VtL?C@OuUwmWkksL;+!#V$JSo6' -v
[FreeTDS][SQL Server]Unable to connect to data source
[FreeTDS][SQL Server]Login failed for user 'myLogin'.
[ISQL]ERROR: Could not SQLDriverConnect

Changing the password in the database worked around the issue, but I
guess iusql needs to do better escaping of special characters in the
password.

--Joe


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

Kernel: Linux 5.18.0-2-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 unixodbc depends on:
ii  libc6 2.33-7
ii  libodbc2  2.3.11-2
ii  libodbcinst2  2.3.11-2
ii  libreadline8  8.1.2-1.2

unixodbc recommends no packages.

unixodbc suggests no packages.

-- no debconf information



Bug#1012603: ITP: node-ismobilejs -- JavaScript library to detect mobile devices

2022-06-09 Thread joe
Package: wnpp
Severity: wishlist
Owner: Joe Nahmias 
X-Debbugs-CC: debian-de...@lists.debian.org
X-Debbugs-CC: Debian Javascript Maintainers 

X-Debbugs-CC: Kai Mallea 

* Package name: node-ismobilejs
  Version : 1.1.1
  Upstream Author : Kai Mallea 
* URL : https://github.com/kaimallea/isMobile
* License : Expat
  Programming Lang: JavaScript
  Description : JavaScript library to detect mobile devices

 A simple JavaScript library for detecting when a page is viewed
 on a mobile device. Output is placed in a JS object that you can
 then test for various results.
 .
 It works both in the browser as a JavaScript library or on the
 server side via NodeJS.
 .
 Node.js is an event-based server-side JavaScript engine.

This is a dependency for Kanboard.
I plan to maintain it within the JavaScript team.



Bug#1008676: RFP: danecheck -- DANE SMTP checker

2022-03-30 Thread Joe Nahmias
Hi Daniel,

I'm a DD, but entirely unfamiliar with Haskell, let alone how it's packaged
within Debian. Do you think that between the two of us we can make this work?

--Joe

On Wed, Mar 30, 2022 at 03:32:04PM +0200, Daniel Gröber wrote:
> Hi Joseph,
> 
> this package sounds useful. I know Haskell and Debian packaging aspects
> since I used to maintain ghc-mod in Debian (it's been a couple of releases
> though :). I would be happy to co-maintain this but unless you already have
> a sponsor in mind we'd still have to find one as I'm not a DD.
> 
> --Daniel
> 
> On Wed, Mar 30, 2022 at 09:02:56AM -0400, Joseph Nahmias wrote:
> > Package: wnpp
> > Severity: wishlist
> > X-Debbugs-Cc: j...@nahmias.net, postfix-us...@dukhovni.org, 
> > debian-hask...@lists.debian.org
> > 
> > * Package name: danecheck
> >   Version : 1.1.0
> >   Upstream Author : Viktor Dukhovni 
> > * URL : https://github.com/vdukhovni/danecheck
> > * License : BSD
> >   Programming Lang: Haskell
> >   Description : DANE SMTP checker
> > 
> > This is a tool to check DANE TLSA security for SMTP.
> > 
> > Features:
> >  *  Test the local resolver configuration by verifying the validity of the
> > root zone DNSKEY and SOA RRSets.
> >  *  Test whether DNSSEC is enabled for a given TLD.
> >  *  Check whether an email domain is fully protected (across all of its MX
> > hosts) by DANE TLSA records, and whether these match the actual
> > certificate chains seen at each IP address of each MX host.
> >  *  Perform certificate chain verification at a time offset from the current
> > time to ensure that that certificates are not about to expire too soon.
> > 
> > A non-zero exit status is returned if any DNS lookups fail or if the MX 
> > records
> > or MX hosts are in an unsigned zone, or if for one of the MX hosts no
> > associated secure TLSA records are found. A non-zero exit status is also
> > returned if any of the SMTP connections fail to establish a TLS connection 
> > or
> > yield a certificate chain that does not match the TLSA records.
> > 
> > 
> > Packaging note:
> > 
> > I do not know haskell, so wouldn't really be a good maintainer, thus 
> > submitting
> > this as an RFP. 
> > 



Bug#1005862: apt: Feature request - apt-get Source IP

2022-02-16 Thread Joe Botha
Hi

I figured out a temporary workaround using ‘ip netns exec’

It works, but things like apticron will still fail.




-- 
Swimmingly,
 Joe

swimgeek.com/blog  +27 82 562 6167  instagram.com/joe.swimgeek
  "...all progress depends on the unreasonable man.”




> On 16 Feb 2022, at 11:24, Joe Botha  wrote:
> 
> Hi
> 
> Yes, sorry, should maybe have had title with Source _IP_address_
> 
> I think you should be able to specify a source IP when opening the tcp socket.
> 
> Would probably need to add some code for IPv4 and IPv6 cases.
> 
> -- 
> Swimmingly,
> Joe
> 
> swimgeek.com/blog  +27 82 562 6167  instagram.com/joe.swimgeek
>  "...all progress depends on the unreasonable man.”
> 
> 
> 
> 
>> On 16 Feb 2022, at 11:11, Julian Andres Klode  wrote:
>> 
>> On Wed, Feb 16, 2022 at 10:42:57AM +0200, Joe Botha wrote:
>>> Package: apt
>>> Version: 2.2.4
>>> Severity: wishlist
>>> Tags: ipv6
>>> 
>>> Dear Maintainer,
>>> 
>>> *** Reporter, please consider answering these questions, where appropriate 
>>> ***
>>> 
>>> I use Debian on a server with multiple upstream internet links. Some of 
>>> these links have peering point IPs.
>>> 
>>> It happens fairly often that apt-get traffic uses the source IP in a 
>>> peering point range and then downloads fail.
>>> 
>>> Please consider adding a feature so I can configure apt-get to specify a 
>>> source IP or interface on the server.
>>> 
>>> For example: traceroute has a -s option: "Chooses  an alternative source 
>>> address."
>> 
>> I was about to say that specifying ip addresses for sources needs to be
>> solved at an RFC level (need to standardize URLs like http://foo[ip]/), 
>> but um now I understand that you don't want to configure the IP of the
>> source, but the interface we send packets from.
>> 
>> Probably should be retitled with a less ambiguous title :D
>> 
>> Anyway, no idea how complex that feature is, I guess proof of
>> concept patches welcome.
>> 
>> -- 
>> debian developer - deb.li/jak | jak-linux.org - free software dev
>> ubuntu core developer  i speak de, en
> 



Bug#1005862: apt: Feature request - apt-get Source IP

2022-02-16 Thread Joe Botha
Hi

Yes, sorry, should maybe have had title with Source _IP_address_

I think you should be able to specify a source IP when opening the tcp socket.

Would probably need to add some code for IPv4 and IPv6 cases.

-- 
Swimmingly,
 Joe

swimgeek.com/blog  +27 82 562 6167  instagram.com/joe.swimgeek
  "...all progress depends on the unreasonable man.”




> On 16 Feb 2022, at 11:11, Julian Andres Klode  wrote:
> 
> On Wed, Feb 16, 2022 at 10:42:57AM +0200, Joe Botha wrote:
>> Package: apt
>> Version: 2.2.4
>> Severity: wishlist
>> Tags: ipv6
>> 
>> Dear Maintainer,
>> 
>> *** Reporter, please consider answering these questions, where appropriate 
>> ***
>> 
>> I use Debian on a server with multiple upstream internet links. Some of 
>> these links have peering point IPs.
>> 
>> It happens fairly often that apt-get traffic uses the source IP in a peering 
>> point range and then downloads fail.
>> 
>> Please consider adding a feature so I can configure apt-get to specify a 
>> source IP or interface on the server.
>> 
>> For example: traceroute has a -s option: "Chooses  an alternative source 
>> address."
> 
> I was about to say that specifying ip addresses for sources needs to be
> solved at an RFC level (need to standardize URLs like http://foo[ip]/), 
> but um now I understand that you don't want to configure the IP of the
> source, but the interface we send packets from.
> 
> Probably should be retitled with a less ambiguous title :D
> 
> Anyway, no idea how complex that feature is, I guess proof of
> concept patches welcome.
> 
> -- 
> debian developer - deb.li/jak | jak-linux.org - free software dev
> ubuntu core developer  i speak de, en



Bug#1005862: apt: Feature request - apt-get Source IP

2022-02-16 Thread Joe Botha
Package: apt
Version: 2.2.4
Severity: wishlist
Tags: ipv6

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

I use Debian on a server with multiple upstream internet links. Some of these 
links have peering point IPs.

It happens fairly often that apt-get traffic uses the source IP in a peering 
point range and then downloads fail.

Please consider adding a feature so I can configure apt-get to specify a source 
IP or interface on the server.

For example: traceroute has a -s option: "Chooses  an alternative source 
address."


-- Package-specific info:

-- (no /etc/apt/preferences present) --


-- (no /etc/apt/preferences.d/* present) --


-- (/etc/apt/sources.list present, but not submitted) --


-- (/etc/apt/sources.list.d/grafana.list present, but not submitted) --


-- (/etc/apt/sources.list.d/influxdb.list present, but not submitted) --


-- (/etc/apt/sources.list.d/ookla_speedtest-cli.list present, but not 
submitted) --


-- (/etc/apt/sources.list.d/saltstack.list present, but not submitted) --


-- (/etc/apt/sources.list.d/stretch-backports.list present, but not submitted) 
--


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

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

Versions of packages apt depends on:
ii  adduser 3.118
ii  debian-archive-keyring  2021.1.1
ii  gpgv2.2.27-2
ii  libapt-pkg6.0   2.2.4
ii  libc6   2.31-13+deb11u2
ii  libgcc-s1   10.2.1-6
ii  libgnutls30 3.7.1-5
ii  libseccomp2 2.5.1-1+deb11u1
ii  libstdc++6  10.2.1-6
ii  libsystemd0 247.3-6

Versions of packages apt recommends:
ii  ca-certificates  20210119

Versions of packages apt suggests:
pn  apt-doc  
pn  aptitude | synaptic | wajig  
ii  dpkg-dev 1.20.9
ii  gnupg2.2.27-2
ii  powermgmt-base   1.36

-- no debconf information



Bug#1002190: [Pkg-javascript-devel] Bug#1002190: Bug#1002190: gyp: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13

2021-12-22 Thread joe
I can take a look at this.--Joe
 Original message From: Yadd  Date: 12/22/21  
04:57  (GMT-05:00) To: 1002...@bugs.debian.org Subject: [Pkg-javascript-devel] 
Bug#1002190: Bug#1002190: gyp: FTBFS:
  dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9"
  returned exit code 13 Hi,is there someone with Python skills to fix that ?I 
think that this package should really own to Python Team, not JS 
Team.Cheers,YaddOn 21/12/2021 16:59, Lucas Nussbaum wrote:> Source: gyp> 
Version: 0.1+20210831gitd6c5dd5-1> Severity: serious> Justification: FTBFS> 
Tags: bookworm sid ftbfs> User: lu...@debian.org> Usertags: ftbfs-20211220 
ftbfs-bookworm> > Hi,> > During a rebuild of all packages in sid, your package 
failed to build> on amd64.> > > Relevant part (hopefully):>> make[1]: Entering 
directory '/<>'>> dh_auto_build>> I: pybuild base:237: 
/usr/bin/python3.10 setup.py build>> running build>> running build_py>> 
creating /<>/.pybuild/cpython3_3.10/build/gyp>> copying 
pylib/gyp/__init__.py -> /<>/.pybuild/cpython3_3.10/build/gyp>> 
copying pylib/gyp/xcode_ninja.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp>> copying 
pylib/gyp/simple_copy.py -> /<>/.pybuild/cpython3_3.10/build/gyp>> 
copying pylib/gyp/ninja_syntax.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp>> copying 
pylib/gyp/common_test.py -> /<>/.pybuild/cpython3_3.10/build/gyp>> 
copying pylib/gyp/win_tool.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp>> copying pylib/gyp/input.py 
-> /<>/.pybuild/cpython3_3.10/build/gyp>> copying 
pylib/gyp/MSVSProject.py -> /<>/.pybuild/cpython3_3.10/build/gyp>> 
copying pylib/gyp/xml_fix.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp>> copying 
pylib/gyp/MSVSUtil.py -> /<>/.pybuild/cpython3_3.10/build/gyp>> 
copying pylib/gyp/mac_tool.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp>> copying 
pylib/gyp/flock_tool.py -> /<>/.pybuild/cpython3_3.10/build/gyp>> 
copying pylib/gyp/xcodeproj_file.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp>> copying 
pylib/gyp/input_test.py -> /<>/.pybuild/cpython3_3.10/build/gyp>> 
copying pylib/gyp/easy_xml_test.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp>> copying 
pylib/gyp/msvs_emulation.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp>> copying 
pylib/gyp/xcode_emulation.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp>> copying pylib/gyp/common.py 
-> /<>/.pybuild/cpython3_3.10/build/gyp>> copying 
pylib/gyp/MSVSUserFile.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp>> copying 
pylib/gyp/easy_xml.py -> /<>/.pybuild/cpython3_3.10/build/gyp>> 
copying pylib/gyp/MSVSSettings.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp>> copying 
pylib/gyp/MSVSVersion.py -> /<>/.pybuild/cpython3_3.10/build/gyp>> 
copying pylib/gyp/MSVSToolFile.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp>> copying 
pylib/gyp/MSVSSettings_test.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp>> copying 
pylib/gyp/MSVSNew.py -> /<>/.pybuild/cpython3_3.10/build/gyp>> 
creating /<>/.pybuild/cpython3_3.10/build/gyp/generator>> copying 
pylib/gyp/generator/__init__.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp/generator>> copying 
pylib/gyp/generator/xcode_test.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp/generator>> copying 
pylib/gyp/generator/msvs_test.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp/generator>> copying 
pylib/gyp/generator/msvs.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp/generator>> copying 
pylib/gyp/generator/ninja_test.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp/generator>> copying 
pylib/gyp/generator/gypsh.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp/generator>> copying 
pylib/gyp/generator/analyzer.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp/generator>> copying 
pylib/gyp/generator/xcode.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp/generator>> copying 
pylib/gyp/generator/make.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp/generator>> copying 
pylib/gyp/generator/gypd.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp/generator>> copying 
pylib/gyp/generator/dump_dependency_json.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp/generator>> copying 
pylib/gyp/generator/eclipse.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp/generator>> copying 
pylib/gyp/generator/ninja.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp/generator>> copying 
pylib/gyp/generator/cmake.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp/generator>> I: pybuild 
base:237: /

Bug#1001413: [pkg-php-pear] Bug#1001413: error when running composer list

2021-12-10 Thread Joe Nahmias
On Thu, Dec 09, 2021 at 09:42:07PM -0400, David Prévot wrote:
> Hi Joe,
> 
> Thank you for your report.
> 
> Le 09/12/2021 à 15:46, Joe Nahmias a écrit :
> […]
> > $ /usr/bin/composer list
> […]
> > PHP Fatal error:  Uncaught Error: Class "Normalizer" not found in 
> > /usr/share/php/Symfony/Component/Console/Helper/Helper.php:65
> 
> I suspect the issue is related to the PHP 8.1 transition that will soon
> begin. Can you check if php7.4-intl is installed, and if not, if installing
> it fixes the issue (or php8.1-intl if you already set PHP 8.1 as default).

Yes, php7.4-intl is already installed. Not sure how I would have set 8.1
as default...
Here's the full list of what I have:

$ dpkg -l php\* | grep ^.i
ii  php-cli   2:8.1+85+really7.4+88 
all  command-line interpreter for the PHP scripting language (default)
ii  php-codecoverage  9.2.10+dfsg-1 
all  collection, processing, and rendering for code coverage
ii  php-common2:88  
all  Common files for PHP packages
ii  php-composer-ca-bundle1.3.1-1   
all  utility library to find a path to the system CA bundle
ii  php-composer-metadata-minifier1.0.0-2   
all  Small utility library that handles metadata minification and 
expansion
ii  php-composer-semver   3.2.6-1   
all  utilities, version constraint parsing and validation
ii  php-composer-spdx-licenses1.5.6-1   
all  SPDX licenses list and validation library
ii  php-composer-xdebug-handler   2.0.2-1   
all  Restarts a process without Xdebug
ii  php-db1.10.0-1  
all  Database Abstraction Layer
ii  php-deepcopy  1.10.2-3  
all  create deep copies (clones) of objects
ii  php-doctrine-instantiator 1.4.0-1   
all  lightweight utility to instantiate objects in PHP
ii  php-file-iterator 3.0.6-1   
all  FilterIterator implementation for PHP
ii  php-fpm   2:8.1+85+really7.4+88 
all  server-side, HTML-embedded scripting language (FPM-CGI binary) 
(default)
ii  php-gd2:8.1+85+really7.4+88 
all  GD module for PHP [default]
ii  php-imap  2:8.1+85+really7.4+88 
all  IMAP module for PHP [default]
ii  php-intl  2:8.1+85+really7.4+88 
all  Internationalisation module for PHP [default]
ii  php-invoker   3.1.1-2   
all  Invoke callables with a timeout
ii  php-json-schema   5.2.11-1  
all  implementation of JSON schema
ii  php-mbstring  2:8.1+85+really7.4+88 
all  MBSTRING module for PHP [default]
ii  php-mysql 2:8.1+85+really7.4+88 
all  MySQL module for PHP [default]
ii  php-parser4.13.2-1  
all  convert PHP code into abstract syntax tree
ii  php-pear  1:1.10.12+submodules+notgz+20210212-1 
all  PEAR Base System
ii  php-phar-io-manifest  2.0.3-1   
all  reading phar.io manifest information from a PHP Archive (Phar)
ii  php-phar-io-version   3.0.4-1   
all  handling version information and constraint
ii  php-phpdocumentor-reflection-common   2.2.0-1   
all  Common reflection classes - phpDocumentor component
ii  php-phpdocumentor-reflection-docblock 5.3.0-1   
all  DocBlock parser - phpDocumentor component
ii  php-phpdocumentor-type-resolver   1.5.1-1   
all  TypeResolver and FqsenResolver - phpDocumentor component
ii  php-phpspec-prophecy  1.14.0-2  
all  object mocking framework - phpspec component
ii  php-psr-container 1.1.2-1   
all  Common Container Interface (PHP FIG PSR-11)
ii  php-psr-log   1.1.3-2   
all  common interface for logging libraries
ii  php-react-promise 2.7.0-2   

Bug#1001413: error when running composer list

2021-12-09 Thread Joe Nahmias
Package: composer
Version: 2.1.14-1
Severity: normal
File: /usr/bin/composer
X-Debbugs-Cc: j...@nahmias.net

Hello,

I just tried running composer list and got a bunch of PHP error spew,
see below.

$ /usr/bin/composer list
   __
  / /___   ___        _
 / /   / __ \/ __ `__ \/ __ \/ __ \/ ___/ _ \/ ___/
/ /___/ /_/ / / / / / / /_/ / /_/ (__  )  __/ /
\/\/_/ /_/ /_/ .___/\//\___/_/
/_/
Composer 2.1.14 2021-11-30 10:51:43

Usage:
  command [options] [arguments]

PHP Fatal error:  Uncaught Error: Class "Normalizer" not found in 
/usr/share/php/Symfony/Component/Console/Helper/Helper.php:65
Stack trace:
#0 /usr/share/php/Symfony/Component/Console/Descriptor/TextDescriptor.php(327): 
Symfony\Component\Console\Helper\Helper::width()
#1 /usr/share/php/Symfony/Component/Console/Descriptor/TextDescriptor.php(97): 
Symfony\Component\Console\Descriptor\TextDescriptor->calculateTotalWidthForOptions()
#2 /usr/share/php/Symfony/Component/Console/Descriptor/TextDescriptor.php(195): 
Symfony\Component\Console\Descriptor\TextDescriptor->describeInputDefinition()
#3 /usr/share/php/Symfony/Component/Console/Descriptor/Descriptor.php(55): 
Symfony\Component\Console\Descriptor\TextDescriptor->describeApplication()
#4 /usr/share/php/Symfony/Component/Console/Helper/DescriptorHelper.php(65): 
Symfony\Component\Console\Descriptor\Descriptor->describe()
#5 /usr/share/php/Symfony/Component/Console/Command/ListCommand.php(75): 
Symfony\Component\Console\Helper\DescriptorHelper->describe()
#6 /usr/share/php/Symfony/Component/Console/Command/Command.php(298): 
Symfony\Component\Console\Command\ListCommand->execute()
#7 /usr/share/php/Symfony/Component/Console/Application.php(1005): 
Symfony\Component\Console\Command\Command->run()
#8 /usr/share/php/Symfony/Component/Console/Application.php(299): 
Symfony\Component\Console\Application->doRunCommand()
#9 /usr/share/php/Composer/Console/Application.php(327): 
Symfony\Component\Console\Application->doRun()
#10 /usr/share/php/Symfony/Component/Console/Application.php(171): 
Composer\Console\Application->doRun()
#11 /usr/share/php/Composer/Console/Application.php(128): 
Symfony\Component\Console\Application->run()
#12 /usr/bin/composer(74): Composer\Console\Application->run()
#13 {main}
  thrown in /usr/share/php/Symfony/Component/Console/Helper/Helper.php on line 
65

Fatal error: Uncaught Error: Class "Normalizer" not found in 
/usr/share/php/Symfony/Component/Console/Helper/Helper.php:65
Stack trace:
#0 /usr/share/php/Symfony/Component/Console/Descriptor/TextDescriptor.php(327): 
Symfony\Component\Console\Helper\Helper::width()
#1 /usr/share/php/Symfony/Component/Console/Descriptor/TextDescriptor.php(97): 
Symfony\Component\Console\Descriptor\TextDescriptor->calculateTotalWidthForOptions()
#2 /usr/share/php/Symfony/Component/Console/Descriptor/TextDescriptor.php(195): 
Symfony\Component\Console\Descriptor\TextDescriptor->describeInputDefinition()
#3 /usr/share/php/Symfony/Component/Console/Descriptor/Descriptor.php(55): 
Symfony\Component\Console\Descriptor\TextDescriptor->describeApplication()
#4 /usr/share/php/Symfony/Component/Console/Helper/DescriptorHelper.php(65): 
Symfony\Component\Console\Descriptor\Descriptor->describe()
#5 /usr/share/php/Symfony/Component/Console/Command/ListCommand.php(75): 
Symfony\Component\Console\Helper\DescriptorHelper->describe()
#6 /usr/share/php/Symfony/Component/Console/Command/Command.php(298): 
Symfony\Component\Console\Command\ListCommand->execute()
#7 /usr/share/php/Symfony/Component/Console/Application.php(1005): 
Symfony\Component\Console\Command\Command->run()
#8 /usr/share/php/Symfony/Component/Console/Application.php(299): 
Symfony\Component\Console\Application->doRunCommand()
#9 /usr/share/php/Composer/Console/Application.php(327): 
Symfony\Component\Console\Application->doRun()
#10 /usr/share/php/Symfony/Component/Console/Application.php(171): 
Composer\Console\Application->doRun()
#11 /usr/share/php/Composer/Console/Application.php(128): 
Symfony\Component\Console\Application->run()
#12 /usr/bin/composer(74): Composer\Console\Application->run()
#13 {main}
  thrown in /usr/share/php/Symfony/Component/Console/Helper/Helper.php on line 
65



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

Kernel: Linux 5.15.0-2-amd64 (SMP w/1 CPU thread)
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 composer depends on:
ii  jsonlint1.8.3-2
ii  php-common  2:88
ii  php-composer-ca-bundle  1.3.1-1
ii  php-composer-metadata-minifier  1.0.0-2
ii  php-composer-semver 3.2.6-1
ii  php-composer-spdx-licenses  1.5.6

Bug#877946: status of python-cx-oracle in Debian?

2021-11-19 Thread Joe Nahmias
Hello,

I am currently in need of the cx_Oracle python module. I see the salsa repo [0]
is gathering dust at the moment... Are you still working on packaging it for
Debian? Would it be okay if I took over and worked on it under the Debian
Python Team?

BTW - I note that since it requires the oracle client, it should go to contrib,
not main. Please let me know if you understand otherwise.

Thanks,
--Joe

0: https://salsa.debian.org/python-team/packages/python-cx-oracle



Bug#997378: python-coverage: diff for NMU version 5.1+dfsg.1-2.1

2021-11-19 Thread Joe Nahmias
Control: tags 997378 + patch


Dear maintainer,

I've prepared an NMU for python-coverage (versioned as 5.1+dfsg.1-2.1). The diff
is attached to this message.

Regards.

diff -Nru python-coverage-5.1+dfsg.1/debian/changelog python-coverage-5.1+dfsg.1/debian/changelog
--- python-coverage-5.1+dfsg.1/debian/changelog	2020-09-06 01:43:16.0 -0400
+++ python-coverage-5.1+dfsg.1/debian/changelog	2021-11-19 08:33:46.0 -0500
@@ -1,3 +1,10 @@
+python-coverage (5.1+dfsg.1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * use add_css_file() instead of deprecated add_stylesheet(); closes: #997378. 
+
+ -- Joseph Nahmias   Fri, 19 Nov 2021 08:33:46 -0500
+
 python-coverage (5.1+dfsg.1-2) unstable; urgency=medium
 
   * The “Karl Karnadi” release.
diff -Nru python-coverage-5.1+dfsg.1/debian/patches/05.fix-add_stylesheet.patch python-coverage-5.1+dfsg.1/debian/patches/05.fix-add_stylesheet.patch
--- python-coverage-5.1+dfsg.1/debian/patches/05.fix-add_stylesheet.patch	1969-12-31 19:00:00.0 -0500
+++ python-coverage-5.1+dfsg.1/debian/patches/05.fix-add_stylesheet.patch	2021-11-19 08:31:49.0 -0500
@@ -0,0 +1,18 @@
+Description: use add_css_file() instead of deprecated add_stylesheet()
+Author: Joseph Nahmias 
+Bug-debian: https://bugs.debian.org/997378
+Forwarded: not-needed
+Applied-Upstream: https://github.com/nedbat/coveragepy/commit/4859de2850f703207b0cab2ff6e7116a3e587b65
+Last-Update: 2021-11-19
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/doc/conf.py
 b/doc/conf.py
+@@ -230,6 +230,6 @@ prerelease = bool(max(release).isalpha()
+ 
+ def setup(app):
+ """Configure Sphinx"""
+-app.add_stylesheet('coverage.css')
++app.add_css_file('coverage.css')
+ app.add_config_value('prerelease', False, 'env')
+ print("** Prerelease = %r" % prerelease)
diff -Nru python-coverage-5.1+dfsg.1/debian/patches/series python-coverage-5.1+dfsg.1/debian/patches/series
--- python-coverage-5.1+dfsg.1/debian/patches/series	2020-09-06 01:43:16.0 -0400
+++ python-coverage-5.1+dfsg.1/debian/patches/series	2021-11-19 08:32:28.0 -0500
@@ -2,3 +2,4 @@
 02.rename-public-programs.patch
 03.remove-hotkeys.patch
 04.sphinx-add-code-path.patch
+05.fix-add_stylesheet.patch


Bug#685506: debian-policy: Please add field Files-Excluded to machine readable copyright files definition

2021-11-13 Thread Joe Nahmias
Hello again,

On Mon, Oct 26, 2020 at 03:14:02PM -0700, Sean Whitton wrote:
> Hello,
> 
> On Sun 25 Oct 2020 at 09:40PM -04, Joe Nahmias wrote:
> 
> > Is this truly the case that all that's needed is a new patch? Can we get
> > an official ACK from one of the policy editors? I'd be happy to re-write
> > the original patch to apply against HEAD if that's all that is required.
> 
> Well, it would need seconding, but otherwise, ACK.
> 
> Thank you for your interest.

Well, it took me longer than I anticipated to get around to this; nevertheless,
below is my first draft at a patch to document Files-Excluded. It's my first
time writing for Debian Policy, so please let me know if I didn't use an
appropriate convention somewhere.

--Joe

---
 copyright-format-1.0.xml | 52 
 1 file changed, 52 insertions(+)

diff --git a/copyright-format-1.0.xml b/copyright-format-1.0.xml
index b8df359..102b7fa 100644
--- a/copyright-format-1.0.xml
+++ b/copyright-format-1.0.xml
@@ -246,6 +246,11 @@
 Copyright: optional.
   
 
+
+  
+Files-Excluded: 
optional.
+  
+
   
   
 The Copyright and License
@@ -672,6 +677,53 @@ Copyright 2009, 2010 Angela Watts
   
 
 
+
+  Files-Excluded
+  
+Whitespace-separated list: list of patterns indicating files that have
+been removed from the original upstream source distribution. The
+syntax for the patterns describing these files is identical to that
+of the Files
+field.
+  
+  
+Often upstream developers include additional files in their source
+distribution files that are unwanted by Debian and/or unneeded for
+use in building a Debian package, such as:
+
+  
+
+  Source files that do not meet the DFSG;
+
+  
+  
+
+  Pre-compiled executable binary or other non human-editable files;
+
+  
+  
+
+  Files intended for use with other platforms.
+
+  
+
+  
+  
+These types of files, or any others that Debian does not want to
+include in our archive, must be stripped from the upstream tarball
+prior to uploading. The Files-Excluded field serves
+to document the removal of these files from the original upstream
+source. This allows others to understand or audit how the source
+distribution in Debian is derived from the upstream source.
+  
+  
+Additionally, once documented in this manner, various tools such as
+uscan or mk-origtargz can use
+this information as instructions on how to automatically repack an
+upstream source distribution into one suitable for use within Debian.
+  
+
+
   
   
 License specification


signature.asc
Description: PGP signature


Bug#998245: virtualbox-dkms upgrades out of sync with other virtualbox packages

2021-11-01 Thread Joe Pfeiffer
Package: virtualbox-dkms
Version: 6.1.28-dfsg-1+b1
Severity: important

Dear Maintainer,

Following updates in aptitude, I now have the following situation:
snowball:511$ dpkg -l "virtualbox*" | grep ii
ii  virtualbox 6.1.26-dfsg-4amd64x86 
virtualization solution - base binaries
ii  virtualbox-dkms6.1.28-dfsg-1+b1 amd64x86 
virtualization solution - kernel module sources for dkms
ii  virtualbox-ext-pack6.1.26-2 all  extra 
capabilities for VirtualBox, downloader.
ii  virtualbox-guest-additions-iso 6.1.22-1 all  guest 
additions iso image for VirtualBox
ii  virtualbox-qt  6.1.26-dfsg-4amd64x86 
virtualization solution - Qt based user interface

Because virtualbox-dkms was upgraded and virtualbox was not, I am
unable to launch a VM (when I try I get an error popup).  I would have
expected the varius virtualbox* packages to have been kept in sync so
this could not happen.

-- System Information:
Debian Release: 11.0
  APT prefers testing
  APT policy: (700, 'testing'), (650, 'stable'), (600, 'unstable'), (550, 
'experimental'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
Kernel taint flags: 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 virtualbox-dkms depends on:
ii  dkms  2.8.4-3

Versions of packages virtualbox-dkms recommends:
ii  virtualbox  6.1.26-dfsg-4

virtualbox-dkms suggests no packages.

-- debconf-show failed



Bug#997916: general: bullseye, (sometimes) keyboard freezes after suspend.

2021-10-27 Thread JoE
Package: general
Severity: normal
X-Debbugs-Cc: bullk...@protonmail.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

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

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

I've had this issue with this version of Debian 11 and previous
as well. It's doesnt always happen, most times I suspend the
system and when resume, keyboard works fine, and sometimes it
freezes when resume from suspend. Haven't found any solution
online yet, I tried removing xscreensaver and xss-lock but issue
remains.



Bug#972570: [Pkg-javascript-devel] Bug#972570: node-lightgallery is built using minified files

2021-10-03 Thread Joe Nahmias
Hello,

Now that bullseye has been released, would it be possible to upload a fix
for this to unstable? That would allow node-lightgallery and rainloop to
migrate to testing (bookworm) and then be backported to bullseye.

If you are not able to do this at the moment, due to time constraints, I'm
happy to prepare the upload based on what's in Salsa, as long as it's okay
with the JS team.

Thanks,
--Joe

On Sat, Apr 24, 2021 at 04:12:06PM -0700, Daniel Ring wrote:
> It looks like this RC bug also caused the next version of Rainloop to be
> removed from bullseye before the freeze. That version contains an relatively
> important security fix (bug #962629), so both Rainloop and node-lightgallery
> will need to be uploaded to bullseye-backports (when available) as well as
> unstable.
> 
> Sincerely,
> Daniel Ring
> 
> On 4/23/2021 9:35 PM, Daniel Ring wrote:
> > The warnings are already overridden in the current version on Salsa,
> > since the Youtube/Vimeo/etc. embeds are only loaded when Lightgallery is
> > used to display a video from that source (e.g. by passing it a Youtube
> > link).
> > 
> > Sincerely,
> > Daniel Ring
> > 
> > On 4/23/2021 12:31 PM, Yadd wrote:
> > > Le 23/04/2021 à 19:03, Jonas Smedegaard a écrit :
> > > > Quoting Yadd (2021-04-23 17:47:23)
> > > > > Control: tags -1 + pending
> > > > > 
> > > > > Le 23/04/2021 à 09:44, Daniel Ring a écrit :
> > > > > > Hello Xavier,
> > > > > > 
> > > > > > It looks like the build process was minifying the source files to 
> > > > > > the
> > > > > > destination *.js files and copying the pre-minified
> > > > > > files to *.min.js. I
> > > > > > corrected it to copy the unminified files directly and minify them 
> > > > > > to
> > > > > > *.min.js.
> > > > > > 
> > > > > > I also updated the package on Salsa to exclude the minified
> > > > > > modules/*.min.js files via Files-Excluded in
> > > > > > d/copyright, so they're no
> > > > > > longer in the source package at all.
> > > > > > 
> > > > > > Sincerely,
> > > > > > Daniel Ring
> > > > > 
> > > > > Hi,
> > > > > 
> > > > > looks good to me, thanks! Could you also ignore these warnings in a
> > > > > debain/lintian-overrides? It looks like false positive
> > > > > 
> > > > > Cheers,
> > > > > Yadd
> > > > > 
> > > > >   W: node-lightgallery: privacy-breach-generic
> > > > > usr/share/nodejs/lightgallery/dist/js/lg-video.min.min.js [ > > > > class="lg-video-object lg-dailymotion '+o+'" '+l+' width="560"
> > > > > height="315"
> > > > [...]
> > > > Those warnings look real to me.
> > > > 
> > > > What makes you consider them false positives, Xavier?
> > > 
> > > Hi Jonas,
> > > 
> > > yes but the relevant lines are in if/then/else blocks:
> > > 
> > >    if (isVideo.youtube) {
> > >  ...  video = '

Bug#990214: unblock: dovecot-fts-xapian/1.4.9a-1

2021-07-05 Thread Joe Nahmias
Control: tags -1 - moreinfo

Hello,

On Sun, Jul 04, 2021 at 10:17:31PM +0200, Sebastian Ramacher wrote:
> Control: tags -1 moreinfo confirmed
> 
> Assuming that the upload happens soon, please go ahead and remove the
> moreinfo tag once the new version is available in unstable.

Thanks for reviewing. I've added one additional patch cherry-picked from
upstream to fix a crash when reindexing, see attached. Uploaded to
unstable.

--Joe



Bug#990214: unblock: dovecot-fts-xapian/1.4.9a-1

2021-06-23 Thread Joe Nahmias
On Tue, Jun 22, 2021 at 10:50:00PM -0400, Joseph Nahmias wrote:
> Source debdiff from 1.4.7-1 (currently in testing) to 1.4.9a-1 is attached
> here. Please let me know when approved so I can upload to unstable.

Hi release team,

I realize that the size of the debdiff is not ideal for an update at this
point in the release cycle; however, I have reviewed every line in it and
feel that the changes to the source are quite targetted such that it makes
sense to take a new version and be in sync with upstream's releases
instead of cherry-picking 80%+ of the changes.

Happy to discuss further on email/bts or on IRC.

Thanks,
--Joe



Bug#972044: still there

2021-06-17 Thread Joe Pfeiffer
The problem persists with version 21.1.0-4



Bug#988262: auto-apt-proxy: the busybox gateway code is never executed even with busybox installed

2021-05-08 Thread Joe Krisch
Package: auto-apt-proxy

Version: 13.1

Severity: normal



The test "busybox ip >/dev/null 2>&1;" doesn't appear to ever be true and
the busybox gateway code is skipped whether or not busybox is installed and
it would work.

"busybox ip route list >/dev/null 2>&1;" does work as well as "busybox true
>/dev/null 2>&1;"

I tried this both within a docker container and outside.

Updating that line to either busybox ip route or busybox true got things
working.


-- System Information:

Debian Release: bullseye/sid

  APT prefers testing

  APT policy: (500, 'testing')

Architecture: amd64 (x86_64)


Kernel: Linux 5.4.0-72-generic (SMP w/4 CPU threads)

Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE

Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set

Shell: /bin/sh linked to /bin/dash

Init: unable to detect


Versions of packages auto-apt-proxy depends on:

ii  apt  2.2.2


Versions of packages auto-apt-proxy recommends:

ii  busybox  1:1.30.1-6+b1


auto-apt-proxy suggests no packages.


-- no debconf information


Bug#987681: libtycho-java: please update tycho to new upstream version 2.0.0 or newer

2021-05-03 Thread Joe Nahmias
On Thu, Apr 29, 2021 at 11:00:23AM +0100, Sudip Mukherjee wrote:
> Hi Joe,
> 
> On Tue, Apr 27, 2021 at 01:12:13PM -0400, Joseph Nahmias wrote:
> > Package: libtycho-java
> > Version: 1.6.0-2
> > Severity: wishlist
> > X-Debbugs-Cc: j...@nahmias.net
> > 
> > Hello,
> > 
> > I am trying to build some software that requires tycho 2.0.0, which was
> > release on 2020-08-03. Since then there have been a few more releases,
> > with 2.3.0 released on 2021-03-24. It would be great if Debian could
> > provide a newer version -- at least in unstable.
> 
> Thanks for this bug report. Looks like the license for some of the files
> have changed to EPL-2.0. I will rework on the the copyright information
> and upload v2.3.0 to experimental by the weekend. I should not be
> uploading to unstable now as Debian is in freeze.

Thank you so much for this Sudip! I didn't expect a response (and an
upload) to happen so quickly.

> --
> Regards
> Sudip

Much obliged,
--Joe



Bug#985473: slic3r: symbol lookup error after gcode export

2021-04-07 Thread Joe Pfeiffer
Bernhard Übelacker writes:
>Hello Joe,
>thanks for the backtrace. It enabled me to reproduce it.
>You have configured a post processing step in your printer settings?

Yes.  I'm sorry I didn't mention that in my original report; it simply
didn't occur to me.

>Then this setenv function is tried to be located in the loaded
>shared objects. Unfortunately Slic3r/XS/XS.so does not show to be
>linked to libboost_nowide.so, where the missing symbols seems to be.
>
>With the 2 lines changed at the bottom of this mail,
>ldd XS.so shows also a line for libboost_nowide.so,
>therefore it gets loaded automatically by the dynamic loader
>and symbol resolution should find it.
>A package build with it shows then a correct error message
>about my missing post processing file.
>
>The given upstream commit contain similar changes.

Excellent!  After a couple of quick passes it's clear I don't have
nearly enough relevant libraries on my machine to build and test the
changes; if you could send me a binary or .deb I'd be happy to give it
a try.
-- 
Joe Pfeiffer   575.525.2764 (H)
1440 Tierra del Sol Dr 575.496.3501 (C)
Las Cruces, NM 88007-5548  



Bug#985473: slic3r: symbol lookup error after gcode export

2021-04-06 Thread Joe Pfeiffer
Hmmm, when I connect gdb to the process, I get an immediate

0x7f9480ca33ff in __GI___poll (fds=0x55943c327d50, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
29  ../sysdeps/unix/sysv/linux/poll.c: No such file or directory.

but am then able to proceed.  I set a breakpoint on

boost::nowide::setenv(char const*, char const*, int)@plt

and sliced AK_Bed.stl

gdb did halt on the breakpoint, and got
Thread 73 "perl" hit Breakpoint 1, 0x7f948024f700 in 
boost::nowide::setenv(char const*, char const*, int)@plt ()
   from /usr/lib/slic3r/auto/Slic3r/XS/XS.so
(gdb) where
#0  0x7f948024f700 in boost::nowide::setenv(char const*, char const*, 
int)@plt () at /usr/lib/slic3r/auto/Slic3r/XS/XS.so
#1  0x7f948045e2f9 in Slic3r::ConfigBase::setenv_() () at 
/usr/lib/slic3r/auto/Slic3r/XS/XS.so
#2  0x7f94803306b6 in  () at /usr/lib/slic3r/auto/Slic3r/XS/XS.so
#3  0x559436bc4047 in Perl_pp_entersub ()
#4  0x559436bba736 in Perl_runops_standard ()
#5  0x559436b1fc44 in Perl_call_sv ()
#6  0x7f94807d352a in  () at 
/usr/lib/x86_64-linux-gnu/perl/5.32/auto/threads/threads.so
#7  0x7f94807d4f6d in  () at 
/usr/lib/x86_64-linux-gnu/perl/5.32/auto/threads/threads.so
#8  0x7f9480d80ea7 in start_thread (arg=) at 
pthread_create.c:477
#9  0x7f9480caddef in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
(gdb) 

I just tried uninstalling and reinstalling it, with the same result.



Bug#985473: slic3r: symbol lookup error after gcode export

2021-03-18 Thread Joe Pfeiffer
Package: slic3r
Version: 1.3.0+dfsg1-3.2
Severity: important

Dear Maintainer,

When I export a gcode file, the file is created successfully, but
slic3r then prints

perl: symbol lookup error: /usr/lib/slic3r/auto/Slic3r/XS/XS.so: undefined 
symbol: _ZN5boost6nowide6setenvEPKcS2_i

to the terminal and terminates.

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (700, 'testing'), (650, 'stable'), (600, 'unstable'), (550, 
'experimental'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-4-amd64 (SMP w/8 CPU threads)
Kernel taint flags: 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 slic3r depends on:
ii  libboost-filesystem1.74.0  1.74.0-9
ii  libboost-geometry-utils-perl   0.15-2+b9
ii  libboost-thread1.74.0  1.74.0-9
ii  libc6  2.31-9
ii  libencode-locale-perl  1.05-1.1
ii  libexpat1  2.2.10-2
ii  libgcc-s1  10.2.1-6
ii  libio-stringy-perl 2.111-3
ii  libmath-convexhull-monotonechain-perl  0.1-1+b9
ii  libmath-geometry-voronoi-perl  1.3-3+b3
ii  libmath-planepath-perl 129-1
ii  libmoo-perl2.004004-1
ii  libstdc++6 10.2.1-6
pn  libstorable-perl   
ii  perl [libtime-hires-perl]  5.32.1-3
ii  perl-base [perlapi-5.32.0] 5.32.1-3

Versions of packages slic3r recommends:
ii  libclass-xsaccessor-perl  1.19-3+b7
ii  libio-all-perl0.87-1
ii  libopengl-perl0.7000+dfsg-5+b1
ii  libpdf-api2-perl  2.038-3
ii  libsvg-perl   2.85-1
ii  libwx-glcanvas-perl   0.09-5+b4
ii  libwx-perl1:0.9932-5+b5
ii  libxml-sax-expatxs-perl   1.33-2+b7

slic3r suggests no packages.

-- debconf-show failed



Bug#983031: konqueror segfaults on starting

2021-02-18 Thread Joe Rowan
Package: konqueror
Version: 4:20.12.0-4
Severity: normal

Dear Maintainer,

I have not used konqueror for probably more than a year. I ran it from the Xfce
menu and it would not start, with a missing file.
I ran 'apt reinstall konqueror', and six additional new packages were
installed.
Konqueror now starts but immediately segfaults.



>From konqueror error box:

Executable: konqueror PID: 5083 Signal: Segmentation fault (11) Time:
18/02/2021 11:19:41 GMT

>From terminal:

~$ konqueror
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = konqueror path = /usr/bin pid = 5167
KCrash: Arguments: /usr/bin/konqueror
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi

[1]+  Stopped konqueror
~$ QSocketNotifier: Invalid socket 11 and type 'Read', disabling...

[1]+  Exit 253konqueror


The file /usr/lib/x86_64-linux-gnu/libexec/drkonqi exists, root:root 755

The same error occurs if run with sudo.

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

Kernel: Linux 4.19.0-1-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages konqueror depends on:
ii  dolphin  4:20.12.2-1
ii  install-info 6.7.0.dfsg.2-6
ii  kio  5.78.0-4
ii  libc62.31-9
ii  libkf5archive5   5.78.0-2
ii  libkf5bookmarks5 5.78.0-2
ii  libkf5codecs55.78.0-2
ii  libkf5completion55.78.0-3
ii  libkf5configcore55.78.0-4
ii  libkf5configgui5 5.78.0-4
ii  libkf5configwidgets5 5.78.0-2
ii  libkf5coreaddons55.78.0-2
ii  libkf5crash5 5.78.0-3
ii  libkf5dbusaddons55.78.0-2
ii  libkf5i18n5  5.78.0-2
ii  libkf5iconthemes55.78.0-2
ii  libkf5itemviews5 5.78.0-2
ii  libkf5jobwidgets55.78.0-2
ii  libkf5kcmutils5  5.78.0-3
ii  libkf5kiocore5   5.78.0-4
ii  libkf5kiofilewidgets55.78.0-4
ii  libkf5kiogui55.78.0-4
ii  libkf5kiowidgets55.78.0-4
ii  libkf5konq6  4:20.12.0-4
ii  libkf5parts5 5.78.0-3
ii  libkf5service-bin5.78.0-2
ii  libkf5service5   5.78.0-2
ii  libkf5sonnetcore55.78.0-2
ii  libkf5sonnetui5  5.78.0-2
ii  libkf5textwidgets5   5.78.0-2
ii  libkf5wallet-bin 5.78.0-2
ii  libkf5wallet55.78.0-2
ii  libkf5widgetsaddons5 5.78.0-2
ii  libkf5windowsystem5  5.78.0-2
ii  libkf5xmlgui55.78.0-2
ii  libqt5core5a 5.15.2+dfsg-4
ii  libqt5dbus5  5.15.2+dfsg-4
ii  libqt5gui5   5.15.2+dfsg-4
ii  libqt5network5   5.15.2+dfsg-4
ii  libqt5printsupport5  5.15.2+dfsg-4
ii  libqt5webenginecore5 5.15.2+dfsg-3
ii  libqt5webenginewidgets5  5.15.2+dfsg-3
ii  libqt5widgets5   5.15.2+dfsg-4
ii  libqt5x11extras5 5.15.2-2
ii  libqt5xml5   5.15.2+dfsg-4
ii  libstdc++6   10.2.1-6

Versions of packages konqueror recommends:
ii  kfind  4:20.12.0-1

Versions of packages konqueror suggests:
pn  konq-plugins  



Bug#982047: wordwarvi

2021-02-08 Thread Joe Nahmias
Hi Ricardo,

Sorry, been afk for a few days...

On Sat, Feb 06, 2021 at 12:48:45PM +0100, Ricardo Mones wrote:
> control: tags -1 confirmed
> 
> Hi Joe,
> 
> On Sun, Jan 31, 2021 at 07:10:46PM -0500, Joe Nahmias wrote:
> > 
> > Indeed, fortuitous timing! He just tagged and closed your issue.Yes,
> > I'm familiar with packaging and at one point was the maintainer for
> > this package, so I should be okay ;)--Joe
> 
> Well, for the next time I'd suggest you to push your changes to salsa
> *before* uploading or at least *immediately after* uploading ;-)

Hmm, I did push to salsa -- I even see the tags there!
Ah, I see what happened. I was using the debian/master branch, but the
salsa repo default is just master. Do you have a preference one way or the
other?

> If you don't have the time or willingness to do it, just please push
> your pending git commits, I'd like to fix #982047 ASAP.

I can push/upload a fix for this tonight.

> Thanks in advance,
> -- 
>  Ricardo Mones
>  http://people.debian.org/~mones
>  «Everything will be just tickety-boo today.»

--Joe



Bug#981835: I am unable to resolve libelf1 violates Multi-Arch: same / unreproducible issue

2021-02-05 Thread Joe Irungu
Good day,

I am a debian bullseye/sid 64 bit user.When I ran the command apt update &&
apt upgrade today to update my packages i got message below

You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 libdw1:i386 : Depends: libelf1:i386 (= 0.182+20210203-1.1) but
0.182+20210203-1 is installed
 libelf1 : Breaks: libelf1:i386 (!= 0.182+20210203-1.1) but
0.182+20210203-1 is installed
 libelf1:i386 : Breaks: libelf1 (!= 0.182+20210203-1) but
0.182+20210203-1.1 is installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or
specify a solution).

When I ran the apt --fix-broken install I got messages below

Unpacking libelf1:i386 (0.182+20210203-1.1) over (0.182+20210203-1) ...
dpkg: error processing archive
/var/cache/apt/archives/libelf1_0.182+20210203-1.1_i386.deb (--unpack):
 trying to overwrite shared
'/usr/share/locale/en@boldquot/LC_MESSAGES/elfutils.mo',
which is different from other instances of package libelf1:i386
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

When I researched on this I stumbled onto your webpage
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981835 and solutions
provided dont work for me.

Kindly assist.

Best Regards


Bug#883138: fceux.desktop file causing huge logs in /var/log

2021-02-02 Thread Joe Nahmias
tags 883138 + moreinfo
thanks

Hello,

On Thu, Nov 30, 2017 at 12:45:14AM -0500, Eric Lynch wrote:
> Package: fceux
> Version: 2.2.2+dfsg0-1+b2
> Severity: normal
> 
> Dear Maintainer,
> 
>Hello,
> 
>  I installed FCEUX from the Debian Stretch repositories and soon after it
> started filling up my
>"messages", "syslog", and "user.log" logs files in /var/log. I noticed this
> evening that I was
> low on disk space and those three files were taking up over 200GB of 
> space.
> 
>  I used the tail command on those three files and noticed that it was
> filled with errors about trying
>   to parse the fceux.desktop file in /usr/share/applications.
> 
>  I managed to fix it by opening the fceux.desktop file and deleting
> everything below the
>   "Actions=Fullscreen;DefaultConfig;" line.
> 
> Once I did that, everything seems fine now.
> 
>Thank you

Sorry for the late reply -- I have just resumed maintenance of the fceux
package. Are you still experiencing this issue? If so, would you mind
trying the new version of fceux [2.3.0]?

Much appreciated,
--Joe



Bug#979363: update dovecot package?

2021-01-25 Thread Joe Nahmias
Hello dovecot folks,

Thanks for maintaining dovecot in Debian! I received an alert on my
dovecot-fts-xapian package that it is due to be removed from bullseye due
to security issues in the current dovecot package.

Just wanted to ask if there's anything I can do to help? I could try
updating the package to the latest upstream release, which should fix
those issues, but hesitate to do that without maintainer agreement. Given
the timing, I'd hate for dovecot not to be present when bullseye freezes.

Let me know,
--Joe



Bug#976668: Pan bug 976668

2020-12-25 Thread Joe
Many apologies, it turns out that this is a news server issue. I'm
still in credit there, but they have moved servers and clearly
something is not right yet.

Sorry for waste of time.

Joe



Bug#974211: metakernel's autopkg tests fail

2020-11-11 Thread Joe Nahmias
reassign 974211 bash 5.1~rc1-1
retitle 974211 bash 5.1rc1 emits bracketed paste escape sequences for dumb 
terminals
notfound 974211 bash/5.1~rc2-1
forwarded 974211 
https://lists.gnu.org/archive/html/bug-bash/2020-11/msg00017.html
affects 974211 metakernel
thanks

Hello,

Thanks for the report.  This is an issue with bash 5.1~rc1 and was fixed
in bash 5.1~rc2.  I note that it passed in debci when I retried after the
new version of bash migrated to testing:
https://ci.debian.net/data/autopkgtest/testing/amd64/m/metakernel/8078921/log.gz

--Joe



Bug#973300: lighttpd: wrong filename for php fpm socket

2020-10-28 Thread Joe Nahmias
Package: lighttpd
Version: 1.4.55-2
Severity: normal

Dear Maintainer,

Hello, the new 15-fastcgi-php-fpm.conf file has the wrong filename for
the PHP FPM socket file.  It should be /run/php/php-fpm.sock; not
/run/php/php-fpm.socket.

Thanks!
--Joe

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

Kernel: Linux 5.8.0-2-amd64 (SMP w/1 CPU thread)
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 lighttpd depends on:
ii  libattr1  1:2.4.48-5
ii  libbz2-1.01.0.8-4
ii  libc6 2.31-4
ii  libcrypt1 1:4.4.17-1
ii  libfam0   2.7.0-17.3
ii  libpcre3  2:8.39-13
ii  libssl1.1 1.1.1h-1
ii  lsb-base  11.1.0
ii  mime-support  3.64
ii  zlib1g1:1.2.11.dfsg-2

Versions of packages lighttpd recommends:
ii  perl5.30.3-4
ii  spawn-fcgi  1.6.4-2

Versions of packages lighttpd suggests:
pn  apache2-utils   
pn  lighttpd-doc
pn  lighttpd-mod-authn-gssapi   
pn  lighttpd-mod-authn-pam  
pn  lighttpd-mod-authn-sasl 
pn  lighttpd-mod-cml
pn  lighttpd-mod-geoip  
pn  lighttpd-mod-magnet 
pn  lighttpd-mod-maxminddb  
pn  lighttpd-mod-trigger-b4-dl  
pn  lighttpd-mod-vhostdb-dbi
pn  lighttpd-mod-vhostdb-pgsql  
pn  lighttpd-mod-webdav 
pn  lighttpd-modules-ldap   
pn  lighttpd-modules-mysql  
ii  openssl 1.1.1h-1
ii  php-cgi 2:7.4+76
ii  php-fpm 2:7.4+76
ii  php7.4-cgi [php-cgi]7.4.11-1
ii  php7.4-fpm [php-fpm]7.4.11-1
ii  rrdtool 1.7.2-3+b5



Bug#685506: debian-policy: Please add field Files-Excluded to machine readable copyright files definition

2020-10-25 Thread Joe Nahmias
Hello,

I really miss the mention of Files-Excluded in CF1.0 and when searching
found this bug.

On Fri, Feb 15, 2019 at 02:12:37PM -0700, Sean Whitton wrote:
> Hello,
> 
> Contrary to an older e-mail in this bug, the consensus among the Policy
> Editors is that we can add new, optional fields to the copyright-format
> spec without bumping its version number.  This is because the addition
> of optional fields is backwards compatible.
> 
> I have not read the whole thread, but a quick scan suggests that all we
> are waiting for here is for someone to write a patch against current
> Policy's master branch.

Is this truly the case that all that's needed is a new patch? Can we get
an official ACK from one of the policy editors? I'd be happy to re-write
the original patch to apply against HEAD if that's all that is required.

--Joe


signature.asc
Description: PGP signature


Bug#970228: nemo: Can no longer copy files

2020-09-15 Thread Joe
Should I mention again that I have this problem with Nautilus and
Thunar over Samba, with Xfce on sid, and there's not a trace of ZFS
anywhere in my network? It isn't just affecting ZFS.

-- 
Joe



Bug#970228: nemo: Can no longer copy files

2020-09-14 Thread Joe
Further info:

No problem copying the same file when logged into the host of the
shares, using mc (no GUI).

No problem copying the file via Samba from another workstation using
Unison.

Other people are not using Samba, so presumably the problem isn't with
Samba itself but the interface between graphical file managers and
Samba, and between them and zfs.

-- 
Joe



Bug#970326: firewall-config: after inputing root password, firewall-config throws an error unknownmethodexceptoin

2020-09-14 Thread Joe McEntire
Package: firewall-config
Version: 0.9.0-1
Severity: important
X-Debbugs-Cc: get...@live.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation? Launched firewall-config
   * What exactly did you do (or not do) that was effective (or
 ineffective)? relaunch
   * What was the outcome of this action? no effect
   * What outcome did you expect instead? working firewall-config for firewalld

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



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

Kernel: Linux 5.7.0-3-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_CRAP
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 firewall-config depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.36.0-1
ii  firewalld0.9.0-1
ii  gir1.2-glib-2.0  1.64.1-1
ii  gir1.2-gtk-3.0   3.24.23-1
ii  gir1.2-nm-1.01.26.2-1
ii  gir1.2-pango-1.0 1.46.1-1
ii  python3  3.8.2-3
ii  python3-dbus 1.2.16-3
ii  python3-firewall 0.9.0-1
ii  python3-gi   3.36.1-1

firewall-config recommends no packages.

firewall-config suggests no packages.

-- no debconf information


Bug#969620: packaging metakernel for Debian

2020-09-07 Thread Joe Nahmias
Hello,

Just wanted to drop you a note to thank you for creating the metakernel
and let you know that I'm planning on packaging it for the Debian
Gnu/Linux distribution (along with the Octave kernel that uses it).

Please do let me know if you have any questions / concerns!

Thanks again,
--Joe



Bug#870633: Regards

2020-09-06 Thread Peter Joe
-- 
Уважаемые,

Вы получили сообщение, которое я вам отправил?

С Уважением,
Питер Джо

Dear,

Did you receive the message i sent to you?

Regards,
Peter Joe


Bug#968050: unison-gtk: Latest version does not update menu correctly

2020-08-07 Thread Joe Rowan
Package: unison-gtk
Version: 2.48.4+2
Severity: normal

Dear Maintainer,



Since upgrading yesterday, Xfce panel launcher is not showing correct start
command or any icon.

Fixed by editing launcher to correct start command and adding icon.



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

Kernel: Linux 4.19.0-1-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages unison-gtk depends on:
ii  unison-2.48-gtk  2.48.4-6

unison-gtk recommends no packages.

Versions of packages unison-gtk suggests:
pn  unison-all-gtk  

-- no debconf information



Bug#780774: Peter Joe

2020-07-05 Thread Peter Joe
Dear,

Did you receive the message i sent to you?

Regards,
Peter Joe

親愛な、

私があなたに送ったメッセージを受け取りましたか?

よろしく、
ピータージョー


Bug#962284: mailman: File "/usr/lib/mailman/cron/cull_bad_shunt", line 77 SyntaxError with Python 3

2020-06-07 Thread Joe Pfeiffer
Dominic Hargreaves writes:
>
>Mailman 2 will never support python 3 and it has been removed from
>unstable and testing (see mailman3 for the future, but bear in mind it's
>very much not a transparent upgrade).

Yeah, the amount of work I anticipate for the switch is why I've been
procrastinating.  I wasn't aware it had been removed from unstable and
testing; it sounds like I'm going to have to bite the bullet sooner
rather than later

>That said, as far as I can tell even
>in unstable, /usr/bin/python is still pointing to /usr/bin/python2.7,
>so you must have manually changed the link in /usr/bin/python behind
>the packaging system's back?

At this point, update-alternatives lists python3 as the "auto"
alternative, so that appears to be the default (I'm nothing resembling
an expert on Debian policies or packaging, so it's entirely possible
I'm reading more into that than I should).

>It does appear to be a bug in this package that /usr/bin/python is used
>(Python policy says that /usr/bin/python2 must be used if the
>application requires a specific major version of python), but
>in practical terms it doesn't appear need fixing since the default isn't
>going to change in the stable releases.
>
>I've attached a trivial patch for completeness (which I prepared before
>I realised that there is no supported mechanism to actually switch
>/usr/bin/python that I can see) in case it's of help. If you're manually
>changing files in /usr/bin, you could of course just fix the scripts
>to specify /usr/bin/python2 by hand, though I don't recommend this
>approach.

That's what I've wound up doing (after filing the bug report, I found
several more scripts in mailman that also break with python3).
-- 
Joe Pfeiffer   575.525.2764 (H)
1440 Tierra del Sol Dr 575.496.3501 (C)
Las Cruces, NM 88007-5548  



Bug#962284: mailman: File "/usr/lib/mailman/cron/cull_bad_shunt", line 77 SyntaxError with Python 3

2020-06-05 Thread Joe Pfeiffer
Package: mailman
Version: 1:2.1.29-1+deb10u1
Severity: normal

Got the following this morning, after switching to Python 3:

From: r...@pfeifferfamily.net (Cron Daemon)
To: l...@pfeifferfamily.net
Subject: Cron  [ -x /usr/lib/mailman/cron/cull_bad_shunt ] && 
/usr/lib/mailman/cron/cull_bad_shunt
Date: Fri, 05 Jun 2020 04:30:01 -0600
Content-Type: text/plain; charset=UTF-8
X-Bogosity: Ham, tests=bogofilter, spamicity=0.28, version=1.2.4

  File "/usr/lib/mailman/cron/cull_bad_shunt", line 77
except getopt.error, msg:
   ^
SyntaxError: invalid syntax

The issue appears to be that Python3 no longer accepts the comma in an
except block.

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (700, 'testing'), (650, 'stable'), (600, 'unstable'), (550, 
'experimental'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages mailman depends on:
ii  apache2 [httpd]2.4.43-1
ii  cron [cron-daemon] 3.0pl1-136
ii  debconf [debconf-2.0]  1.5.74
ii  libc6  2.30-4
ii  logrotate  3.16.0-3
ii  lsb-base   11.1.0
ii  python 2.7.17-2
ii  python-dnspython   1.16.0-1
ii  ucf3.0038+nmu1

Versions of packages mailman recommends:
ii  exim4-daemon-light [mail-transport-agent]  4.93-15

Versions of packages mailman suggests:
pn  listadmin  
ii  lynx   2.9.0dev.5-1
pn  mailman3-full  
pn  spamassassin   

-- debconf information excluded



Bug#960308: RFP: python-vipaccess -- A FLOSS Symantec VIP Access application

2020-05-11 Thread Joe Nahmias
Package: wnpp
Severity: wishlist

* Package name: python-vipaccess
  Version : 0.13
  Upstream Author : Daniel Lenski 
* URL : https://github.com/dlenski/python-vipaccess
* License : Apache2
  Programming Lang: Python
  Description : A FLOSS Symantec VIP Access application

This package enables the user to generate a One-Time Password (OTP)
access token and register it with the Symantec VIP Access service. The
token can be saved to a local config file and thereafter used by the
program to generate OTPs based on the token. This token can also be used
with standard Two-Factor Authentication (2FA) clients to log into
services using the Symantec 2FA managed service.
.
It also includes a QR Code generator for easy integration
with OTP clients.



Bug#958529: RFP: routinator -- Routinator 3000 is RPKI Relying Party software

2020-04-23 Thread Joe Botha
Package: wnpp
Severity: wishlist

* Package name: routinator
  Version : 0.6.4
  Upstream Author : Name 
* URL : https://www.nlnetlabs.nl/projects/rpki/routinator/
* License : BSD
  Programming Lang: Rust
  Description : Routinator 3000 is free, open source RPKI Relying Party 
software

Routinator 3000 is RPKI Relying Party software, also known as an RPKI 
Validator. It is designed to have a small footprint and great portability.

Routinator 3000 connects to the Trust Anchors of the five Regional Internet 
Registries (RIRs) — APNIC, AFRINIC, ARIN, LACNIC and RIPE NCC — downloads all 
of the certificates and ROAs in the various repositories and validates the 
signatures. It can feed the validated information to hardware routers 
supporting Route Origin Validation such as Juniper, Cisco and Nokia, as well as 
serving software solutions like BIRD, OpenBGPD, GoBGP and VyOS. Alternatively, 
Routinator can output the validated data in a number of useful formats, such as 
CSV, JSON and RPSL.



Bug#417094: Peter Joe

2020-04-18 Thread Peter Joe
Dear,

Did you receive the message i sent to you?

Regards,
Peter Joe



Bug#955758: python3-more-itertools: incompatible upstream version 8.2.0

2020-04-04 Thread Joe Pfeiffer
Package: python3-more-itertools
Version: 4.2.0-1
Severity: important

Dear Maintainer,

This package upstream is at 8.2.0.  The order of operands for the
grouper recipe was changed in 6.0.0, so recent packages using it are
incompatible with this version

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (700, 'testing'), (650, 'stable'), (600, 'unstable'), (550, 
'experimental'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages python3-more-itertools depends on:
ii  python3  3.7.5-3
ii  python3-six  1.14.0-2

python3-more-itertools recommends no packages.

python3-more-itertools suggests no packages.

-- no debconf information



Bug#955267: gnome-calendar: 'All Day' events are displayed over mutliple days within the month when viewed in Week View.

2020-03-28 Thread Joe Aczel
Package: gnome-calendar
Version: 3.36.0-1
Severity: important
Tags: upstream

Dear Maintainer,

Please note that this bug has been reported upstream:
https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/550

I am currently using Debian Testing (Bullseye) with the latest gnome-
calendar (3.36). When viewing my events in Week mode, events that are stored as
'All Day' span backwards across the month. E.g. an event saved as 'All Day' for
the 3rd of March will appear on the 1st, 2nd and 3rd of March.

   * What led up to the situation?
1) Installed Debian Testing
2) Opened gnome-calendar
3) Switched to week view
4) Created a new event by clicking on a time slot
5) Edit Details...
6) Selected 'All Day' toggle
7) Selected the 3rd of April
7) Entered a Title
8) Selected 'Done'
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
- I have attempted creating new events at different times of different
months. The same outcome occurs: the event will be visible in week view from
the first day of the month until the day the event takes place.
   * What was the outcome of this action?
Within Week View, the event will take place from either the first day
of the month. If the first day of the month is not visible within the currently
viewed week, the event will seem to take place from the first day of the week
until the time the event takes place.
   * What outcome did you expect instead?
The event will appear only on the day that the event takes place.

Please be aware that I have only reported a few bugs before. If you need any
technical information please be specific as to how I should go about obtaining
it.
If this bug does not need to be reported because it has already been reported
upstream please let me know and I can remove this bug report.

Joe



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

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

Versions of packages gnome-calendar depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.36.0-1
ii  gsettings-desktop-schemas3.36.0-1
ii  libc62.30-2
ii  libcairo21.16.0-4
ii  libdazzle-1.0-0  3.36.0-1
ii  libecal-2.0-13.36.0-1
ii  libedataserver-1.2-243.36.0-1
ii  libedataserverui-1.2-2   3.36.0-1
ii  libgeoclue-2-0   2.5.6-1
ii  libglib2.0-0 2.64.1-1
ii  libgoa-1.0-0b3.36.0-1
ii  libgtk-3-0   3.24.14-1
ii  libgweather-3-16 3.36.0-1
ii  libhandy-0.0-0   0.0.13-2
ii  libical3 3.0.8-1
ii  libpango-1.0-0   1.42.4-8
ii  libpangocairo-1.0-0  1.42.4-8
ii  libsoup2.4-1 2.70.0-1

Versions of packages gnome-calendar recommends:
ii  evolution-data-server  3.36.0-1

gnome-calendar suggests no packages.

-- no debconf information



Bug#954800: baloo-kf5: baloo_file 5.62.0-2 (current testing) crashes on amd64 on database creation

2020-03-23 Thread Joe Kays
Package: baloo-kf5
Version: 5.62.0-2.1
Severity: important
Tags: newcomer

Dear Maintainer,

current version of baloo_file crashes on database creation on my amd64
(multiarch enabled) system.

The problem is that in engine/database.cpp line 139:

rc = mdb_env_open(..)

returns a non-zero exit code (12: out of memory).

This can be fixed by changing line 125:

size_t sizeInGByte = 256;

to

size_t sizeInGByte = 8;

If I remember correctly 9 was the highest working on my system with 16GB RAM
and ~5GB used (if that has anything to do with it).

I have absolutely no idea why this fixes the problem, but I hope someone else
does and this bug report helps. Thanks!

Best regards
Joe Kays



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (1000, 'testing'), (700, 'experimental'), (700, 'unstable'), 
(700, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de:en_GB 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages baloo-kf5 depends on:
ii  kio  5.62.1-2+b1
ii  libc62.30-2
ii  libkf5baloo5 5.62.0-2.1
ii  libkf5balooengine5   5.62.0-2.1
ii  libkf5configcore55.62.0-1+b1
ii  libkf5coreaddons55.62.0-1
ii  libkf5crash5 5.62.0-1+b1
ii  libkf5dbusaddons55.62.0-1
ii  libkf5filemetadata3  5.62.0-1+b1
ii  libkf5i18n5  5.62.0-1
ii  libkf5idletime5  5.62.0-1+b1
ii  libkf5kiocore5   5.62.1-2+b1
ii  libkf5solid5 5.62.0-2
ii  libqt5core5a 5.12.5+dfsg-9
ii  libqt5dbus5  5.12.5+dfsg-9
ii  libqt5gui5   5.12.5+dfsg-9
ii  libqt5qml5   5.12.5-5
ii  libqt5widgets5   5.12.5+dfsg-9
ii  libstdc++6   10-20200312-2

baloo-kf5 recommends no packages.

baloo-kf5 suggests no packages.

-- no debconf information



Bug#940696: please add drbdtop or keep drbd-overview

2020-02-08 Thread Joe Rayhawk
On Thu, 19 Sep 2019 08:24:46 +0200 Harald Dunkel  
wrote:
> Would it be possible to either *keep* drbd-overview (I am using it
> for monitoring) or to add drbdtop to Debian?

While not nearly as pleasant to work with as drbd-overview, drbdadm can
produce output marginally servicable for use in crontabs, including
uninitialized drbd resources.

set -o pipefail
/sbin/drbdadm sh-status | /usr/bin/pee \
  '! /bin/grep ^_cstate | /bin/grep -v Connected' \
  '! /bin/grep ^_peer   | /bin/grep -v Secondary' \
  '! /bin/grep ^_role   | /bin/grep -v Primary'   \
  '! /bin/grep ^_disk   | /bin/grep -v UpToDate'  \
  '! /bin/grep ^_pdsk   | /bin/grep -v UpToDate'
# /usr/bin/pee from the moreutils package



Bug#921904: Bug#946951: Bug#921904: win-iconv: FTBFS (wine: chdir to /tmp/wine-I6miLw/server-29-3583b06 : No such file or directory)

2019-12-28 Thread Joe Nahmias

On 12/27/2019 6:23 PM, Vincent Lefevre wrote:

On 2019-12-27 19:49:46 +, Joseph Nahmias wrote:

On Fri, Dec 27, 2019 at 07:27:42PM +, Joseph Nahmias wrote:

The attached patch works around the issue until that is fixed.


Of course, I forgot this patch... Take 2.


Wouldn't the use of wildcards be a security issue?

+   ln -s /tmp/.wine-`id -u`/server* /tmp/wine-*/

i.e. could you end up creating wrong symbolic links?


Attached is an updated patch that does the extra work to avoid the 
wildcards.



In any case, this seems rather ugly to me.


Not sure precisely what you are referring to as ugly here; but in my 
experience, band-aids are usually placed over something ugly, if that's 
what you mean... The proper fix would of course have to come from within 
wine itself.


--Joe
diff -Nru win-iconv-0.0.8/debian/changelog win-iconv-0.0.8/debian/changelog
--- win-iconv-0.0.8/debian/changelog2019-03-12 12:06:01.0 -0400
+++ win-iconv-0.0.8/debian/changelog2019-12-29 01:11:42.0 -0500
@@ -1,3 +1,12 @@
+win-iconv (0.0.8-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Work around #946951 by initializing WINEPREFIX and adding a symlink,
+closes: #921904.
+  * To speed up the build, don't install g++, only gcc is needed here.
+
+ -- Joe Nahmias   Sun, 29 Dec 2019 01:11:42 -0500
+
 win-iconv (0.0.8-3) unstable; urgency=medium
 
   * wrap-and-sort -ast
diff -Nru win-iconv-0.0.8/debian/control win-iconv-0.0.8/debian/control
--- win-iconv-0.0.8/debian/control  2019-03-12 12:06:01.0 -0400
+++ win-iconv-0.0.8/debian/control  2019-12-29 01:09:11.0 -0500
@@ -7,7 +7,7 @@
  debhelper-compat (= 12),
 Build-Depends-Indep:
  dpkg-dev (>= 1.17.14),
- mingw-w64,
+ gcc-mingw-w64,
  wine [i386 amd64]  ,
 Vcs-Git: https://salsa.debian.org/debian/win-iconv.git
 Vcs-Browser: https://salsa.debian.org/debian/win-iconv
diff -Nru win-iconv-0.0.8/debian/rules win-iconv-0.0.8/debian/rules
--- win-iconv-0.0.8/debian/rules2019-03-12 11:29:02.0 -0400
+++ win-iconv-0.0.8/debian/rules2019-12-29 01:03:56.0 -0500
@@ -3,11 +3,13 @@
 # we do not want stackprotector because there is no implementation on mingw32:
 export DEB_BUILD_MAINT_OPTIONS = hardening=-stackprotector
 
+DEB_BUILD_ARCH ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH)
 ifeq ($(DEB_BUILD_ARCH),i386)
   TESTARCH=i686-w64-mingw32
 else ifeq ($(DEB_BUILD_ARCH), amd64)
   TESTARCH=x86_64-w64-mingw32
 endif
+export WINEPREFIX := $(CURDIR)/build-$(TESTARCH)/.wine
 
 %:
dh $@
@@ -30,9 +32,17 @@
  cd .. ; \
done
 
+override_dh_auto_test: T := $(CURDIR)/build-$(TESTARCH)/tmp
 override_dh_auto_test:
 ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
 ifdef TESTARCH
-   cd build-$(TESTARCH) && WINEPREFIX=$(shell pwd)/build-$(TESTARCH)/.wine 
$(MAKE) CC=$(TESTARCH)-gcc AR=$(TESTARCH)-ar RANLIB=$(TESTARCH)-ranlib 
DLLTOOL=$(TESTARCH)-dlltool test
+   -wineboot -i
+   mkdir -p $(T)/`cat "${WINEPREFIX}/wineserver"`/
+   -ln -s /tmp/.wine-`id -u`/$$( \
+   printf "server-%x-%x" `stat --printf="%d %i" "${WINEPREFIX}"` \
+ ) $(T)/`cat "${WINEPREFIX}/wineserver"`/
+   $(MAKE) -C build-$(TESTARCH) CC=$(TESTARCH)-gcc AR=$(TESTARCH)-ar \
+   RANLIB=$(TESTARCH)-ranlib DLLTOOL=$(TESTARCH)-dlltool \
+   TMPDIR=$(T) test
 endif
 endif


Bug#606825: mingw-w64 triplets/ostable

2019-12-26 Thread Joe Nahmias

Greetings!

I recently became interested in cross-compiling software from Debian to 
Windows. To my delight, I found the gcc-mingw-w64 & mingw-w64-tools 
packages already in Debian (thanks Stephen!). However, I see that they 
are using a workaround of a /usr/${triplet}/ path, rather than multi-arch.


Then found and read through this bug which hasn't seen an update in 5+ 
years :(  Meanwhile, the Windows world has changed quite a bit in that 
time, with Windows 10 being released in 2015, and Windows 7 due to go 
EOL on 2020-01-14.


So, how can I best help the effort to get a proper multi-arch 
infrastructure in Debian appropriate from cross-building using mingw-w64?


On 9/15/2014 11:46 AM, Guillem Jover wrote:

Hi!

On Tue, 2014-09-09 at 23:28:10 +0200, Stephen Kitt wrote:

On Sat, 30 Aug 2014 15:51:12 +0200, Guillem Jover  wrote:

But I just noticed that a proper triplet was accepted in the config.git
repo around 2012 (commit f16804b79ee5a23a9994a1cdc760cd9ba813148a), this
is what config.sub has to say:

   $ /usr/share/misc/config.sub mingw64
   x86_64-pc-mingw64
   $ /usr/share/misc/config.sub x86_64-mingw64
   x86_64-pc-mingw64
   $ /usr/share/misc/config.sub i686-mingw64
   i686-pc-mingw64

So, just one thought, if you are going to end up having to do the work
that would be required to add support for what amounts to the equivalent
of a new triplet, you could as well use a proper triplet, like the one
above?


That triplet was actually added by the MinGW project, not the MinGW-w64
project, and is intended for their putative 64-bit support, whenever that
appears;


Oh wow, even more confusion to the already confusing current situation.
I assume we cannot expect the mingw-w64 and the mingw64 ports to be ABI
compatible? :(


I'll take it up with MinGW-w64 upstream though and see what they make of it.


Thanks, that might help.


Did this conversation happen? Was there any result?


In the end it seems to me that as long as the triplet is officially
supported by config.sub/guess the rest of software should just follow
suit, which as mentioned before is what needs to be done for each and
every new architecture anyway. What might be more time consuming is
hunting down and updating the rest of the affected packages in Debian,
but given that this has been thought to be a partial architecture from
the beginning it should not amount to so many packages (in contrast to
a full fledged architecture, that is).


I think what will be time-consuming is getting the various required patches
into the various upstream projects; there are very few affected packages in
Debian. Unless you mean we should just go our own way, regardless of what
upstream thinks, and use the mingw64 which is already in config.sub and patch
whatever breaks?


Well, not really if that would mean making the situation even worse by
conflating what might end up being upstream projects tripping over
each other's triplets. (Sorry, this was not clear from the aforementioned
commit.)


I'd rather do the work required to get something supported properly in Debian
and by upstream...


Sure.

Thanks,
Guillem


Thanks,
--Joe



Bug#941988: libncurses-dev: Please package libncurses_g

2019-10-08 Thread Joe Pfeiffer
Package: libncurses-dev
Version: 6.1+20190803-1
Severity: wishlist

I'm tracking down a bug in a program of mine, which is either a
regression in the current version of libncurses-dev or a bug in my
code which has been exposed by the current version.  It would be very
helpful to me to be able to use the trace() function, to see the
activity of the library.  This is documented as requiring a program to
be linked against libncurses_g (instead of libncurses); so far as I've
been able to find this library is not currently packaged, so I'll need
to rebuild from source.  I'd appreciate it if it could be packaged.

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (700, 'testing'), (650, 'stable'), (600, 'unstable'), (550, 
'experimental'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages libncurses-dev depends on:
ii  libc6-dev [libc-dev]  2.29-2
ii  libncurses6   6.1+20190803-1
ii  libncursesw6  6.1+20190803-1
ii  libtinfo6 6.1+20190803-1
ii  ncurses-bin   6.1+20190803-1

libncurses-dev recommends no packages.

Versions of packages libncurses-dev suggests:
ii  ncurses-doc  6.1+20190803-1

-- no debconf information



Bug#940627: ffmpegthumbnailer Rotation metadata ignored

2019-09-17 Thread Joe Dupuis
Package: ffmpegthumbnailer
Version: 2.1.1-0.1+b3
Severity: normal

Hi,
The version of ffmpegthumbnailer on debian ignore rotation metadata.
This is problematic when dealing with video filmed on a smartphone.
A fix for it have been pushed upstream in version 2.1.2 (debian is at 2.1.1).

Thank you,

Joe

-- System Information:
Debian Release: 9.6
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-8-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ffmpegthumbnailer depends on:
ii  libc62.24-11+deb9u4
ii  libffmpegthumbnailer4v5  2.1.1-0.1+b3
ii  libgcc1  1:6.3.0-18+deb9u1
ii  libstdc++6   6.3.0-18+deb9u1

ffmpegthumbnailer recommends no packages.

Versions of packages ffmpegthumbnailer suggests:
ii  libglib2.0-0  2.50.3-2

-- no debconf information



Bug#933153: linux-image-4.19.0-5-amd64: soft lockup cpu stuck

2019-07-26 Thread Joe B. McEntire
Package: src:linux
Version: 4.19.37-5+deb10u1
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?  Time
   * What exactly did you do (or not do) that was effective (or
 ineffective)? It was after upgrading to Buster, I changed kernel boot
params removing kvm stuff for gpu passthough, etc
   * What was the outcome of this action? Ranges from minor annoyance to making
applications like games crash
   * What outcome did you expect instead? stability :)

Error generally looks like:
Message from syslogd@master at Jul 26 12:56:02 ...
 kernel:[226137.665230] watchdog: BUG: soft lockup - CPU#17 stuck for 23s!
[libvirtd:7893]

Message from syslogd@master at Jul 26 12:56:02 ...
 kernel:[226137.681225] watchdog: BUG: soft lockup - CPU#23 stuck for 23s!
[kworker/23:0:6856]

Message from syslogd@master at Jul 26 12:56:30 ...
 kernel:[226165.665295] watchdog: BUG: soft lockup - CPU#17 stuck for 23s!
[libvirtd:7893]

Message from syslogd@master at Jul 26 12:56:30 ...
 kernel:[226165.681289] watchdog: BUG: soft lockup - CPU#23 stuck for 23s!
[kworker/23:0:6856]

I run 2 Xeon E5-2620 CPUs in this system with 64GB RAM

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



-- Package-specific info:
** Version:
Linux version 4.19.0-5-amd64 (debian-ker...@lists.debian.org) (gcc version 
8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.37-5+deb10u1 (2019-07-19)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.19.0-5-amd64 root=/dev/mapper/System-root ro quiet 
splash apparmor=1 security=apparmor

** Tainted: PWOEL (29185)
 * Proprietary module has been loaded.
 * Taint on warning.
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded.
 * Kernel has detected soft lockup before.

** Kernel log:
[226169.517462] CR2: 7f073877b010 CR3: 001030912002 CR4: 
000626f0
[226169.517464] Call Trace:
[226169.517475]  ? flush_tlb_func_common.constprop.9+0x210/0x210
[226169.517478]  flush_tlb_mm_range+0xd0/0x120
[226169.517483]  arch_tlb_finish_mmu+0xbd/0x100
[226169.517486]  tlb_finish_mmu+0x1f/0x30
[226169.517488]  unmap_region+0xdd/0x110
[226169.517492]  do_munmap+0x27f/0x430
[226169.517495]  vm_munmap+0x5f/0xa0
[226169.517498]  __x64_sys_munmap+0x22/0x30
[226169.517503]  do_syscall_64+0x53/0x110
[226169.517510]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[226169.517513] RIP: 0033:0x7f0786a6e1d7
[226169.517514] Code: 10 e9 67 ff ff ff 0f 1f 44 00 00 48 8b 15 b1 6c 0c 00 f7 
d8 64 89 02 48 c7 c0 ff ff ff ff e9 6b ff ff ff b8 0b 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d 89 6c 0c 00 f7 d8 64 89 01 48
[226169.517515] RSP: 002b:7fffb6091068 EFLAGS: 0202 ORIG_RAX: 
000b
[226169.517517] RAX: ffda RBX: 063f RCX: 
7f0786a6e1d7
[226169.517518] RDX: 55f136255a60 RSI: 0004 RDI: 
7f06ee93e000
[226169.517519] RBP: 7f06ed704050 R08: 55f136255a60 R09: 
7f073877b000
[226169.517520] R10: 0040 R11: 0202 R12: 
55f1352162f0
[226169.517521] R13: 0006 R14:  R15: 

[226179.485519] nfs: server storage not responding, timed out
[226184.349339] [ cut here ]
[226184.349345] NETDEV WATCHDOG: enp6s0f0 (igb): transmit queue 1 timed out
[226184.349376] WARNING: CPU: 16 PID: 0 at net/sched/sch_generic.c:461 
dev_watchdog+0x20d/0x220
[226184.349377] Modules linked in: vhost_net vhost tap tun rfcomm devlink 
rpcsec_gss_krb5 nfsv4 dns_resolver nfs lockd grace fscache 
nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT xt_tcpudp ip6t_rpfilter 
ip6t_REJECT nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 xt_conntrack nft_counter 
nft_chain_nat_ipv6 nf_nat_ipv6 nft_chain_route_ipv6 bridge stp llc 
nft_chain_nat_ipv4 nf_nat_ipv4 nf_nat nft_chain_route_ipv4 nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 ip6_tables nft_compat ip_set nf_tables nfnetlink 
bnep binfmt_misc nls_ascii nls_cp437 vfat fat snd_hda_codec_hdmi intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel intel_cstate vfio_pci vfio_virqfd 
vfio_iommu_type1 vfio irqbypass nvidia_drm(POE) drm_kms_helper btusb btrtl 
btbcm btintel
[226184.349442]  intel_uncore bluetooth drm snd_hda_codec_realtek efi_pstore 
intel_rapl_perf snd_hda_codec_generic efivars pcspkr nvidia_modeset(POE) 
uvcvideo drbg joydev videobuf2_vmalloc ansi_cprng videobuf2_memops 
videobuf2_v4l2 snd_usb_audio videobuf2_common ecdh_generic videodev 
snd_hda_intel snd_usbmidi_lib snd_hda_codec snd_rawmidi rfkill snd_seq_device 
media snd_hda_core iTCO_wdt snd_hwdep iTCO_vendor_support snd_pcm snd_timer snd 
mei_me sg mei soundcore ioatdma uinput pcc_cpufreq evdev nvidia(POE) 
ipmi_devintf ipmi_msghandler auth_rpcgss sunrpc parport_pc ppdev lp parport 
efivarfs ip_tables x_tables autofs4 ext4 hid_steam crc16 mbcache jbd2 fscrypto 
ecb dm_mod sr_mod sd_mod cdrom btrfs xor zstd_dec

Bug#931290: general: Asrock A300 Deskmini AMD Athlon 200GE ends in black screen Monitor has no Signal

2019-07-12 Thread Joe Lobeck


Dear Mantainer, 

in the meantime I found that the most things work form kernel 5.0 or higher.
Unfortunately so I will have to choose an other linux distribution as such a 
kernel
is for debian only from the experimantal repository avaiable.
If you have any other idea how to make debian stable or testing run with this 
hardware please let me know.

Kind regards,

Joe

Quoting joe :

> Package: general
> Severity: important
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate
> ***
> 
>* What led up to the situation?
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>* What was the outcome of this action?
>* What outcome did you expect instead?
> 
> *** End of the template - remove these template lines ***
> 
> After normal installation of Debian Buster (Testing) with Default desktop
> the
> grub screen comes up and the system boots. When it normally switches to
> graphics mode it shows only a blinking cursor.
> After installing firmware-linux and rebooting the system does not show the
> blinking server, but a black screen and the monitor shows "No signal".
> Tested with 3 monitors.
> Afterwards reinstalled without "Default desktop".
> Now the system started ok and ended in the login.
> After installing firmware-linux unfortunately the system did not show the
> login
> after booting, but ended once again in a black screen (no Monitor signal).
> With
> nomodeset in grub I could start, but had to press "Ctrl + alt + F2" to go
> in
> the login as the system stopped after initializing the network card.
> So graphical interface is not possible with this hardware configuration and
> Debian 10 Buster.
> Normally Kernel 4.19... should be good enough for Vega 3 graphics. Live
> system
> (LXDE) fails as well with blinking cursor. "Lubuntu 19.04" does the job,
> but I
> do not like it and would appreciate if I could stay with Debian.
> 
> 
> 
> 
> -- System Information:
> Debian Release: 9.9
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.9.0-9-amd64 (SMP w/4 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
> LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>





Bug#931290: general: Asrock A300 Deskmini AMD Athlon 200GE ends in black screen Monitor has no Signal

2019-06-30 Thread joe
Package: general
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

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

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

After normal installation of Debian Buster (Testing) with Default desktop the
grub screen comes up and the system boots. When it normally switches to
graphics mode it shows only a blinking cursor.
After installing firmware-linux and rebooting the system does not show the
blinking server, but a black screen and the monitor shows "No signal".
Tested with 3 monitors.
Afterwards reinstalled without "Default desktop".
Now the system started ok and ended in the login.
After installing firmware-linux unfortunately the system did not show the login
after booting, but ended once again in a black screen (no Monitor signal). With
nomodeset in grub I could start, but had to press "Ctrl + alt + F2" to go in
the login as the system stopped after initializing the network card.
So graphical interface is not possible with this hardware configuration and
Debian 10 Buster.
Normally Kernel 4.19... should be good enough for Vega 3 graphics. Live system
(LXDE) fails as well with blinking cursor. "Lubuntu 19.04" does the job, but I
do not like it and would appreciate if I could stay with Debian.




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

Kernel: Linux 4.9.0-9-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



Bug#931014: Solved

2019-06-24 Thread Joe McEntire
This was solved by:

apt autoremove virt-manager --purge

apt install virt-manager

I do not see this issue on my laptop. I think it was a fluke issue.

Please disregard!

Thanks for your time,

Joe
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


Bug#931014: virt-manager: Virt-manager crashed when attempting to create new VM.

2019-06-24 Thread Joe B. McEntire
Package: virt-manager
Version: 1:2.0.0-3
Severity: important

Dear Maintainer,

   * What led up to the situation?  Attempted to create a new VM
   * What exactly did you do (or not do) that was effective (or
 ineffective)? Clicked the new VM button
   * What was the outcome of this action?  Virt-manager crashed
   * What outcome did you expect instead? VM creation wizard comes up and
works.

Here's the output of the console during the crash:

[Mon, 24 Jun 2019 10:39:53 virt-manager 21406] DEBUG (create:200) Showing new
vm wizard
[Mon, 24 Jun 2019 10:39:53 virt-manager 21406] DEBUG (create:695) Guest type
set to os_type=hvm, arch=x86_64, dom_type=kvm

(virt-manager:21406): GLib-GIO-ERROR **: 10:39:53.289: Settings schema
'org.virt-manager.virt-manager.urls' does not contain a key named 'containers'

There is not further output past this point.

My system is an upgrade from Debian Stretch to Debian Buster.



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

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

Versions of packages virt-manager depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  gir1.2-gtk-3.0   3.24.5-1
ii  gir1.2-gtk-vnc-2.0   0.9.0-1.1
ii  gir1.2-libosinfo-1.0 1.2.0-1
ii  gir1.2-libvirt-glib-1.0  1.0.0-1
ii  gir1.2-vte-2.91  0.54.2-2
ii  librsvg2-common  2.44.10-2.1
ii  python-requests  2.21.0-1
ii  python3  3.7.3-1
ii  python3-dbus 1.2.8-3
ii  python3-gi   3.30.4-1
ii  python3-gi-cairo 3.30.4-1
ii  python3-libvirt  5.0.0-1
ii  virtinst 1:2.0.0-3

Versions of packages virt-manager recommends:
ii  gir1.2-spiceclientglib-2.0  0.35-2
ii  gir1.2-spiceclientgtk-3.0   0.35-2
ii  libvirt-daemon-system   5.0.0-3

Versions of packages virt-manager suggests:
ii  gir1.2-secret-10.18.7-1
ii  gnome-keyring  3.28.2-5
ii  ksshaskpass [ssh-askpass]  4:5.14.5-1
pn  python3-guestfs
ii  virt-viewer7.0-2

-- no debconf information



Bug#929941: [INTL:da] Danish translation of the template debian-security-support

2019-06-03 Thread Joe Dalton
Package: debian-security-support
Severity: wishlist
Tags: l10n patch

Please include the attached Danish debian-security-support translation

joe@debianbuster:~/over/debianp/debian-security-support$ msgfmt --statistics -c 
-v -o /dev/null da.po
da.po: 21 oversatte tekster.

bye
Joe

da.po.tar.bz2
Description: application/bzip


Bug#925612: psi-plus: the following option is always enabled:option/messages/chat/raise chat window on receiving new messages

2019-03-27 Thread joe
Package: psi-plus
Version: 1.4.554-1~bpo9+1
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

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

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



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

Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages psi-plus depends on:
ii  libc6 2.24-11+deb9u4
ii  libgcc1   1:6.3.0-18+deb9u1
ii  libhunspell-1.4-0 1.4.1-2+b2
ii  libidn11  1.33-1
ii  libminizip1   1.1-8+b1
ii  libqca-qt5-2  2.1.1-4+b2
ii  libqca-qt5-2-plugins  2.1.1-4+b2
ii  libqt5concurrent5 5.7.1+dfsg-3+deb9u1
ii  libqt5core5a  5.7.1+dfsg-3+deb9u1
ii  libqt5dbus5   5.7.1+dfsg-3+deb9u1
ii  libqt5gui55.7.1+dfsg-3+deb9u1
ii  libqt5keychain1   0.7.0-3
ii  libqt5network55.7.1+dfsg-3+deb9u1
ii  libqt5sql55.7.1+dfsg-3+deb9u1
ii  libqt5sql5-sqlite 5.7.1+dfsg-3+deb9u1
ii  libqt5svg55.7.1~20161021-2+b2
ii  libqt5widgets55.7.1+dfsg-3+deb9u1
ii  libqt5x11extras5  5.7.1~20161021-2
ii  libqt5xml55.7.1+dfsg-3+deb9u1
ii  libstdc++66.3.0-18+deb9u1
ii  libx11-6  2:1.6.4-3+deb9u1
ii  psi-plus-common   1.4.554-1~bpo9+1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages psi-plus recommends:
ii  psi-plus-l10n 0.16.330-1
ii  psi-plus-plugins  1.4.554-1~bpo9+1
ii  psi-plus-sounds   0.16.330-1.3
ii  sox   14.4.1-5+deb9u1

Versions of packages psi-plus suggests:
ii  xdg-utils  1.1.1-1+deb9u1

-- no debconf information



Bug#925611: psi-plus-plugins: otr fails. looks like session starts to initiate but plugin does not "catch" key exchange.

2019-03-27 Thread joe
Package: psi-plus-plugins
Version: 1.4.554-1~bpo9+1
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

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

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



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

Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages psi-plus-plugins depends on:
ii  libc6  2.24-11+deb9u4
ii  libgcc11:6.3.0-18+deb9u1
ii  libgcrypt201.7.6-2+deb9u3
ii  libotr54.1.1-2
ii  libqt5core5a   5.7.1+dfsg-3+deb9u1
ii  libqt5dbus55.7.1+dfsg-3+deb9u1
ii  libqt5gui5 5.7.1+dfsg-3+deb9u1
ii  libqt5network5 5.7.1+dfsg-3+deb9u1
ii  libqt5printsupport55.7.1+dfsg-3+deb9u1
ii  libqt5sql5 5.7.1+dfsg-3+deb9u1
ii  libqt5widgets5 5.7.1+dfsg-3+deb9u1
ii  libqt5x11extras5   5.7.1~20161021-2
ii  libqt5xml5 5.7.1+dfsg-3+deb9u1
ii  libsignal-protocol-c2  2.3.1+git20171007-3~bpo9+1
ii  libssl1.1  1.1.0j-1~deb9u1
ii  libstdc++6 6.3.0-18+deb9u1
ii  libtidy5   1:5.2.0-2
ii  libx11-6   2:1.6.4-3+deb9u1
ii  libxcb11.12-1
ii  psi-plus   1.4.554-1~bpo9+1

psi-plus-plugins recommends no packages.

psi-plus-plugins suggests no packages.

-- no debconf information



Bug#917738: patch

2019-03-09 Thread Joe Lee
tag 917738 + patch
thanks

Hi, here's a patch for bug #917738 that I extracted from upstream.
Description: remove WebServiceException
Origin: upstream, https://github.com/OpenHFT/Chronicle-Threads/commit/bb1d4edfc7a783ebdc7c58bfc2f278f665e2539e#diff-e5af304c7efa4fec7930553b2fab754b
Index: openhft-chronicle-threads-1.1.6/src/main/java/net/openhft/chronicle/threads/MonitorEventLoop.java
===
--- openhft-chronicle-threads-1.1.6.orig/src/main/java/net/openhft/chronicle/threads/MonitorEventLoop.java
+++ openhft-chronicle-threads-1.1.6/src/main/java/net/openhft/chronicle/threads/MonitorEventLoop.java
@@ -25,7 +25,6 @@ import org.jetbrains.annotations.NotNull
 import org.slf4j.Logger;
 import org.slf4j.LoggerFactory;
 
-import javax.xml.ws.WebServiceException;
 import java.io.Closeable;
 import java.util.ArrayList;
 import java.util.List;
@@ -120,7 +119,8 @@ public class MonitorEventLoop implements
 }
 
 @Override
-public void close() throws WebServiceException {
+public void close() {
+stop();
 service.shutdown();
 try {
 if (!service.awaitTermination(100, TimeUnit.MILLISECONDS))


Bug#923064: [INTL:da] Danish translation of the debconf templates wireshark

2019-02-27 Thread Joe Dalton
of course sorry about that



Den tirs 26/2/19 skrev Balint Reczey :

 Emne: Re: Bug#923064: [INTL:da] Danish translation of the debconf templates 
wireshark
 Til: "Joe Dalton" , 923...@bugs.debian.org
 Dato: tirsdag 26. februar 2019 17.43
 
 Control: tags -1 moreinfo
 
 Hi Joe,
 
 On
 Sat, Feb 23, 2019 at 8:00 PM Joe Dalton 
 wrote:
 >
 > Package:
 wireshark
 > Severity: wishlist
 > Tags: l10n patch
 >
 > Please include the attached Danish
 wireshark debconf po file.
 >
 > joe@debianbuster:~/over/debian/wireshark$
 msgfmt --statistics -c -v -o /dev/null da.po
 > da.po: 16 oversatte tekster.
 
 This looks like the po file
 for apt-listchanges. Could you please
 attach
 the one for wireshark?
 
 Cheers,
 Balint
 
 
 -- 
 Balint Reczey
 Ubuntu &
 Debian Developer

da.po.tar.gz
Description: application/gzip


Bug#923145: [INTL:da] Danish translation of the debconf template cltl

2019-02-24 Thread Joe Dalton
Package: cltl
Severity: wishlist
Tags: l10n patch

Please include the attached Danish cltl debconf po file.

joe@debianbuster:~/over/debian/cltl$ msgfmt --statistics -c -v -o /dev/null 
da.po
da.po: 4 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip


Bug#923144: [INTL:da] Danish translation of the debconf template lyskom-server

2019-02-24 Thread Joe Dalton
Package: lyskom-server
Severity: wishlist
Tags: l10n patch

Please include the attached Danish lyskom-server debconf po file.

joe@debianbuster:~/over/debian/lyskom-server$ msgfmt --statistics -c -v -o 
/dev/null da.po
da.po: 11 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip


Bug#923143: [INTL:da] Danish translation of the debconf template diaspora-installer

2019-02-24 Thread Joe Dalton
Package: diaspora-installer
Severity: wishlist
Tags: l10n patch

Please include the attached Danish diaspora-installer debconf po file.

joe@debianbuster:~/over/debian/diaspora-installer$ msgfmt --statistics -c -v -o 
/dev/null da.po
da.po: 45 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip


Bug#923138: [INTL:da] Danish translation of the debconf template keystone

2019-02-24 Thread Joe Dalton
Package: keystone
Severity: wishlist
Tags: l10n patch

Please include the attached Danish keystone debconf po file.

joe@debianbuster:~/over/debian/keystone$ msgfmt --statistics -c -v -o /dev/null 
da.po
da.po: 28 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip


Bug#923136: [INTL:da] Danish translation of the debconf template openstack-pkg-tools

2019-02-24 Thread Joe Dalton
Package: openstack-pkg-tools
Severity: wishlist
Tags: l10n patch

Please include the attached Danish openstack-pkg-tools debconf po file.

joe@debianbuster:~/over/debian/openstack-pkg-tools$ msgfmt --statistics -c -v 
-o /dev/null da.po
da.po: 53 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip


Bug#923134: [INTL:da] Danish translation of the debconf template miniupnpd

2019-02-24 Thread Joe Dalton
Package: miniupnpd
Severity: wishlist
Tags: l10n patch

Please include the attached Danish miniupnpd debconf po file.

joe@debianbuster:~/over/debian/miniupnpd$ msgfmt --statistics -c -v -o 
/dev/null da.po
da.po: 13 oversatte tekster.


bye
Joe

da.po.tar.gz
Description: application/gzip


Bug#923132: [INTL:da] Danish translation of the debconf template horizon

2019-02-24 Thread Joe Dalton
Package: horizon
Severity: wishlist
Tags: l10n patch

Please include the attached Danish horizon debconf po file.

joe@debianbuster:~/over/debian/horizon$ msgfmt --statistics -c -v -o /dev/null 
da.po
da.po: 10 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip


Bug#923130: [INTL:da] Danish translation of the debconf template neutron

2019-02-24 Thread Joe Dalton
Package: neutron
Severity: wishlist
Tags: l10n patch

Please include the attached Danish neutron debconf po file.

joe@debianbuster:~/over/debian/neutron$ msgfmt --statistics -c -v -o /dev/null 
da.po
da.po: 16 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip


  1   2   3   4   5   6   7   8   9   10   >