Bug#1069642: linux-image-6.1.0-20-amd64: kernel panic after 2024-04-20

[Damian]

Same problem here, but with a different call trace. The RIP logline had 
one of `security_file_permission` and `security_netlink_send`, I don't 
remember which one.

Bug#1059744: spamassassin-maintenance does not invoke amavisd-new update-hook

[Damian]

Package: spamassassin
Version: 4.0.0-7

The fix for #1028030 introduced a regression for amavisd-new. Its hook [1] is 
never run as long as spamd is not installed.

I'd also like an opinion on a related issue: When spamd is running but amavisd-new is not, spamassassin-maintenance.service fails 
by virtue of [1] failing with a dedicated exit code. Would you like to consider this a spamassassin or an amavisd-new bug?


[1] /etc/spamassassin/sa-update-hooks.d/amavisd-new

Bug#1056658: Regex too greedy on multiple encoded names

[Damian]

Package: libmail-message-perl
Version: 3.012-1

The version in Debian Bookworm is affected by [1], which has been fixed 
upstream in 3.013.


[1] https://github.com/markov2/perl5-Mail-Message/issues/5

Bug#819341: [unison] Please build unison-fsmonitor

[Damian Lukowski]

Please consider 
https://salsa.debian.org/ocaml-team/unison/-/merge_requests/2

Bug#1043424: plasma-desktop: Missing dependency on pipewire breaks screen sharing under Wayland

[Lisandro Damian Nicanor Perez Meyer]

severity 1043424 normal
thanks

Hi!

On jueves, 10 de agosto de 2023 15:19:04 -03 Nazar Zhuk wrote:
> Package: plasma-desktop
> Version: 4:5.27.5-2
> Severity: important
> X-Debbugs-Cc: nazar@zhuk.online
> 
> Dear Maintainer,
> 
>* What led up to the situation?
>I attempted screen sharing in Zoom on a fresh install of Debian 12
>with KDE Plasma under Wayland.
> 
>* What was the outcome of this action?
>KDE window allowed me to pick a screen or a window to share. It did
>not show previews. Upon selection the error was shown:
>KDE Portal Integration
>Failed to start screencasting
>Failed to create PipeWire context
> 
>* What outcome did you expect instead?
>I expected the screen/window to be shared.
> 
> I tested screen capture in
> https://mozilla.github.io/webrtc-landing/gum_test.html to make sure this
> isn't a Zoom issue. Same outcome.
> 
> After some searching and digging the issue appears to be that pipewire
> was not installed.
> 
> This fixed the problem:
> 
> sudo apt install pipewire
> systemctl --user start pipewire
> 
> pipewire should be a dependency of plasma-desktop or one of it's
> dependencies so this works out of the box.
> 
> Marking this as important since screen sharing is a must for a desktop OS
> in business.

I can agree that something in Plasma should depend/recommend xdg-desktop-
portal-kde.  But neither KDE+Wayland nor pipewire are defaults for Debian, so 
users wanting to use them are expected to do some work. Granted, it would be 
just awesome if no action would be required, but that is sadly not the case 
here. I am so downgrading this bug to normal.

I would argue that this bug should be retitled to only care about the xdg-
desktop-portal-kde package.

Kinds regards, Lisandro.





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

Bug#1040496: qt6-virtualkeyboard FTBFS with parallel=1: qmlcachegen segfaults

[Lisandro Damian Nicanor Perez Meyer]

severity 1040496 important
thanks

As discussed on IRC I am hacking around this in qt6-virtualkeyboard 
6.4.2+dfsg-3 so parallel is at least 2. I personally do not think this is an 
RC bug, but at least we have a way to avoid the FTBFS for the time being.

My tests with Qt 6.5 showed no issue, so hopefully we are going to get this 
cleaned up soon.

Regards, Lisandro.

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

Bug#1038699: closed by Patrick Franz ()

[Lisandro Damian Nicanor Perez Meyer]

On miércoles, 12 de julio de 2023 19:15:20 -03 Lisandro Damian Nicanor Perez 
Meyer wrote:
> On miércoles, 21 de junio de 2023 05:51:37 -03 Oswald Buddenhagen wrote:
> > huh?
> > 
> > if the declaration of the private dependency is just missing in that qtc
> > plugin , then fair enough.
> 
> You need the QML private headers for that part since ages.
> 
> > but that doesn't explain the total garbage
> > error message which suggests some kind of internal error (it sort of
> > suggests that an incomplete package is installed like in the other bug i
> > reported, except that it's just not there).
> 
> Exactly, it suggests you are missing the private headers. Whoever coded that
> made them a dependency. The fact that we split them and do not install them
> by default makes the code show that error message.

Or maybe you where suggesting that the error message is not as helpful as a 
more direct one. If that's the case... I don't think any of us will put time 
on that. If you want I can reopen the bug and mark it as wishlist. But you 
know the upstream procedure better than I, and maybe you can sen a patch to 
upstream!


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

Bug#1038699: closed by Patrick Franz ()

[Lisandro Damian Nicanor Perez Meyer]

On miércoles, 21 de junio de 2023 05:51:37 -03 Oswald Buddenhagen wrote:
> huh?
> 
> if the declaration of the private dependency is just missing in that qtc
> plugin , then fair enough.

You need the QML private headers for that part since ages.

> but that doesn't explain the total garbage
> error message which suggests some kind of internal error (it sort of
> suggests that an incomplete package is installed like in the other bug i
> reported, except that it's just not there).

Exactly, it suggests you are missing the private headers. Whoever coded that 
made them a dependency. The fact that we split them and do not install them by 
default makes the code show that error message.

> please investigate whether this is a result of splitting, and forward
> the bug to upstream with your findings.

No need to, the answer will be "install the private headers".


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

Bug#1040653: gnome-keyring: Depends upon pinentry-gtk instead of pinentry

[Lisandro Damian Nicanor Perez Meyer]

On domingo, 9 de julio de 2023 12:20:44 -03 Lisandro Damian Nicanor Perez 
Meyer wrote:
> On sábado, 8 de julio de 2023 12:38:53 -03 Lisandro Damián Nicanor Pérez
> Meyer wrote:
> [snip]
> 
> > Hi! gnome-keyring depends upon pinentry-gtk instead of just pinentry.
> > This forces the installation of the gtk versions on systems that might
> > as well use the curses or Qt versions of pinentry.
> > 
> > If you want you could use pinentry as a dependency and pinentry-gtk as a
> > recommendation, thus installaing the GTK version by default on systems
> > that do not have any other pinentry package installed, but still
> > allowing the user to choose which pinentry version to install.
> 
> Actually the dependency can be changed to
> 
>   pinentry | pinentry-gtk
> 
> **unless** it is expected to have a GUI, in which case the dependency can be
> 
>   pinentry-x11 | pinentry- gtk

My apologies, it needs to be the other way around in order to avoid apt 
picking a random one, so either

  pinentry-gtk | pinentry

or

  pinenty-gtk | pinentry-x11

Thanks Pino Toscano for the tip!

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

Bug#1040653: gnome-keyring: Depends upon pinentry-gtk instead of pinentry

[Lisandro Damian Nicanor Perez Meyer]

On sábado, 8 de julio de 2023 12:38:53 -03 Lisandro Damián Nicanor Pérez Meyer 
wrote:
[snip] 
> Hi! gnome-keyring depends upon pinentry-gtk instead of just pinentry.
> This forces the installation of the gtk versions on systems that might
> as well use the curses or Qt versions of pinentry.
> 
> If you want you could use pinentry as a dependency and pinentry-gtk as a
> recommendation, thus installaing the GTK version by default on systems
> that do not have any other pinentry package installed, but still
> allowing the user to choose which pinentry version to install.

Actually the dependency can be changed to

  pinentry | pinentry-gtk

**unless** it is expected to have a GUI, in which case the dependency can be

  pinentry-x11 | pinentry- gtk

Thanks in advance, Lisandro.

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

Bug#1040700: kleopatra: Depends upon pinentry-qt instead of pinentry

[Lisandro Damian Nicanor Perez Meyer]

tag 1040700 + patch
thanks

On domingo, 9 de julio de 2023 12:00:30 -03 Lisandro Damián Nicanor Pérez 
Meyer wrote:
> Package: kleopatra
> Version: 4:22.12.3-1
> Severity: normal
> X-Debbugs-Cc: lisan...@debian.org
> 
> Hi! kleopatra has a direct dependency on pinentry-qt instead of
> pinentry. The problem with this is that people wanting to use any other
> pinentry fronted are forced to install the Qt version.
> 
> The correct solution for this would be to replace the dependency with
> pinentry and move pinentry-qt as Recommends, thus giving the Qt version
> a chance but allowing users to use any other variant, like the curses or
> gtk one.

MR in https://salsa.debian.org/qt-kde-team/kde/kleopatra/-/merge_requests/2

Thanks Pino for noticing that this requires a graphical pinentry manager, so 
now the dependency is pinentry-x11 | pinentry-qt.


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

Bug#1038988: qt6-multimedia: Patch to build with system egein3

[Lisandro Damian Nicanor Perez Meyer]

Hi!

On sábado, 24 de junio de 2023 03:42:33 -03 Christian Marillat wrote:
> Source: qt6-multimedia
> Version: 6.4.2-5
> Severity: normal
> 
> Dear Maintainer,
> 
> Please find bellow a debdiff to build qt6-multimedia with system
> eigen3
> 
> Changes are:
>   Add libeigen3-dev to Build-Depends
>   Add a pacth to changes the cinclude path ../3rdparty/eigen to
> /usr/include/eigen3 in src/spatialaudio/CMakeLists.txt and
> src/resonance-audio/CMakeLists.txt

Thanks for your patch! to be totally honest I missed it yesterday while doing 
a Multimedia upload, my bad.

The patch looks really good, but I also just noticed that eigen3 provides both 
cmake and pkg-config files, so ideally we should try to use that. No, I'm not 
asking you to do it, I'll tyr to give it a go.

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

Bug#1040496: qt6-virtualkeyboard FTBFS with parallel=1: qmlcachegen segfaults

[Lisandro Damian Nicanor Perez Meyer]

On sábado, 8 de julio de 2023 12:27:34 -03 Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Hi,
> 
> On Thu, 6 Jul 2023 at 14:30, Helmut Grohne  wrote:
> > Source: qt6-virtualkeyboard
> > Version: 6.4.2+dfsg-2
> > Severity: serious
> > Tags: ftbfs
> > 
> > qt6-virtualkeyboard fails to build from source in unstable when passing
> 
> > DEB_BUILD_OPTIONS=parallel=1. A build ends as follows:
> Interestingly enough I could only reproduce the issue by using sbuild.
> If I hand compile it using dpkg-buildpackage directly on a clean
> machine things just work.

More info: I did a build of qt6-virtualkeyboard on 6.5.1 with parallel=1 with 
no issues... but at the same time not the fully proper environment, because it 
was an sbuild build using Ubuntu focal and some special Qt build I have at 
hand. But maybe the answer is there.

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

Bug#1035985: Built without GLESv2 support causing errors on machines only supporting GLES

[Lisandro Damian Nicanor Perez Meyer]

Hi Erik, Leonardo

On Sun, 4 Jun 2023 22:41:46 -0300 Lisandro Damián Nicanor Pérez Meyer 
 wrote:
[snip]
> > please consider bumping the severity level of #1035985, as it makes
> > Debian unable to use qt on the many embedded platforms, and the next
> > stable will be affected by this for a long time. Is it possible to
> > include the `QT_FEATURE_opengles2` flag before the release? I'm
> > willingly to send a patch if needed.
> 
> I am afraid it was discovered too late in the release process. My plan
> is to test it as soon as Bookworm is released and hopefully get a
> stable pu update. But I can't promise anything.
> 
> Bumping the severity for a feature not discovered in time is a non-go.
> 
> 

I reviewed this bug report. libgles-dev is present in the build, as you can see 
in [0].

[0] 


Moreover, if you grep for "gles" in the build log [1] you will see that both 
libgles1 and libgles2 are present.

[1] 


Or even:

```
-- Performing Test HAVE_GLESv2
-- Performing Test HAVE_GLESv2 - Success
-- Found GLESv2: /usr/include 
```

If I force FEATURE_opengles2=ON I get:

```
CMake Error at cmake/QtBuildInformation.cmake:490 (message):
  Feature "opengles2": Forcing to "ON" breaks its condition:

  NOT WIN32 AND NOT WATCHOS AND NOT QT_FEATURE_opengl_desktop AND 
GLESv2_FOUND

  Condition values dump:

  WIN32 = ""
  WATCHOS = "0"
  QT_FEATURE_opengl_desktop = "ON"
  GLESv2_FOUND = "TRUE"

Call Stack (most recent call first):
  cmake/QtFeature.cmake:281 (qt_configure_add_report_error)
  cmake/QtFeature.cmake:403 (qt_feature_check_and_save_internal_value)
  cmake/QtFeature.cmake:606 (qt_evaluate_feature)
  cmake/QtFeature.cmake:575 (qt_feature_module_end)
  src/CMakeLists.txt:12 (qt_feature_evaluate_features)
```

So, unless I am missing something, it is Qt itself the one not producing OpenGL 
ES 2 support.

Am I missing something here?

Kinds regards, Lisandro.

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

Bug#1034457: libqt5quick5: Qt segfault on amd64

[Lisandro Damian Nicanor Perez Meyer]

tag 1034457 unreproducible moreinfo
thanks

Hi!

On sábado, 15 de abril de 2023 18:51:18 -03 Julian Groß wrote:
> Package: libqt5quick5
> Version: 5.15.8+dfsg-3
> Severity: normal
> 
> Dear Maintainer,
> 
> we ran into what appears to be a segmentation fault in Qt.
> One of the last places it runs into is QQuickOpenGLShaderEffectCommon which
> is why I am reporting it towards this package.

Well, when you have a crash you are supposed to file a bug against the 
application that triggers the segfault. If this is the case, then please close 
this bug (or just reply asking us to do it) and then file a new bug to the 
application itself, so all the relevant metadata is there.

If the application that triggers the bug is not in Debian then you must add a 
complete small example code to trigger the bug.

Thanks, Lisandro.

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

Bug#929458: RFP: trivy -- A Simple and Comprehensive Vulnerability Scanner for Containers, Suitable for CI

[Damian Szuberski]

 not yet been converted to use XS-Go-Import-Path in
debian/control2023/05/01 10:55:44 Build-Dependency
"github.com/aquasecurity/bolt-fixtures
<http://github.com/aquasecurity/bolt-fixtures>" is not yet available in
Debian, or has not yet been converted to use XS-Go-Import-Path in
debian/control2023/05/01 10:55:44 Build-Dependency
"github.com/aquasecurity/trivy-java-db
<http://github.com/aquasecurity/trivy-java-db>" is not yet available in
Debian, or has not yet been converted to use XS-Go-Import-Path in
debian/control2023/05/01 10:55:44 Build-Dependency
"github.com/aquasecurity/trivy-db
<http://github.com/aquasecurity/trivy-db>" is not yet available in Debian,
or has not yet been converted to use XS-Go-Import-Path in
debian/control2023/05/01 10:55:44 Build-Dependency
"github.com/aquasecurity/go-pep440-version
<http://github.com/aquasecurity/go-pep440-version>" is not yet available in
Debian, or has not yet been converted to use XS-Go-Import-Path in
debian/control2023/05/01 10:55:44 Build-Dependency
"github.com/tetratelabs/wazero <http://github.com/tetratelabs/wazero>" is
not yet available in Debian, or has not yet been converted to use
XS-Go-Import-Path in debian/control2023/05/01 10:55:44 Build-Dependency
"github.com/openvex/go-vex <http://github.com/openvex/go-vex>" is not yet
available in Debian, or has not yet been converted to use XS-Go-Import-Path
in debian/control2023/05/01 10:55:44 Build-Dependency
"github.com/aquasecurity/tml <http://github.com/aquasecurity/tml>" is not
yet available in Debian, or has not yet been converted to use
XS-Go-Import-Path in debian/control2023/05/01 10:55:44 Build-Dependency
"github.com/aquasecurity/testdocker
<http://github.com/aquasecurity/testdocker>" is not yet available in
Debian, or has not yet been converted to use XS-Go-Import-Path in
debian/control2023/05/01 10:55:44 Build-Dependency
"github.com/open-policy-agent/opa
<http://github.com/open-policy-agent/opa>" is not yet available in Debian,
or has not yet been converted to use XS-Go-Import-Path in
debian/control2023/05/01 10:55:44 Build-Dependency
"github.com/aquasecurity/loading <http://github.com/aquasecurity/loading>"
is not yet available in Debian, or has not yet been converted to use
XS-Go-Import-Path in debian/control2023/05/01 10:55:44 Build-Dependency
"github.com/GoogleCloudPlatform/docker-credential-gcr
<http://github.com/GoogleCloudPlatform/docker-credential-gcr>" is not yet
available in Debian, or has not yet been converted to use XS-Go-Import-Path
in debian/control2023/05/01 10:55:44 Build-Dependency
"github.com/twitchtv/twirp <http://github.com/twitchtv/twirp>" is not yet
available in Debian, or has not yet been converted to use XS-Go-Import-Path
in debian/control2023/05/01 10:55:44 Build-Dependency
"github.com/masahiro331/go-ebs-file
<http://github.com/masahiro331/go-ebs-file>" is not yet available in
Debian, or has not yet been converted to use XS-Go-Import-Path in
debian/control*


On Fri, Apr 28, 2023 at 9:03 PM  wrote:

> Our friends from openSUSE have this packaged already. We can probably use
> that as inspiration.
>
> https://software.opensuse.org/package/trivy
>


-- 
Damian Szuberski

Bug#1034749: ITP: session-manager-plugin -- This plugin helps you to use the AWS Command Line Interface (AWS CLI) to start and end sessions to your managed instances

[Damian Szuberski]

Package: wnpp
Severity: wishlist
Owner: Damian Szuberski 

* Package name: session-manager-plugin
  Version : 1.2.463.0-1
  Upstream Author : Amazon Web Services
* URL : https://github.com/aws/session-manager-plugin
* License : Apache-2.0
  Programming Lang: Go
  Description : This plugin helps you to use the AWS Command Line
Interface (AWS CLI) to start and end sessions to your managed instances

 Session Manager Plugin
 .
 This plugin helps you to use the AWS Command Line Interface (AWS CLI) to
 start and end sessions to your managed instances. Session Manager is a
 capability of AWS Systems Manager.

-- 
Damian Szuberski

Bug#717528: kdm and gwenview cannot display complex svg

[Lisandro Damian Nicanor Perez Meyer]

reassign 717528 src:qtbase-opensource-src 5.7.1+dfsg-3+deb9u2
tag 717528 wontfix
thanks

On Sun, 21 Jul 2013 20:52:54 +0200 Holger Levsen  
wrote:
> package: kdm,gwenview
> tags: upstream
> 
> Hi,
> 
> thanks for maintaining KDE!
> 
> both kdm and gwenview cannot display complex svg correctly. The attached file 
> can be viewed by inkview without problem, also gimp+inkscape work well. All 
in 
> wheezy.
> 
> I guess some library is to blame but I'm not sure which. Please reassign as 
> appropriate.

Wooa, this is an old one!

The real culprit here is Qt's SVG rendering engine. It has never been up to 
task.

I am ressigning to qtbase-opensource-src, the oldest I can currently find with 
rmadison, because... it's as old as Qt 5 itself.

I am also marking it as wontfix, as clearly the situation has not improved 
along all these years. I still need to check what's the Qt 6 status on 
this

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

Bug#1034606: ITP: golang-github-cihub-seelog -- Seelog is a native Go logging library that provides flexible asynchronous dispatching, filtering, and formatting.

[Damian Szuberski]

Package: wnpp
Severity: wishlist
Owner: Damian Szuberski 

* Package name: golang-github-cihub-seelog
  Version : 2.6-1
  Upstream Author : Seelog project repository
* URL : https://github.com/cihub/seelog
* License : BSD-3-clause
  Programming Lang: Go
  Description : Seelog is a native Go logging library that provides
flexible asynchronous dispatching, filtering, and formatting.

 Seelog
 .
 Seelog is a powerful and easy-to-learn logging framework that provides
 functionality for flexible dispatching, filtering, and formatting log
 messages. It is natively written in the Go (http://golang.org/)
 programming language.

A dependency for github.com/aws/session-manager-plugin

-- 
Damian Szuberski

Bug#1034137: Acknowledgement (ITP: diffr -- Yet another diff highlighting tool)

[Damian Szuberski]

Relevant MR at
https://salsa.debian.org/rust-team/debcargo-conf/-/merge_requests/485

On Mon, Apr 10, 2023 at 8:12 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 1034137:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034137.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  w...@debian.org
>  szubersk 
>
> If you wish to submit further information on this problem, please
> send it to 1034...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 1034137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034137
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>


-- 
Damian Szuberski

Bug#1034137: ITP: diffr -- Yet another diff highlighting tool

[Damian Szuberski]

Package: wnpp
Owner: szubersk 
Severity: wishlist

* Package name: diffr
  Version : 1.5.0
  Upstream Author : Nathan Moreau 
* URL : https://github.com/mookid/diffr
<https://github.com/tfeldmann/organize>
* License : MIT
  Programming Lang: Rust
  Description : Yet another diff highlighting tool


Reviewing changes involves reading diffs. Sometimes, a line-oriented
presentation of changes is not precise enough, especially when changes
involve long lines or very similar consecutive lines.

This program processes such diffs, and outputs them (in the console) with
additional diff information on top of the unified diff format, using text
attributes.

It works hunk by hunk, recomputing the diff on a word-by-word basis.
The current implementation uses Myers' longest common subsequence
<http://www.xmailserver.org/diff2.pdf> algorithm.

-- 
Damian Szuberski

Bug#1034136:

[Damian Szuberski]

Package: wnpp
Owner: szubersk 
Severity: wishlist

* Package name: diffr
  Version : 1.5.0
  Upstream Author : Nathan Moreau 
* URL : https://github.com/mookid/diffr
<https://github.com/tfeldmann/organize>
* License : MIT
  Programming Lang: Rust
  Description : Yet another diff highlighting tool


Reviewing changes involves reading diffs. Sometimes, a line-oriented
presentation of changes is not precise enough, especially when changes
involve long lines or very similar consecutive lines.

This program processes such diffs, and outputs them (in the console) with
additional diff information on top of the unified diff format, using text
attributes.

It works hunk by hunk, recomputing the diff on a word-by-word basis.
The current implementation uses Myers' longest common subsequence
<http://www.xmailserver.org/diff2.pdf> algorithm.

-- 
Damian Szuberski

Bug#1031863: libqt5sql5-mysql: incompatible change in libmariadb3 breaks kontact, needs upstream fix in libqt5sql5-mysql

[Lisandro Damian Nicanor Perez Meyer]

Hi Paul!

On domingo, 26 de febrero de 2023 12:18:48 -03 Paul Boddie wrote:
> On Sunday, 26 February 2023 15:38:20 CET Lisandro Damian Nicanor Perez Meyer
> wrote:
> > reassign 1031863 libmariadb3 1:10.3.34-0+deb10u1
> > thanks
> 
> [...]
> 
> > This is a bug in oldstable! If mariadb maintainers pushed a new version
> > there then they need to undo the change you mention above. This is not a
> > Qt
> > issue for oldstable.
> 
> It was an open question as to whether Debian packaging would adopt the same
> strategy as Qt upstream, introducing the workaround in Qt, or mitigate the
> problem in the libmariadb3 packaging. I wonder, then, if the severity should
> be elevated since this regression potentially breaks numerous other
> packages.

If we where talking about testing, yes, fixing Qt would be the way to go. But 
this is different, ideally the mariadb maintainers (or whoever uploaded the 
package) should fix the regression. If we try to do this in oldtsbale then we 
risk breaking someone else's setup.

That being said: you should **REALLY** consider switching to stable like 
**RIGHT NOW**. Why? Because in Debian we provide no security on webengine/
wekbit, and kde pim uses it a lot. Using it in oldstable is really a bad, bad 
idea.

Regards, Lisandro.


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

Bug#1031863: libqt5sql5-mysql: incompatible change in libmariadb3 breaks kontact, needs upstream fix in libqt5sql5-mysql

[Lisandro Damian Nicanor Perez Meyer]

reassign 1031863 libmariadb3 1:10.3.34-0+deb10u1
thanks

Hi!

On Fri, 24 Feb 2023 15:25:58 +0100 Paul Boddie  wrote:
> Package: libqt5sql5-mysql
> Version: 5.11.3+dfsg1-1+deb10u5
> Severity: important
> 
> Dear Maintainer,
> 
> A recent update to libmariadb3 introduced a change to MySQL version number
> reporting that ultimately breaks Kontact and Akonadi. To note this, I filed
> bug #1031770 against the kontact package:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031770
> 
> However, this breakage probably needs fixing in the Qt 5 SQL driver for
> MySQL/MariaDB, and a fix was indeed introduced to Qt 5.15 upstream:
> 
> https://bugreports.qt.io/browse/QTBUG-95071

This is a bug in oldstable! If mariadb maintainers pushed a new version there 
then they need to undo the change you mention above. This is not a Qt issue 
for oldstable.

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

Bug#1020387: dictionaries-common: Consensus regarding the packaging of the Qt WebEngine hunspell binary dictionaries

[Lisandro Damian Nicanor Perez Meyer]

By the way: I **do** understand that what you all are proposing is an easy way 
out and sounds like it makes sense.

Now I have been around Qt for 10+ years already, and suffered each and every 
web engine of the day source code during all this time. I know how problematic 
it can be and how, at the end of the day, is us maintainers then one that get 
the broken pieces when something breaks. Really, it's a pain.

Had this occurred in another Qt submodule I would probably not be so adamant 
in avoiding it. But webengine/webkit where always a PITA. And I do not expect 
that to change, I'm afraid.

Bug#1020387: dictionaries-common: Consensus regarding the packaging of the Qt WebEngine hunspell binary dictionaries

[Lisandro Damian Nicanor Perez Meyer]

On jueves, 16 de febrero de 2023 02:40:21 -03 Rene Engelhard wrote:
> Hi,
> 
> Am 16.02.23 um 02:24 schrieb Lisandro Damian Nicanor Perez Meyer:
> > - Hunspell dictionaries should be handled by... hunspell. Yes, I know
> > this was
> > considered and it's still not possible. But the fact that webengine ships
> > them is not enough a reason to expose them to the world instead of doing
> > the right thing: handling them there.
> 
> Then make it use hunspell.
> 
> Unpatched and with the same format.
> 
> It's not as if hunspell invented a binary format for no gain at all
> instead of just differentiating for differentiating.
> 
> Same with an internal *patched* hunspell copy.

I agree with that, and actually is one of the many reasons why I was against 
uploading qt6-webengine in the first place.

> > - If the patches are taken and at some point webengine upstreams decide to
> > switch to something else then we the Qt maintainers get the broken pieces.
> > Insta RC bugs, we get this package stopped from migrating to testing until
> > solving the issue... a pain.
> 
> e.g.
> 
> That is already the case. All packages building bdic right now *are*
> laready using it (and be it via usage of installdeb-myspell which calls
> the binary):
> 
> root@frodo:/# apt-cache showsrc igerman98
> Package: igerman98
> Binary: ingerman, iswiss, wngerman, wswiss, rmligs-german,
> hunspell-de-at, hunspell-de-ch, hunspell-de-de, aspell-de
> Version: 20161207-11
> Maintainer: Roland Rosenfeld 
> Uploaders: Rene Engelhard 
> Build-Depends: debhelper-compat (= 13)
> Build-Depends-Indep: aspell, busybox, dictionaries-common-dev (>=
> 1.29.3), hunspell, qt6-webengine-dev-tools, ispell
> [...]
>
> > So no, I'm totally against these change. Dmitry, Patrick: my suggestion is
> > to reverse the patches.
> 
> If you  revert the virtual package it's still too late. And it
> complicates things even more since then people need to change their
> build-dependency (and maybe calls) explicitely, causing more PITA.

The virtual package for Qt 6 is commited but not uploaded.

See, with the current status if tomorrow webengine stops providing hunspell 
dictionaries then we Qt maintainers have no obligation against packages using 
them: they where never meant to be used for packages not really using Qt 6.

On the other hand going ahead with this means this becomes official API-like 
behavior.
 
> The virtual package will help with that in that this will automagically
> happen.
> 
> 
> And the whole bdic  thingy: It's there, in in qtwebengine itself.
> dictionaries-commons policy, in installdeb-myspell --bdic-only etc.
> 
> And Soren has a point, Debian should support those .bdic files is
> possible, how broken their existence may be.

Then fork the hunspell code out of webengine and provide a proper package. 
That won't break at webengine's developers will.

Bug#1020387: dictionaries-common: Consensus regarding the packaging of the Qt WebEngine hunspell binary dictionaries

[Lisandro Damian Nicanor Perez Meyer]

On martes, 14 de febrero de 2023 19:28:53 -03 Soren Stoutner wrote:
> Which part do you not understand about not being needed on both Qt 5 and Qt
> 6? The part about building the .bdic files or the part about Qt WebEngine
> using the .bdic files at runtime?

Sorry, wrong question on my side.

I just went trough the whole thread. I understand that these bdic files are 
needed for packages that use Qt[5 6]webengine. But I do not like the idea of 
**other** packages making use of them.

Let me explain you why:

- webengine is the most complicated package we handle, it is the very example 
of a PITA. It embeds the world, it takes ages to compile, it has weird 
errors...

- Hunspell dictionaries should be handled by... hunspell. Yes, I know this was 
considered and it's still not possible. But the fact that webengine ships them 
is not enough a reason to expose them to the world instead of doing the right 
thing: handling them there.

- They are not built by default by Qt itself. This is weird... or they do not 
want to handle possible build errors. Should we Qt maintainers? No.

- If the patches are taken and at some point webengine upstreams decide to 
switch to something else then we the Qt maintainers get the broken pieces. 
Insta RC bugs, we get this package stopped from migrating to testing until 
solving the issue... a pain.

So no, I'm totally against these change. Dmitry, Patrick: my suggestion is to 
reverse the patches.

Bug#1030546: qt6-base FTBFS on hppa

[Lisandro Damian Nicanor Perez Meyer]

On lunes, 6 de febrero de 2023 17:59:47 -03 Peter Pentchev wrote:
[snip]
> FWIW, I think that you're mostly on the right path, but with a small
> correction: both zstd::libzstd_shared and zstd::libzstd_static are defined
> by libzstd's newly-exposed CMake config.

Exactly.

> I added --trace-expand to
> qt6-base's dh_auto_configure arguments, and got (among much else) this
> output:
> 
> ...
> /<>/cmake/FindWrapZSTD.cmake(21):  find_package(zstd CONFIG
> QUIET ) /usr/lib/x86_64-linux-gnu/cmake/zstd/zstdConfigVersion.cmake(12): 
> set(PACKAGE_VERSION 1.5.2 ) ...
> /usr/lib/x86_64-linux-gnu/cmake/zstd/zstdTargets.cmake(69): 
> add_library(zstd::libzstd_shared SHARED IMPORTED )
> /usr/lib/x86_64-linux-gnu/cmake/zstd/zstdTargets.cmake(71): 
> set_target_properties(zstd::libzstd_shared PROPERTIES
> INTERFACE_INCLUDE_DIRECTORIES /usr/include )
> /usr/lib/x86_64-linux-gnu/cmake/zstd/zstdTargets.cmake(76): 
> add_library(zstd::libzstd_static STATIC IMPORTED )
> /usr/lib/x86_64-linux-gnu/cmake/zstd/zstdTargets.cmake(78): 
> set_target_properties(zstd::libzstd_static PROPERTIES
> INTERFACE_INCLUDE_DIRECTORIES /usr/include ) ...
> /<>/cmake/FindWrapZSTD.cmake(25):  if(TARGET
> zstd::libzstd_static OR TARGET zstd::libzstd_shared ) ...
> /<>/cmake/FindWrapZSTD.cmake(28):  if(TARGET
> zstd::libzstd_static ) /<>/cmake/FindWrapZSTD.cmake(29): 
> set(zstdtargetsuffix _static ) ...
> 
> So qt6-base's cmake/FindWrapZSTD.cmake file asks CMake about the zstd
> configuration, then correctly determines that either the shared or
> the static libraries are defined as CMake targets (they both are), and
> then, at cmake/FindWrapZSTD.cmake line 28, prefers the static one to
> the shared one. That's what caused the change in behavior.

Once again, exactly.

> > I'll open a bug upstream about this, in the meantime I'll create a
> > derivative patch that forces using the shared library, ie , being more
> > aggressive so it's understood.
> 
> Thanks for your analysis and your work!

My pleasure! I realized what you wrote above when writing the upstream bug. 
Now we will need to see what upstream does, because according to Thiago there 
is a chance that the CMake support in libzstd is non-official... which I do not 
care much for as long as it works :-)

Anyways forcing the right behavior in Qt is done and that's the kind of patch 
I don't mind keeping.

Bug#1030497: ITP: accounts-qml-module -- Expose the Online Accounts API to QML applications

[Lisandro Damian Nicanor Perez Meyer]

On sábado, 4 de febrero de 2023 05:24:03 -03 Mike Gabriel wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Mike Gabriel 
> X-Debbugs-Cc: debian-de...@lists.debian.org
> 
> * Package name: accounts-qml-module

Hi Mike!

In the Qt/KDE team we have this naming convention for QML modules:

https://qt-kde-team.pages.debian.net/qmlmodulesnaming.html

So in this case the binary would be called qml-module-accounts.

It is not a strong policy for the rest of Debian, but I guess that following 
the convention could help here.

Happy hacking, Lisandro.

Bug#1025823: qt6-base FTBFS on Alpha; Unknown Q_PROCESSOR_xxx macro

[Lisandro Damian Nicanor Perez Meyer]

On viernes, 9 de diciembre de 2022 22:19:16 -03 Michael Cree wrote:
> Source: qt6-base
> Version: 6.3.1+dfsg-10
> Severity: important
> Tags: patch ftbfs
> Justification: fails to build from source (but built successfully in the
> past)
> 
> The build fails with:
> /<>/src/corelib/plugin/qelfparser_p.cpp:178:4: error: #error
> "Unknown Q_PROCESSOR_xxx macro, please update."
> 
> Full log at:
> https://buildd.debian.org/status/fetch.php?pkg=qt6-base=alpha=6.3.1
> %2Bdfsg-10=1664652510=0
> 
> Attached is patch to provide the Q_PROCESSOR defines for Alpha.  With
> that qt6-base builds successfully.

This really sounds like a patch that should go upstream. Normally such patchs 
would need to be sent by the creator. Would you mind doing that? Please ping 
me if you need help here.

Bug#1022116: SpamAssassin OLEVBMacro recursion limit not honored

[Damian]

Package: spamassassin
Version: 3.4.6-1

OLEVBAMacro offers olemacro_zip_depth as a recursion limit, which has no 
effect in SA3. I propose to backport the SA4 fix.diff --git a/debian/patches/fix-olemacro_zip_depth b/debian/patches/fix-olemacro_zip_depth
new file mode 100644
index 000..10bcb45
--- /dev/null
+++ b/debian/patches/fix-olemacro_zip_depth
@@ -0,0 +1,15 @@
+--- a/lib/Mail/SpamAssassin/Plugin/OLEVBMacro.pm
 b/lib/Mail/SpamAssassin/Plugin/OLEVBMacro.pm
+@@ -595,8 +595,10 @@
+   }
+   return 0 if $pms->{conf}->{olemacro_num_zip} == 0;
+ 
+-  $depth = $depth || 1;
+-  return 0 if ($depth > $pms->{conf}->{olemacro_zip_depth});
++  if (++$depth > $pms->{conf}->{olemacro_zip_depth}) {
++dbg("Zip recursion limit exceeded");
++return 0;
++  }
+ 
+   return 0 unless _is_zip_file($name, $data);
+   my $zip = _open_zip_handle($data);
diff --git a/debian/patches/series b/debian/patches/series
index 1891b96..a0bc92b 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -7,3 +7,4 @@ debian_gitignore
 bug426031-pod-fix
 skip_config_tree_recurse_test
 upstream/bug_7848_Rule_parser_doesn_t_support_nested_if_ifplugins.patch
+fix-olemacro_zip_depth

Bug#1013920: [Pkg-rust-maintainers] Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")

[Damian Yerrick]

Requiring work to be done upstream fails the desert island test,
as described by Thomas Bushnell in

> A good test case for whether a license is free (for issues like this)
> is whether a disconnected group of people on a desert island could
> distribute the software among themselves.  In the vim case, they
> cannot.  (For example, if the vim maintainer flies over the island and
> drops down a message saying "you must hereby send me your changes",
> how are the people down below to comply?)  The fact that the vim
> maintainer can send the request does not say anything about whether
> the people receiving it could reply.

> Documentation updates should be done upstream.
> Optimisations should be done upstream and not downstream.
> Such patches are part of the "adding patches that have been released
> upstream"
Updating documentation upstream, adding optimizations upstream,
or fixing security vulnerabilities upstream requires an Internet
connection when the changes are made.  It does not allow a relatively
isolated community with no consistent access to the Internet to make
these changes.

Bug#998852: Bug report is incorrect

[Damian Johnson]

Hi, I'm the author of Nyx and was just notified about Debian bug
998852. The sample nyxrc comes from me...

https://gitweb.torproject.org/nyx.git/tree/web/nyxrc.sample

And from what I can tell the reporter's interpretation of
color_override is incorrect (as discussed on
https://github.com/torproject/nyx/issues/39). This Debian ticket can
be closed and if the reporter has further issues they should open a
GitGub ticket with me to discuss it.

Bug#998468: libvirt0: qmeu KVM: USB Passthrough partially stopped working in Bullseye

[Damian Philipp]

Package: libvirt0
Version: 7.0.0-3
Severity: important
X-Debbugs-Cc: damian.phil...@gmx.net

Dear Maintainer,

I use a Debian Host to run KVM-based virtual machines, configured with 
virt-manager.
I run a VM with HASS.io (Home Assistant, a smart home software). Attached to 
the host is a USB Zigbee modem (Conbee II, in case it is important) which is 
passed through as individual device to the VM.
In Debian Buster, this setup was working reliably. After a dist-upgrade of the 
host to Debian Bullsee, this setup is now reliably broken.

virt-manager still shows the device as passed through to the VM. However, the 
VM does not appear to no longer have access to the USB device. Inside the VM, I 
run the zigbee2mqtt Plugin. The logs from the Plugin state:

[17:42:45] INFO: Handing over control to Zigbee2mqtt Core ...
> zigbee2mqtt@1.22.0 start
> node index.js
CREATED DECONZ ADAPTER
Zigbee2MQTT:error 2021-11-04 17:42:52: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2021-11-04 17:42:52: Failed to start zigbee
Zigbee2MQTT:error 2021-11-04 17:42:52: Check 
https://www.zigbee2mqtt.io/information/FAQ.html#help-zigbee2mqtt-fails-to-start 
for possible solutions
Zigbee2MQTT:error 2021-11-04 17:42:52: Exiting...
Zigbee2MQTT:error 2021-11-04 17:42:52: Error: Error while opening serialport 
'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
at SerialPort. 
(/app/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28)
at SerialPort._error 
(/app/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14)
at 
/app/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12
[17:42:52] INFO: Handing over control to Zigbee2mqtt Core ...

In short, /dev/ttyACM0 is not available. I can confirm that this device node is 
indeed missing by logging into the console of the VM and poking around in its 
/dev directory.

More interesting than the log from the VM is probably the following log from 
the host. Whenever the VM tries to access the USB device, dmesg is spammed (~30 
messages per second) with the following message:

[162164.169864] usb 1-5: usbfs: process 1788 (qemu-system-x86) did not claim 
interface 1 before use

The spam stops immediately when I shutdown the software inside the VM that 
tries to access the USB device.


In an attempt to narrow down the problem, I used another VM running an Ubuntu 
21.04 Live ISO. I attached a USB Flash drive to the Ubuntu VM to verify wheter 
USB passthrough was completely broken - reading from the flash drive worked. I 
then attached the USB Zigbee Modem to the Ubuntu VM instead of the HASS.io VM. 
I saw the aforementioned dmesg message exactly once - likely occuring as the 
Ubuntu VM tried to enumerate the USB device, as it does not otherwise know what 
to do with the device.
Furthermore, I observed that virt-manager shows different information for both 
of the USB devices. For the flash drive, it shows "002:002 Sony Corp. Storage 
Media", whereas for the Zigbee modem it shows "USB 1cf1:0030" instead. lsusb 
does show a device information that matches the name and manufacturer of the 
Zigbee modem, though.

I do not really know where the problem originates. Given that it surfaced 
exactly when I dist-upgraded Debian, I'm pinning it on Debian (and libvirt, 
more specifically) for now.

Can you please tell me how to fix passthrough of my USB device or how to 
further narrow down the problem?

Damian

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

Kernel: Linux 5.10.0-9-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libvirt0 depends on:
ii  libacl1  2.2.53-10
ii  libapparmor1 2.13.6-10
ii  libaudit11:3.0-2
ii  libc62.31-13+deb11u2
ii  libcap-ng0   0.7.9-2.2+b1
ii  libcurl3-gnutls  7.74.0-1.3+b1
ii  libgcc-s110.2.1-6
ii  libglib2.0-0 2.66.8-1
ii  libgnutls30  3.7.1-5
ii  libnl-3-200  3.4.0-1+b1
ii  libnuma1 2.0.12-1+b1
ii  libsasl2-2   2.1.27+dfsg-2.1
ii  libselinux1  3.1-3
ii  libssh2-11.9.0-2
ii  libxml2  2.9.10+dfsg-6.7
ii  libyajl2 2.1.0-3

Versions of packages libvirt0 recommends:
ii  lvm2  2.03.11-2.1

libvirt0 suggests no packages.

-- no debconf information

Bug#996148: linux-image-4.19.0-18-amd64: VMware Multi-Writer Shared Disks (via Physical SCSI Bus Sharing) now reported as 512b

[Damian]

Package: src:linux
Version: 4.19.208-1
Severity: important

Dear Maintainer,

an upgrade from linux-image-4.19.0-17-amd64=4.19.194-3 to 
linux-image-4.19.0-18-amd64=4.19.208-1 rendered certain VMware virtual 
disks unusable.
The affected VMware VM utilizes ordinary non-shared disks attached to a 
VMware Paravirtual SCSI controller with no SCSI Bus Sharing. Those disks 
are fine under linux-image-4.19.0-17 as well as linux-image-4.19.0-18.
The system has another set of disks which are shared with a different 
VM, by using a second VMware Paravirtual SCSI controller whose SCSI Bus 
Sharing is set to "Physical". Under linux-image-4.19.0-17, those disks 
work as indended, under linux-image-4.19.0-18, they are reported to be 
512b in size. Those 512b (under linux-image-4.19.0-18-amd64) are 
identical to the first 512b of the full-sized device under 
linux-image-4.19.0-17-amd64.


-- Package-specific info:
** Version:
Linux version 4.19.0-18-amd64 (debian-ker...@lists.debian.org) (gcc 
version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.208-1 (2021-09-29)


** Command line:
BOOT_IMAGE=/vmlinuz-4.19.0-18-amd64 root=/dev/mapper/vg0-root ro quiet

** Not tainted

** Kernel log (only storage related lines):
[    0.764041] Block layer SCSI generic (bsg) driver version 0.4 loaded 
(major 247)

[    0.940902] SCSI subsystem initialized
[    0.943488] VMware PVSCSI driver - version 1.0.7.0-k
[    0.943748] vmw_pvscsi: using 64bit dma
[    0.943850] vmw_pvscsi: max_id: 16
[    0.943851] vmw_pvscsi: setting ring_pages to 8
[    0.963320] vmw_pvscsi: enabling reqCallThreshold
[    0.963524] vmw_pvscsi: driver-based request coalescing enabled
[    0.963525] vmw_pvscsi: using MSI-X
[    0.963599] scsi host0: VMware PVSCSI storage adapter rev 2, 
req/cmp/msg rings: 8/8/1 pages, cmd_per_lun=254

[    0.963859] vmw_pvscsi :03:00.0: VMware PVSCSI rev 2 host #0
[    0.964092] vmw_pvscsi: using 64bit dma
[    0.964143] vmw_pvscsi: max_id: 16
[    0.964143] vmw_pvscsi: setting ring_pages to 8
[    0.964211] scsi 0:0:0:0: Direct-Access VMware   Virtual disk 
2.0  PQ: 0 ANSI: 6
[    0.964910] scsi 0:0:1:0: Direct-Access VMware   Virtual disk 
2.0  PQ: 0 ANSI: 6

[    0.971186] vmw_pvscsi: enabling reqCallThreshold
[    0.971400] vmw_pvscsi: driver-based request coalescing enabled
[    0.971401] vmw_pvscsi: using MSI-X
[    0.971477] scsi host1: VMware PVSCSI storage adapter rev 2, 
req/cmp/msg rings: 8/8/1 pages, cmd_per_lun=254

[    0.971661] vmw_pvscsi :04:00.0: VMware PVSCSI rev 2 host #1
[    0.972202] ata_piix :00:07.1: version 2.13
[    0.976312] scsi 1:0:0:0: Direct-Access VMware   Virtual disk 
2.0  PQ: 0 ANSI: 6

[    0.976343] scsi host2: ata_piix
[    0.976835] scsi 1:0:1:0: Direct-Access VMware   Virtual disk 
2.0  PQ: 0 ANSI: 6
[    0.984002] sd 0:0:0:0: [sda] 2097152 512-byte logical blocks: (1.07 
GB/1.00 GiB)

[    0.984017] sd 0:0:0:0: [sda] Write Protect is off
[    0.984017] sd 0:0:0:0: [sda] Mode Sense: 31 00 00 00
[    0.984033] sd 0:0:0:0: [sda] Cache data unavailable
[    0.984033] sd 0:0:0:0: [sda] Assuming drive cache: write through
[    0.984205] sd 0:0:1:0: [sdb] 33554432 512-byte logical blocks: (17.2 
GB/16.0 GiB)

[    0.984223] sd 0:0:1:0: [sdb] Write Protect is off
[    0.984224] sd 0:0:1:0: [sdb] Mode Sense: 31 00 00 00
[    0.984236] sd 0:0:1:0: [sdb] Cache data unavailable
[    0.984236] sd 0:0:1:0: [sdb] Assuming drive cache: write through
[    0.985425] scsi host3: ata_piix
[    0.985463] ata1: PATA max UDMA/33 cmd 0x1f0 ctl 0x3f6 bmdma 0x1060 
irq 14
[    0.985464] ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0x1068 
irq 15

[    0.986026]  sda: sda1
[    0.986203] sd 0:0:0:0: [sda] Attached SCSI disk
[    0.986237] sd 1:0:0:0: [sdc] Sector size 0 reported, assuming 512.
[    0.986381] sd 1:0:0:0: [sdc] 1 512-byte logical blocks: (512 B/512 B)
[    0.986382] sd 1:0:0:0: [sdc] 0-byte physical blocks
[    0.986403] sd 1:0:0:0: [sdc] Write Protect is off
[    0.986404] sd 1:0:0:0: [sdc] Mode Sense: 31 00 00 00
[    0.986418] sd 1:0:0:0: [sdc] Cache data unavailable
[    0.986418] sd 1:0:0:0: [sdc] Assuming drive cache: write through
[    0.986805] sd 1:0:1:0: [sdd] Sector size 0 reported, assuming 512.
[    0.986845] sd 1:0:1:0: [sdd] 1 512-byte logical blocks: (512 B/512 B)
[    0.986846] sd 1:0:1:0: [sdd] 0-byte physical blocks
[    0.986856] sd 1:0:1:0: [sdd] Write Protect is off
[    0.986857] sd 1:0:1:0: [sdd] Mode Sense: 31 00 00 00
[    0.986867] sd 1:0:1:0: [sdd] Cache data unavailable
[    0.986868] sd 1:0:1:0: [sdd] Assuming drive cache: write through
[    0.987074] sd 1:0:0:0: [sdc] Sector size 0 reported, assuming 512.
[    0.987668] Dev sdc: unable to read RDB block 1
[    0.987719]  sdc: unable to read partition table
[    0.987720] sdc: partition table beyond EOD, enabling native capacity
[    0.988215] sd 1:0:1:0: [sdd] Sector size 0 reported, assuming 512.
[    0.988463] sd 0:0:1:0: [sdb] Attached SCSI disk
[    0.988677] Dev sdd: 

Bug#994411: error: ‘DRM_IOCTL_I915_GEM_MMAP_OFFSET’ undeclared

[Marin Damian]

Package: libdrm-dev
Version: 2.4.104-1

When I'm using 'DRM_IOCTL_I915_GEM_MMAP_OFFSET' literal in a C program, I get 
an error message: 'DRM_IOCTL_I915_GEM_MMAP_OFFSET' undeclared.
Here is a transcript:

root@debian:~# gcc -xc -S -o - - << EOF
#include 
#include 
int main(void) {
  int code = 0;
  switch (code) {
  case DRM_IOCTL_I915_GEM_MMAP:
  case DRM_IOCTL_I915_GEM_MMAP_GTT:
  case DRM_IOCTL_I915_GEM_MMAP_OFFSET:
break;
  }
  return 0;
}
EOF
.file   ""
: In function ‘main’:
:8:8: error: ‘DRM_IOCTL_I915_GEM_MMAP_OFFSET’ undeclared (first use in 
this function); did you mean ‘DRM_IOCTL_I915_GEM_MMAP_GTT’?
:8:8: note: each undeclared identifier is reported only once for each 
function it appears in
root@debian:~#

I suggest that 'i915_drm.h' uapi header file be corrected.

I am using Debian GNU/Linux 11.0, kernel 5.10.46-4 and libc6 2.31.

Bug#986622: ClamAV 0.103.2 security patch release

[Damian Lukowski]

> CVE-2021-1252 :
> Fix for Excel XLM parser infinite loop. Affects 0.103.0 and 0.103.1 only.

Debian's security tracker claims that stretch and buster are vulnerable. According to the clamav announcement and CVE they 
shouldn't be.


> CVE-2021-1405 :
> Fix for mail parser NULL-dereference crash. Affects 0.103.1 and prior.

The clamav announcement and CVE are inconsistent whether 0.102 is affected.

Bug#934242:

[Damian Pluta]

Bug#760485: Jitsi meet packaging

[Damian Minkov]

Hi all,

Thanks for the interest in the project. There are a few concerns I have,
first is that we do not have the resources to maintain this.

The second one is that the project sometimes follows the pace of the
browsers to do new releases. Which means a new version every 6 weeks. We
had two or three occasions in the last few years where everyone needs to
update due to a breaking change in the browsers, like a mandatory field
being added in SDP, or the old bridge not supporting the new DTLS version.
And because of the pace of how things evolve, we do not support old release
doing backports. This means that if a package goes in stable it may happen
to soon be unusable.
And sometimes backporting a change is even not possible :) Like the DTLS
change, the update was moving of using a complete re-write of the bridge
... new dependencies and totally new project ...

And if someone chooses the path of doing the job we are talking about
150-200 dependent libraries, I'm not sure how many of those are already in
Debian, I would guess not much ... This was the main problem when we did
the Jitsi Desktop submission to the Debian repos, It took us, one
person, fulltime for almost six months.
Nowadays the video bridge had been rewritten and has fewer dependencies.
I'm also not sure about the state of Kotlin, is it yet in the repos, cause
it is one of the dependencies?

Regards
damencho


On Sun, Sep 27, 2020 at 8:11 AM Ko Ko Ye`  wrote:

> May I help you ?
>
> Mentoring or RFP / RFS
>
> with regards
>
> On Sun, Sep 27, 2020 at 6:57 PM Sudip Mukherjee <
> sudipm.mukher...@gmail.com> wrote:
>
>> On Sun, Sep 27, 2020 at 11:49 AM Mathias Behrle  wrote:
>> >
>> > * Fioddor Superconcentrado: " Jitsi meet packaging" (Sun, 27 Sep 2020
>> 12:10:17
>> >   +0200):
>> >
>> > Hi,
>> >
>> > > As user I'm interested in having Jitsi Meet available in FreedomBox.
>> Since
>> > > it is a pure Debian blend we need an official Debian package. So I'm
>> > > considering to step forward and take over it.
>> > >
>> > > But
>> > > 1) I've never ever packaged any Debian package.
>> > > 2) According to this bug, previous attempts have failed, so I guess
>> there
>> > > are reasons for that.
>> > >
>> > > So, any guidance would be welcome.
>> > >
>> > > I've seen that upstream already provides a .deb file. I guess it needs
>> > > further debianisation to be accepted in the archive.
>> >
>> > At least the original owner of #760485 seems to be the same person that
>> is
>> > currently active and in Uploaders at
>> > https://github.com/jitsi/jitsi-meet/blob/master/debian/control
>> >
>> > Best will be to ask him directly why he didn't push to get the packages
>> into
>> > Debian main. I have added him on CC.
>>
>> I had the same interest and mailed Damencho around March and he
>> mentioned about lack of resources to maintain jitsi in Debian as its a
>> lot of work.
>>
>>
>> --
>> Regards
>> Sudip
>>
>>
>
> --
>
> with regards *Ko Ko Ye`*
>
> +95 97989 22022
> +95 94500 22022
> +95 9731 47907
> kokoye2...@gmail.com
> kokoye2...@ubuntu.com
>
> skype: kokoye2007
> jitsi: kokoye2007
>
> http://ubuntu-mm.net
> http://wiki.ubuntu.com/kokoye2007
> http://wiki.ubuntu.com/MyanmarTeam http://loco.ubuntu.com/teams/ubuntu-mm
>

Bug#952443: libfile-slurp-perl: tempfile without OPEN

[Damian Lukowski]

Package: libfile-slurp-perl
Version: .26-1
Severity: normal

Dear Maintainer,

I would like to request a fix of [1] in buster if possible.

Regards
 Damian

[1] https://rt.cpan.org/Public/Bug/Display.html?id=129029

Bug#950258: fixed in spamassassin 3.4.2-1~deb9u3

[Damian]

Will there be a fix for jessie?

On Sun, 02 Feb 2020 13:47:53 + Debian FTP Masters
 wrote:

> Source: spamassassin
> Source-Version: 3.4.2-1~deb9u3
>
> We believe that the bug you reported is fixed in the latest version of
> spamassassin, which is due to be installed in the Debian FTP archive.
>
> A summary of the changes between this version and the previous one is
> attached.
>
> Thank you for reporting the bug, which will now be closed. If you
> have further comments please address them to 950...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.

Bug#900746: xen toolstack xl causes a Segmentation fault on create domu

[Damian Pietras]

I've also hit it on one of my boxes with
4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u8

This is related to too small stack size set for threads in XEN utils
which explicitly set it to use 16KB. Similar issue is reported here for
NTP: https://bugzilla.redhat.com/show_bug.cgi?id=1564527

I've recompilled the package with the attached patch to increase the
stack size from 16KB to 32KB and it works.

Technical details:

The issue appears with modern CPU that support AVX-512 instruction set,
in my case it's Intel(R) Xeon(R) Gold 6148. More details are in this
bug report against glibc: https://bugzilla.redhat.com/show_bug.cgi?id=1
527887#c18

There was a post on xen-users acknowledging the bug that says it's
fixed in XEN 4.11: https://lists.xenproject.org/archives/html/xen-users
/2018-05/msg00034.html





-- 
Damian Pietras
--- xen-4.8.3+xsa267+shim4.10.1+xsa267.orig/shim/tools/xenstore/xs.c
+++ xen-4.8.3+xsa267+shim4.10.1+xsa267/shim/tools/xenstore/xs.c
@@ -800,7 +800,7 @@ bool xs_watch(struct xs_handle *h, const
 	struct iovec iov[2];
 
 #ifdef USE_PTHREAD
-#define DEFAULT_THREAD_STACKSIZE (16 * 1024)
+#define DEFAULT_THREAD_STACKSIZE (32 * 1024)
 #define READ_THREAD_STACKSIZE 	\
 	((DEFAULT_THREAD_STACKSIZE < PTHREAD_STACK_MIN) ? 	\
 	PTHREAD_STACK_MIN : DEFAULT_THREAD_STACKSIZE)
--- xen-4.8.3+xsa267+shim4.10.1+xsa267.orig/tools/xenstore/xs.c
+++ xen-4.8.3+xsa267+shim4.10.1+xsa267/tools/xenstore/xs.c
@@ -725,7 +725,7 @@ bool xs_watch(struct xs_handle *h, const
 	struct iovec iov[2];
 
 #ifdef USE_PTHREAD
-#define DEFAULT_THREAD_STACKSIZE (16 * 1024)
+#define DEFAULT_THREAD_STACKSIZE (32 * 1024)
 #define READ_THREAD_STACKSIZE 	\
 	((DEFAULT_THREAD_STACKSIZE < PTHREAD_STACK_MIN) ? 	\
 	PTHREAD_STACK_MIN : DEFAULT_THREAD_STACKSIZE)

Bug#856124: Crash when want to render using OpenCL GPU

[Damian Zaręba]

Package: blender
Version: 2.78.a+dfsg0-4
Severity: normal

Dear Maintainer,

I was trying to render a sample thing in blender using OpenCL,but It
crashed. My PC is Lenovo ideaPad 300-15ISK. Debian paste of error from gdb
bt full: https://paste.debian.net/916710/


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

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

Versions of packages blender depends on:
ii  blender-data  2.78.a+dfsg0-4
ii  fonts-dejavu  2.37-1
ii  libavcodec57  10:3.2.4-dmo2
ii  libavdevice57 10:3.2.4-dmo2
ii  libavformat57 10:3.2.4-dmo2
ii  libavutil55   10:3.2.4-dmo2
ii  libboost-atomic1.62.0 1.62.0+dfsg-4
ii  libboost-chrono1.62.0 1.62.0+dfsg-4
ii  libboost-date-time1.62.0  1.62.0+dfsg-4
ii  libboost-filesystem1.62.0 1.62.0+dfsg-4
ii  libboost-iostreams1.62.0  1.62.0+dfsg-4
ii  libboost-locale1.62.0 1.62.0+dfsg-4
ii  libboost-regex1.62.0  1.62.0+dfsg-4
ii  libboost-system1.62.0 1.62.0+dfsg-4
ii  libboost-thread1.62.0 1.62.0+dfsg-4
ii  libc6 2.24-9
ii  libfftw3-double3  3.3.5-3
ii  libfontconfig12.11.0-6.7+b1
ii  libfreetype6  2.6.3-3+b2
ii  libgcc1   1:6.3.0-8
ii  libgl1-mesa-glx [libgl1]  13.0.5-1
ii  libglew2.02.0.0-3
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libgomp1  6.3.0-8
ii  libilmbase12  2.2.0-12
ii  libjack-jackd2-0 [libjack-0.125]  1.9.10+20150825git1ed50c92~dfsg-4+b1
ii  libjemalloc1  3.6.0-9.1
ii  libjpeg62-turbo   1:1.5.1-2
ii  libopenal11:1.17.2-4+b2
ii  libopencolorio1v5 1.0.9~dfsg0-6
ii  libopenexr22  2.2.0-11
ii  libopenimageio1.6 1.6.17~dfsg0-1+b2
ii  libopenjp2-7  2.1.2-1.1
ii  libopenvdb3.2 3.2.0-2.1
ii  libpcre3  2:8.39-2.1
ii  libpng16-16   1.6.28-1
ii  libpython3.5  3.5.3-1
ii  libsndfile1   1.0.27-1+b1
ii  libspnav0 0.2.3-1
ii  libstdc++66.3.0-8
ii  libswscale4   10:3.2.4-dmo2
ii  libtbb2   4.3~20150611-2
ii  libtiff5  4.0.7-5
ii  libx11-6  2:1.6.4-3
ii  libxi62:1.7.9-1
ii  libxml2   2.9.4+dfsg1-2.2
ii  libxxf86vm1   1:1.1.4-1
pn  python3:any   
ii  zlib1g1:1.2.8.dfsg-5

Bug#853787: wxmaxima: loadfile: failed to load /usr/share/wxMaxima/wxmathml.lisp

[Damian Zaręba]

Package: wxmaxima
Version: 16.12.2-1
Severity: important

Dear Maintainer,
I wanted to use a wxMaxima package,but I'm unable to,because It don't
want to load wxmathml.lisp file,which performs all of the calculations
in wxMaxima.it just appears in main window of the program.

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

Kernel: Linux 4.9.0-6.1-liquorix-amd64 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=pl_PL.utf8, LC_CTYPE=pl_PL.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages wxmaxima depends on:
ii  ibus-gtk31.5.14-2
ii  imagemagick  8:6.9.7.4+dfsg-1
ii  imagemagick-6.q16 [imagemagick]  8:6.9.7.4+dfsg-1
ii  libc62.24-9
ii  libgcc1  1:6.3.0-5
ii  libstdc++6   6.3.0-5
ii  libwxbase3.0-0v5 3.0.2+dfsg-2
ii  libwxgtk3.0-0v5  3.0.2+dfsg-2
ii  maxima   5.38.1-8
ii  maxima-doc   5.38.1-8

Versions of packages wxmaxima recommends:
ii  fonts-jsmath 0.090709+0-3
ii  texlive-latex-extra  2016.20170123-1

wxmaxima suggests no packages.

-- no debconf information




signature.asc
Description: OpenPGP digital signature

Bug#812866: flashplugin-nonfree: failed to verify checksum of install_flash_player_11_linux.x86_64.tar.gz file

[Damian Wrzalski]

Package: flashplugin-nonfree
Version: 1:3.6.1
Severity: normal

When root user have exported variable GREP_OPTIONS='--color=always' in
..bashrc, then update-flashplugin-nonfree failed on checksum verification:
ERROR: sha512sum rejected install_flash_player_11_linux.x86_64.tar.gz
I think it occur on 328 line in /usr/sbin/update-flashplugin-nonfree.

-- Package-specific info:
Debian version: 8.3
Architecture: amd64
Package version: 1:3.6.1
MD5 checksums:
160a01dd00527304e5291e65eb0c65e2  
/var/cache/flashplugin-nonfree/get-upstream-version.pl
md5sum: /usr/lib/flashplugin-nonfree/libflashplayer.so: No such file or 
directory
Alternatives:
update-alternatives: error: no alternatives for flash-mozilla.so
ls: cannot access /usr/lib/mozilla/plugins/flash-mozilla.so: No such 
file or directory
/usr/lib/mozilla/plugins/flash-mozilla.so: cannot open 
`/usr/lib/mozilla/plugins/flash-mozilla.so' (No such file or directory)

-- System Information:
Debian Release: 8.3
  APT prefers stable
  APT policy: (802, 'stable'), (791, 'testing'), (790, 'oldstable'), (780, 
'unstable'), (500, 'testing-updates'), (500, 'stable-updates'), (500, 
'oldstable-updates'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages flashplugin-nonfree depends on:
ii  binutils   2.25-5
ii  ca-certificates20141019+deb8u1
ii  debconf [debconf-2.0]  1.5.56
ii  gnupg  1.4.18-7
ii  libatk1.0-02.14.0-1
ii  libcairo2  1.14.0-2.1
ii  libcurl3-gnutls7.38.0-4+deb8u2
ii  libfontconfig1 2.11.0-6.3
ii  libfreetype6   2.5.2-3+deb8u1
ii  libgcc11:4.9.2-10
ii  libglib2.0-0   2.42.1-1
ii  libgtk2.0-02.24.25-3
ii  libnspr4   2:4.10.7-1+deb8u1
ii  libnss32:3.17.2-1.1+deb8u2
ii  libpango1.0-0  1.36.8-3
ii  libstdc++6 4.9.2-10
ii  libx11-6   2:1.6.2-3
ii  libxext6   2:1.3.3-1
ii  libxt6 1:1.1.4-1+b1
ii  wget   1.16-1

flashplugin-nonfree recommends no packages.

Versions of packages flashplugin-nonfree suggests:
ii  fonts-dejavu   2.34-1
ii  hal0.5.14-8
ii  iceweasel  43.0.4-1~bpo80+1
ii  konqueror-nsplugins4:4.14.2-1
ii  ttf-mscorefonts-installer  3.6
ii  ttf-xfree86-nonfree4.2.1-4

-- no debconf information

Bug#757768: ITP: libjitsi -- advanced Java media library

[Damian Minkov]

We always tried to keep all the packaging in one place, the code of
the project. You can find everything in
https://github.com/jitsi/libjitsi. The problem for rejection was the
api used in jsip and its license, I know Ingo and Daniel Pocock had
done some work in that direction, but nothing is finished. Also there
were a lot of changes since the last submission, like license changed
from lgpl to apache, and there were few libraries that we created from
libjitsi code (the lgpl dependencies) and some new were added. Also
the project was mavenized. A lot of changes, which suppose a lot of
work.


On Sun, Jan 10, 2016 at 2:20 AM, Petter Reinholdtsen <p...@hungry.com> wrote:
> [Damian Minkov]
>> I'm not aware of anybody working on it and there are no contributions
>> or volunteers of doing it. We will do it at some point, but we do not
>> have resources currently.
>
> Oh, that was sad to hear.
>
> Where is the code and debian packaging used to upload the last upload,
> and what was the message from the ftpmasters when it was rejected?  Is
> there a git repo somewhere with the Debian packaging available?  Without
> those key pieces of information, it will be impossible for volunteers to
> provide help.
>
> --
> Happy hacking
> Petter Reinholdtsen

Bug#757768: ITP: libjitsi -- advanced Java media library

[Damian Minkov]

The debian folder is here:
https://github.com/jitsi/libjitsi/tree/master/resources/install, but
everything is build using the ant in the main folder. Some of the docs
maybe outdated due to the changes I've described previously.

On Sun, Jan 10, 2016 at 9:38 AM, Damian Minkov <damen...@jitsi.org> wrote:
> We always tried to keep all the packaging in one place, the code of
> the project. You can find everything in
> https://github.com/jitsi/libjitsi. The problem for rejection was the
> api used in jsip and its license, I know Ingo and Daniel Pocock had
> done some work in that direction, but nothing is finished. Also there
> were a lot of changes since the last submission, like license changed
> from lgpl to apache, and there were few libraries that we created from
> libjitsi code (the lgpl dependencies) and some new were added. Also
> the project was mavenized. A lot of changes, which suppose a lot of
> work.
>
>
> On Sun, Jan 10, 2016 at 2:20 AM, Petter Reinholdtsen <p...@hungry.com> wrote:
>> [Damian Minkov]
>>> I'm not aware of anybody working on it and there are no contributions
>>> or volunteers of doing it. We will do it at some point, but we do not
>>> have resources currently.
>>
>> Oh, that was sad to hear.
>>
>> Where is the code and debian packaging used to upload the last upload,
>> and what was the message from the ftpmasters when it was rejected?  Is
>> there a git repo somewhere with the Debian packaging available?  Without
>> those key pieces of information, it will be impossible for volunteers to
>> provide help.
>>
>> --
>> Happy hacking
>> Petter Reinholdtsen

Bug#757768: ITP: libjitsi -- advanced Java media library

[Damian Minkov]

I'm not aware of anybody working on it and there are no contributions
or volunteers of doing it. We will do it at some point, but we do not
have resources currently.

On Sat, Jan 9, 2016 at 10:21 AM, Petter Reinholdtsen <p...@hungry.com> wrote:
> [Damian Minkov]
>>   Description : advanced Java media library
>
> Hi, what is the status of getting libjitsi into Debian?
>
> --
> Happy hacking
> Petter Reinholdtsen

Bug#255572: cc65 is free software now

[Damian Yerrick]

Two things have changed about cc65 in the past decadethat affect our 
ability to package it.First, the project has moved to 
http://cc65.github.io/cc65/Second, it is now free software. The 
license has changedfrom a non-free license with restrictions on 
distributionfor a fee to the zlib license as of May 5, 2015.
 

Bug#798727: Encode::Unicode decode() dies unnecessarily

[Damian Lukowski]

Hi Dominic,

the patch has been applied upstream.

Regards
 Damian

Am 12.09.2015 um 11:17 schrieb Dominic Hargreaves:

> Thanks for the bug report; I've added your patch to the upstream bug
> report, and will await comment by them.
> 
> Dominic.

Bug#798727: Acknowledgement (Encode::Unicode decode() dies unnecessarily)

[Damian Lukowski]

Unfortunately my first patch does not account for the first two octets
when they are not a BOM. In that case one needs to reset the read
pointer to the beginning.

root@d5305a0f945d:~# cat check-unicode.pl

use Encode qw/encode decode/;
my $str = 'ABCD';
printf "%s vs %s\n", $str, decode('utf-16be', encode('utf-16be', $str));
printf "%s vs %s\n", $str, decode('utf-16',   encode('utf-16',   $str));
printf "%s vs %s\n", $str, decode('utf-16',   encode('utf-16be', $str));

root@d5305a0f945d:~# perl check-unicode.pl # debian version
ABCD vs ABCD
ABCD vs ABCD
UTF-16:Unrecognised BOM 41 at
/usr/lib/x86_64-linux-gnu/perl/5.20/Encode.pm line 175.

root@d5305a0f945d:~# perl check-unicode.pl # first version of patch
ABCD vs ABCD
ABCD vs ABCD
ABCD vs BCD

root@d5305a0f945d:~# perl check-unicode.pl # second version of patch
ABCD vs ABCD
ABCD vs ABCD
ABCD vs ABCD


diff --git a/Unicode/Unicode.xs b/Unicode/Unicode.xs
index 5f3bceb..e309307 100644
--- a/Unicode/Unicode.xs
+++ b/Unicode/Unicode.xs
@@ -166,9 +166,19 @@ CODE:
endian = 'V';
}
else {
-   croak("%"SVf":Unrecognised BOM %"UVxf,
- *hv_fetch((HV *)SvRV(obj),"Name",4,0),
- bom);
+   /* No BOM found, use big-endian fallback as specified in
+* RFC2781 and the Unicode Standard version 8.0:
+*
+*  The UTF-16 encoding scheme may or may not begin with
+*  a BOM. However, when there is no BOM, and in the
+*  absence of a higher-level protocol, the byte order
+*  of the UTF-16 encoding scheme is big-endian.
+*
+*  If the first two octets of the text is not 0xFE
+*  followed by 0xFF, and is not 0xFF followed by 0xFE,
+*  then the text SHOULD be interpreted as big-endian.
+*/
+   s -= size;
}
}
 #if 1

Bug#798727: Encode::Unicode decode() dies unnecessarily

[Damian Lukowski]

Package: perl
Version: 5.20.2-2

The Encode::Unicode documentation states the following:

When BE or LE is omitted during decode(), it checks if BOM is at the
beginning of the string; if one is found, the endianness is set to what
the BOM says. If no BOM is found, the routine dies.

To reproduce:
---
use Encode qw/decode/;
decode("utf-16be", "Hello World"); # does not die
decode("utf-16le", "Hello World"); # does not die
decode("utf-16", "\xFE\xFFHello World"); # does not die
decode("utf-16", "Hello World"); # dies with "UTF-16:Unrecognised BOM"
---

Unicode Standard version 8.0:

The UTF-16 encoding scheme may or may not begin with a BOM. However,
when there is no BOM, and in the absence of a higher-level protocol, the
byte order of the UTF-16 encoding scheme is big-endian.

RFC2781:

If the first two octets of the text is not 0xFE followed by
0xFF, and is not 0xFF followed by 0xFE, then the text SHOULD be
interpreted as being big-endian.

There is a simple fix of doing nothing:

diff --git a/cpan/Encode/Unicode/Unicode.xs b/cpan/Encode/Unicode/Unicode.xs
index cf42ab8..7caf1c1 100644
--- a/cpan/Encode/Unicode/Unicode.xs
+++ b/cpan/Encode/Unicode/Unicode.xs
@@ -164,9 +164,18 @@ CODE:
endian = 'V';
}
else {
-   croak("%"SVf":Unrecognised BOM %"UVxf,
- *hv_fetch((HV *)SvRV(obj),"Name",4,0),
- bom);
+   /* No BOM found, use big-endian fallback as specified in
+* RFC2781 and the Unicode Standard version 8.0:
+*
+*  The UTF-16 encoding scheme may or may not begin with
+*  a BOM. However, when there is no BOM, and in the
+*  absence of a higher-level protocol, the byte order
+*  of the UTF-16 encoding scheme is big-endian.
+*
+*  If the first two octets of the text is not 0xFE
+*  followed by 0xFF, and is not 0xFF followed by 0xFE,
+*  then the text SHOULD be interpreted as big-endian.
+*/
}
}
 #if 1

CPAN bug report: https://rt.cpan.org/Ticket/Display.html?id=107043

Bug#783454: radiotray not supporting a radio

[Damian Nardelli]

Package: radiotray
Version: 0.7.3-3
Severity: normal

Dear Maintainer,

I'm trying to listen to the following radio http://201.212.5.144/aspen
The problem is when I try to turn it on, there is no audio and radiotray pops
up an error saying gstdecodebin2.c(3576): gst_decode_bin_expose ():
/GstPlayBin2:player/GstURIDecodeBin:uridecodebin1/GstDecodeBin2:decodebin21:
no suitable plugins found.
The log file located at ~/.local/share/radiotray shows the following:

--
2015-04-27 04:21:31,792 - DEBUG - Request to play
2015-04-27 04:21:31,793 - DEBUG - connecting
2015-04-27 04:21:31,796 - INFO - Requesting stream...
http://201.212.5.144/aspen
2015-04-27 04:21:31,827 - DEBUG - Metadata obtained...
2015-04-27 04:21:31,827 - INFO - Content-Type: video/x-ms-asf
2015-04-27 04:21:31,827 - INFO - Checking decoder
2015-04-27 04:21:31,827 - INFO - Checking decoder
2015-04-27 04:21:31,827 - INFO - Checking decoder
2015-04-27 04:21:31,828 - INFO - Stream is readable by ASF Playlist Decoder
2015-04-27 04:21:31,828 - INFO - Downloading playlist..
2015-04-27 04:21:31,875 - INFO - Playlist downloaded
2015-04-27 04:21:31,875 - INFO - Decoding playlist...
2015-04-27 04:21:31,875 - DEBUG - ['mms://201.212.5.144/aspen?MSWMExt=.asf',
'mms://201.212.5.144:80/aspen?MSWMExt=.asf']
2015-04-27 04:21:31,875 - INFO - Play mms://201.212.5.144/aspen?MSWMExt=.asf
2015-04-27 04:21:31,875 - INFO - Not an HTTP url. Maybe direct stream...
2015-04-27 04:21:32,005 - DEBUG - Received MESSAGE_STATE_CHANGED (enum
GST_STATE_NULL of type GstState - enum GST_STATE_READY of type GstState)
2015-04-27 04:21:32,005 - DEBUG - Received MESSAGE_STATE_CHANGED (enum
GST_STATE_NULL of type GstState - enum GST_STATE_READY of type GstState)
2015-04-27 04:21:32,005 - DEBUG - Received MESSAGE_STATE_CHANGED (enum
GST_STATE_NULL of type GstState - enum GST_STATE_READY of type GstState)
2015-04-27 04:21:32,006 - DEBUG - Received MESSAGE_STATE_CHANGED (enum
GST_STATE_NULL of type GstState - enum GST_STATE_READY of type GstState)
2015-04-27 04:21:32,006 - DEBUG - Received MESSAGE_STATE_CHANGED (enum
GST_STATE_READY of type GstState - enum GST_STATE_PAUSED of type GstState)
2015-04-27 04:21:32,006 - DEBUG - Received MESSAGE_STATE_CHANGED (enum
GST_STATE_NULL of type GstState - enum GST_STATE_READY of type GstState)
2015-04-27 04:21:32,006 - DEBUG - Received MESSAGE_STATE_CHANGED (enum
GST_STATE_READY of type GstState - enum GST_STATE_PAUSED of type GstState)
2015-04-27 04:21:32,006 - DEBUG - Received MESSAGE_STATE_CHANGED (enum
GST_STATE_NULL of type GstState - enum GST_STATE_READY of type GstState)
2015-04-27 04:21:32,007 - DEBUG - Received MESSAGE_STATE_CHANGED (enum
GST_STATE_READY of type GstState - enum GST_STATE_PAUSED of type GstState)
2015-04-27 04:21:32,007 - DEBUG - Received MESSAGE_STATE_CHANGED (enum
GST_STATE_READY of type GstState - enum GST_STATE_PAUSED of type GstState)
2015-04-27 04:21:32,007 - DEBUG - Received MESSAGE_STATE_CHANGED (enum
GST_STATE_NULL of type GstState - enum GST_STATE_READY of type GstState)
2015-04-27 04:21:32,008 - DEBUG - Received MESSAGE_STATE_CHANGED (enum
GST_STATE_NULL of type GstState - enum GST_STATE_READY of type GstState)
2015-04-27 04:21:32,008 - DEBUG - Received MESSAGE_STATE_CHANGED (enum
GST_STATE_PAUSED of type GstState - enum GST_STATE_PAUSED of type GstState)
2015-04-27 04:21:32,008 - DEBUG - Received MESSAGE_STATE_CHANGED (enum
GST_STATE_NULL of type GstState - enum GST_STATE_READY of type GstState)
2015-04-27 04:21:32,008 - DEBUG - Received MESSAGE_STATE_CHANGED (enum
GST_STATE_READY of type GstState - enum GST_STATE_PAUSED of type GstState)
2015-04-27 04:21:32,008 - DEBUG - Received MESSAGE_STATE_CHANGED (enum
GST_STATE_READY of type GstState - enum GST_STATE_PAUSED of type GstState)
2015-04-27 04:21:32,008 - DEBUG - Received MESSAGE_STATE_CHANGED (enum
GST_STATE_NULL of type GstState - enum GST_STATE_READY of type GstState)
2015-04-27 04:21:32,009 - DEBUG - Received MESSAGE_STATE_CHANGED (enum
GST_STATE_READY of type GstState - enum GST_STATE_PAUSED of type GstState)
2015-04-27 04:21:32,009 - DEBUG - Received MESSAGE_STATE_CHANGED (enum
GST_STATE_PAUSED of type GstState - enum GST_STATE_PLAYING of type
GstState)
2015-04-27 04:21:32,009 - DEBUG - playing
2015-04-27 04:21:32,049 - DEBUG - Buffering 0
2015-04-27 04:21:32,983 - DEBUG - Buffering 9
2015-04-27 04:21:32,983 - DEBUG - Buffering 0
2015-04-27 04:21:32,983 - DEBUG - Buffering 9
2015-04-27 04:21:32,984 - DEBUG - Buffering 0
2015-04-27 04:21:32,985 - DEBUG - Buffering 9
2015-04-27 04:21:32,985 - DEBUG - Buffering 0
2015-04-27 04:21:32,986 - DEBUG - Received MESSAGE_STATE_CHANGED (enum
GST_STATE_NULL of type GstState - enum GST_STATE_READY of type GstState)
2015-04-27 04:21:32,986 - DEBUG - Received MESSAGE_STATE_CHANGED (enum
GST_STATE_READY of type GstState - enum GST_STATE_PAUSED of type GstState)
2015-04-27 04:21:32,986 - DEBUG - Received MESSAGE_ERROR
2015-04-27 04:21:34,011 - WARNING - Your GStreamer installation is missing a
plug-in.

Bug#782151: Missing OSGi bundle manifest entries

[Damian Minkov]

Package: libcommons-lang3-java
Version: 3.3.2-1

When building upstream with mvn package produces jar which is OSGi enabled.

Bug#736773 will be fixed using workaround, but depends on fixing this one.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736773


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#754586: [jitsi-dev] debcheckout jitsi

[Damian Minkov]

Hi,

On Wed, Sep 17, 2014 at 11:51 PM, Damian Minkov damen...@jitsi.org wrote:
 Hi,



 On Wed, Sep 17, 2014 at 11:40 PM, Kurt Roeckx k...@roeckx.be wrote:
 On Wed, Sep 17, 2014 at 11:21:06PM +0300, Damian Minkov wrote:
 Hi,

 it is the upstream which contains the debian packaging. We commit
 everything in resources/install/debian.
 What's the point of this field if its not the upstream? What should we
 put there?
 I saw there is a bug report about missing vcs fields and I've added
 them with values pointing to the repository containing the sources we
 are currently packaging.

 It seems to contain instruction on how to generate the source
 package from that repository, including having to do a few git
 clone / svn checkouts.  The Vcs-* fields should point to the
 sources like it's in Debian so that people working on
 Debian can make changes to it.  This means among other things
 that there is a debian directory, instead of a
 resources/install/debian.  The full sources shouldn't even be
 there, it could be that the upstream sources are gotten from
 the .orig.tar.gz file.  Or it might have the upstream sources
 too, but most likely not contain the full upstream history, just
 those things that are uploaded to Debian.

 Typically the debian dir is not maintained upstream, but in it's
 own repository like the one in collab-maint.  You seem to have a
 different workflow.  And the Vcs-* fields you added will not result
 in people getting what they expect to find.

 (I don't know if I explained myself good, but I hope you
 understand what I mean.)

 Thanks for clearing it. Are these values correct:

 +Vcs-Git: git://anonscm.debian.org/collab-maint/jitsi.git
 +Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/jitsi.git

 Should we commit there or it is automatically imported? Do we have
 access there? How can we update with current version or it is updated
 after the package is accepted into Debian repo?

I see that you need to be Debian developer to have write access. Also
external developers can be granted access by the developer.
But what I see is that the repository is out of sync, it is missing
the changes for 2.4.4997-1.2. As long as we have our packaging folder,
we need some sort of notifications for changes in the package so we
can merge the changes. Not sure how good is to have one more
repository to sync. Still there is a source package that can be
downloaded with apt-get source and for sure it is in sync, and people
can make changes to it.

Regards
damencho


 Thanks
 damencho



 Kurt



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#754586: [jitsi-dev] debcheckout jitsi

[Damian Minkov]

Hi,

we have added Vcs-* fields in the version that is currently pushed into mentors.
https://mentors.debian.net/package/jitsi

Regards
damencho

On Wed, Sep 17, 2014 at 2:59 PM, Geert Stappers stapp...@stappers.nl wrote:

 Hi,

 It would be nice if

debcheckout jitsi

 would work.
 Bugreport #754586, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754586  
 has allready a patch.
 It is 
 https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=add_vcs_headers.patch;att=1;bug=754586


 Groeten
 Geert Stappers
 --
 Leven en laten leven

 ___
 dev mailing list
 d...@jitsi.org
 Unsubscribe instructions and other list options:
 http://lists.jitsi.org/mailman/listinfo/dev


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#754586: [jitsi-dev] debcheckout jitsi

[Damian Minkov]

Hi,

it is the upstream which contains the debian packaging. We commit
everything in resources/install/debian.
What's the point of this field if its not the upstream? What should we
put there?
I saw there is a bug report about missing vcs fields and I've added
them with values pointing to the repository containing the sources we
are currently packaging.

Regards
damencho


On Wed, Sep 17, 2014 at 10:45 PM, Kurt Roeckx k...@roeckx.be wrote:
 On Wed, Sep 17, 2014 at 04:56:16PM +0300, Damian Minkov wrote:
 Hi,

 we have added Vcs-* fields in the version that is currently pushed into 
 mentors.

 Those seem to point to the upstream git repository that doesn't
 contain the debian packaging.  Those should point to where the
 package as uploaded to Debian is maintained.  I don't think we
 have any way to add the upstream repositories.


 Kurt



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#754586: [jitsi-dev] debcheckout jitsi

[Damian Minkov]

Hi,



On Wed, Sep 17, 2014 at 11:40 PM, Kurt Roeckx k...@roeckx.be wrote:
 On Wed, Sep 17, 2014 at 11:21:06PM +0300, Damian Minkov wrote:
 Hi,

 it is the upstream which contains the debian packaging. We commit
 everything in resources/install/debian.
 What's the point of this field if its not the upstream? What should we
 put there?
 I saw there is a bug report about missing vcs fields and I've added
 them with values pointing to the repository containing the sources we
 are currently packaging.

 It seems to contain instruction on how to generate the source
 package from that repository, including having to do a few git
 clone / svn checkouts.  The Vcs-* fields should point to the
 sources like it's in Debian so that people working on
 Debian can make changes to it.  This means among other things
 that there is a debian directory, instead of a
 resources/install/debian.  The full sources shouldn't even be
 there, it could be that the upstream sources are gotten from
 the .orig.tar.gz file.  Or it might have the upstream sources
 too, but most likely not contain the full upstream history, just
 those things that are uploaded to Debian.

 Typically the debian dir is not maintained upstream, but in it's
 own repository like the one in collab-maint.  You seem to have a
 different workflow.  And the Vcs-* fields you added will not result
 in people getting what they expect to find.

 (I don't know if I explained myself good, but I hope you
 understand what I mean.)

Thanks for clearing it. Are these values correct:

+Vcs-Git: git://anonscm.debian.org/collab-maint/jitsi.git
+Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/jitsi.git

Should we commit there or it is automatically imported? Do we have
access there? How can we update with current version or it is updated
after the package is accepted into Debian repo?

Thanks
damencho



 Kurt



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#735409:

[Damian Minkov]

Hi,

we only bind to this port if it is available. It is also useful and
for registerless accounts.

Regards
damencho


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#760483: ITP: prosody-module-turncredentials -- Prosody module to provide time-limited turn credentials

[Damian Minkov]

Package: wnpp
Severity: wishlist
Owner: Damian Minkov damen...@jitsi.org

* Package name: prosody-module-turncredentials
  Upstream Author : yet contact cont...@andyet.com
* URL : https://github.com/andyet/otalk-server/
* License : MIT/X
  Description : Prosody module to provide time-limited turn credentials

XEP-0215 implementation for time-limited turn credentials. Jitsi Meet depends 
on it
to be able to provide turn/turns host for webrtc clients.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#760485: ITP: jitsi-meet -- WebRTC JavaScript application that uses Jitsi Videobridge to provide high quality, scalable video conferences.

[Damian Minkov]

Package: wnpp
Severity: wishlist
Owner: Damian Minkov damen...@jitsi.org

* Package name: jitsi-meet
  Upstream Author : Jitsi Team d...@jitsi.org
* URL : https://jitsi.org/meet
* License : MIT
  Programming Lang: JavaScript
  Description : WebRTC JavaScript application that uses Jitsi Videobridge 
to provide high quality, scalable video conferences.

Jitsi Meet is an OpenSource (MIT) WebRTC JavaScript application that uses Jitsi 
Videobridge to provide high quality, scalable video conferences.
Jitsi Meet allows for very efficient collaboration. It allows users to stream 
their desktop or only some windows. It also shared document editing with 
Etherpad and remote presentations with Prezi.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#727430: blocking the ppc64el architecture bootstrap

[Damian Viano]

Aurelien:

 By all means feel free to NMU, as I probably won't get tp it before you do.

  Damian.

On Mon, Aug 25, 2014 at 04:42:54AM +0200, Aurelien Jarno wrote:
 Dear maintainer,
 
 The ppc64el architecture has been added to the Debian archive. Your
 package libpcl1 fails to build as reported in bug #727430 and
 the build log is available on [1].
 
 It would be very nice if you can upload a fixed version of this package.
 Don't hesitate to ask questions if you need help to fix this bug. If
 you lack time for that, I can also proceed with an NMU.
 
 Thanks,
 Aurelien
 
 [1] https://buildd.debian.org/status/logs.php?pkg=libpcl1arch=ppc64el
 
 -- 
 Aurelien Jarno  GPG: 4096R/1DDD8C9B
 aurel...@aurel32.net http://www.aurel32.net
 


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#757768: ITP: libjitsi -- advanced Java media library

[Damian Minkov]

Package: wnpp
Severity: wishlist
Owner: Damian Minkov damen...@jitsi.org

* Package name: libjitsi
  Version : 481
* URL : http://www.jitsi.org/libjitsi
* License : LGPL-2.1
  Programming Lang: Java
  Description : advanced Java media library

libjitsi is an advanced Java media library for secure real-time audio/video 
communication. It allows applications to capture, playback, stream, 
encode/decode and encrypt audio and video flows. It also allows for advanced 
features such as audio mixing, handling multiple streams, participation in 
audio and video conferences.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#757769: ITP: jitsi-videobridge -- a WebRTC compatible Selective Forwarding Unit that allows for multiuser video communication

[Damian Minkov]

Package: wnpp
Severity: wishlist
Owner: Damian Minkov damen...@jitsi.org

* Package name: jitsi-videobridge
  Version : 202
* URL : https://jitsi.org/jitsi-videobridge
* License : LGPL-2.1
  Programming Lang: Java
  Description : a WebRTC compatible Selective Forwarding Unit that allows 
for multiuser video communication

Jitsi Videobridge is a WebRTC compatible Selective Forwarding Unit (SFU) that 
allows for multiuser video communication. Unlike expensive dedicated hardware 
videobridges, Jitsi Videobridge does not mix the video channels into a 
composite video stream. It only relays the received video flows to all call 
participants. Therefore, while it does need to run on a server with good 
network bandwidth, CPU horsepower is not critical for performance.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#745099: [Openmama-dev] Fwd: Re: Bug#745099: openmama: FTBFS with Java 8: class MamdaLock is public, should be declared in a file named MamdaLock.java

[Damian Maguire]

Cheers for that Emmanuel, and Daniel for forwarding it on. We'll take a look 
and get this merged into upstream as soon as possible.

Thanks,

Damian

From: Daniel Pocock dan...@pocock.com.aumailto:dan...@pocock.com.au
Date: Friday, August 8, 2014 2:48 PM
To: 
'openmama-...@lists.openmama.orgmailto:'openmama-...@lists.openmama.org' 
openmama-...@lists.openmama.orgmailto:openmama-...@lists.openmama.org, 
745...@bugs.debian.orgmailto:745...@bugs.debian.org 
745...@bugs.debian.orgmailto:745...@bugs.debian.org, Emmanuel Bourg 
ebo...@apache.orgmailto:ebo...@apache.org
Subject: [Openmama-dev] Fwd: Re: Bug#745099: openmama: FTBFS with Java 8: class 
MamdaLock is public, should be declared in a file named MamdaLock.java



Emmanuel, thanks for this fix, I'm sending it to the OpenMAMA developers for 
inclusion upstream


 Original Message 
Subject:Re: Bug#745099: openmama: FTBFS with Java 8: class MamdaLock is 
public, should be declared in a file named MamdaLock.java
Date:   Fri, 08 Aug 2014 15:38:05 +0200
From:   Emmanuel Bourg ebo...@apache.orgmailto:ebo...@apache.org
To: 745...@bugs.debian.orgmailto:745...@bugs.debian.org, Daniel Pocock 
dan...@pocock.com.aumailto:dan...@pocock.com.au



Control: tags -1 patch

Here is a patch fixing this issue. Java 8 was simply not recognized as
Java 5 or later by the Ant build, this skipped the logic to rename
MamdaLock15.java into MamdaLock.java and triggered a compiler error.

Emmanuel Bourg







This message may contain confidential information and is intended for specific 
recipients unless explicitly noted otherwise. If you have reason to believe you 
are not an intended recipient of this message, please delete it and notify the 
sender. This message may not represent the opinion of Intercontinental 
Exchange, Inc. (ICE), Euronext or any of their subsidiaries or affiliates, and 
does not constitute a contract or guarantee. Unencrypted electronic mail is not 
secure and the recipient of this message is expected to provide safeguards from 
viruses and pursue alternate means of communication where privacy or a binding 
message is desired.

Bug#750739: apache2-mpm-worker: Can't start with = 5000 VirtualHosts with 'SSLEngine On' - AH00016: Configuration Failed. sysctl fs.file-max=512000

[INTEN - Damian S. Kołodziejczyk]

 On Mon, 23 Jun 2014, INTEN - Damian S. Kołodziejczyk wrote:
 Strace shows only info about too many open files - so i increase it.
 Nothing more points.

 Have you looked at APACHE_ULIMIT_MAX_FILES in /etc/apache2/envvars? Maybe
 you just need to set a higher value there?


I check - problem still exist.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#743910:

[Damian Nadales]

This workaround solves the problem for me:
https://savannah.gnu.org/bugs/?41099#comment4


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#750739: apache2-mpm-worker: Can't start with = 5000 VirtualHosts with 'SSLEngine On' - AH00016: Configuration Failed. sysctl fs.file-max=512000

[INTEN - Damian S. Kołodziejczyk]

 On Monday 16 June 2014 14:20:27, INTEN - Damian S. Kołodziejczyk
 wrote:
 error log shows only AH00016: Configuration Failed

 If you have separate error logs for ssl virtualhosts, please also
 check those for additional error messages.


Additional error messages was empty - nothig more.

 i increased max openfiles (sysctl fs.file-max=512000) becouse
 i also increased FD_SETSIZE in httpd.

 Did you do this to try to fix this issue or was this an unrelated
 change to fix something else? httpd should not use FD_SETSIZE
 internally (though some library used by httpd may).


Yes - all libs with httpd required.

 Normal virtualhosts = 40 000 and working,
 SSL virtualhosts  5000 and AH00016: Configuration Failed

 You could try to start it under strace -f and try to see if there is
 some system call that fails shortly before this message is printed.

 BTW, you original report said version 2.2.22-13+deb7u1, but the
 AH00016 tag was only introduced in 2.4. Which version do you use
 exactly?


Strace shows only info about too many open files - so i increase it.
Nothing more points.

I checked also on version 2.4 - error also occurs and apparently
this is the version pasted. Today, I went back to 2.2.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#743910:

[Damian Nadales]

I can reproduce the error on Ubuntu 14.04, running the default Octave
and Emacs packages.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#750739: apache2-mpm-worker: Can't start with = 5000 VirtualHosts with 'SSLEngine On' - AH00016: Configuration Failed. sysctl fs.file-max=512000

[INTEN - Damian S. Kołodziejczyk]

 tags 750739 moreinfo
 thanks


 This report does not have enough information. Is there anything
 related in the error log? What do you mean with the sysctl?


error log shows only AH00016: Configuration Failed
i increased max openfiles (sysctl fs.file-max=512000) becouse
i also increased FD_SETSIZE in httpd.
Normal virtualhosts = 40 000 and working,
SSL virtualhosts  5000 and AH00016: Configuration Failed


-- 
Damian S. Kołodziejczyk
INTEN
www.inten.pl * in...@inten.pl


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#750739: apache2-mpm-worker: Can't start with = 5000 VirtualHosts with 'SSLEngine On' - AH00016: Configuration Failed. sysctl fs.file-max=512000

[Damian Kolodziejczyk]

Package: apache2-mpm-worker
Version: 2.2.22-13+deb7u1
Severity: important



-- Package-specific info:
List of enabled modules from 'apache2 -M':
  alias auth_basic authn_file authz_default authz_groupfile
  authz_host authz_user autoindex cgid deflate dir env mime
  negotiation reqtimeout setenvif ssl status

-- System Information:
Debian Release: 7.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-486
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages apache2-mpm-worker depends on:
ii  apache2.2-bin 2.2.22-13+deb7u1
ii  apache2.2-common  2.2.22-13+deb7u1

apache2-mpm-worker recommends no packages.

apache2-mpm-worker suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#750354: Aw: Re: Bug#750354: linux-image-3.2.0-4-kirkwood: usbip-core.ko and usbip-host.ko missing

[Damian Philipp]

 Bug #568903 enabled this feature for x86, [...]

While I can't comment on the evolution of the code, I can offer some 
circumstantial evidence. According to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/900384, Ubuntu has been 
shipping these modules in the default kernel for two years now. Apart from 
PEBKAC-errors mentioned in the bug report and possibly mismatching userland 
tools (which would be another bug report on package usbip, should it affect 
Debian too), a quick google search didn't show problems relating to crashes, 
machine freezes or OOPSes.

From a users perspective: There used to be a source package to build these 
modules on any arch if one wanted to do so (perfectly acceptable solution, in 
my opinion). With the removal of this package and the addition of the drivers 
for x86 only, this breaks the package usbip on anything but x86 (what about 
amd64?). Even worse, there is no way for the average user to get this 
functionality, as the simplest way to get these modules is currently a full 
rebuild of the kernel - but compiling the kernel on (in my case) an ARM 
machine takes just under an eternity and cross-compilation is a pretty 
advanced topic, IMHO.

If including these modules in the default Debian kernel is not an option, 
having a simple solution to get them would be great. 
Either installing them from a separate package or having a low-maintenance way 
to compile just the required modules (without the full kernel rebuild, e.g., 
something involving module-assistant or DKMS) would be sufficient.

Regards,
Damina Philipp


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#749812: [Openmama-dev] Bug#749812: openmama: Wrong number of arguments to mamaConnection_allocate to cause undefined behaviour

[Damian Maguire]

Cheers Damiel, Michael,

There does appear to be an issue there, and it hasn't been fixed in next.
I've raised a bugzilla ticket
(http://bugs.openmama.org/show_bug.cgi?id=104) which can be used to track
the issue, and we'll get a fix sorted.

Cheers, 

Damian



On 5/30/14 11:40 AM, Daniel Pocock dan...@pocock.com.au wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256



Hi Michael,

Thanks for this bug report - as it appears to be an upstream issue,
I'm putting it on the OpenMAMA mailing list for discussion

Regards,

Daniel



On 30/05/14 00:02, Michael Tautschnig wrote:
 Package: openmama Version: 2.2.2.1-10 Usertags: goto-cc
 
 During an analysis of all Debian packages using our research
 compiler tool-chain (using tools from the cbmc package) the
 following error was found:
 
 When invoking mamaConnection_allocate here
 
 
http://sources.debian.net/src/openmama/2.2.2.1-10/mama/jni/src/c/mamaconn
ectionjni.c?hl=139#L139

  only 10 arguments are passed, even though 11 are required. It
 seems the bytesSent parameter is missing, which also causes the
 remaining ones (userName, appName, handle) to take wrong/undefined
 values.
 
 Best, Michael
 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQIcBAEBCAAGBQJTiGAvAAoJEOm1uwJp1aqDjYEP/jLW++UEm0pG3XSwdsveSzBd
nlW4Uao2VQJNH2NgUDLRjLvIALBP2tAHPOWKQY7g8TR9VqrzFngIRmah026SXe+/
Jo0E8TEH/K3ZfLOaSrN1swjCPO1z0WJLltjLPleTBU4f+RHZJ86ldJ1UnglSTlrW
NuKisio7VWZtAjMKqlThjvHVXbJrUxFoKb/gHX4p587Ptryg+blVyhBql0h3xgf4
sQo9TN8Zg7RqDk7+41FW/IVAMbQRyqrZs1C4Pt9lL6bTtFBqoujxk5Gu6UPCXIGy
kQHMX6Cd+/hIcx3YH6bCFO1HEpeXdHA7LmzS2Lv0aUimVvBeBB90ERXJgyTmwGoG
05gi/WQFTF6PgcODf0bkZlFxO8uu9HDbaRkHFTt4Lx24oMEGBGQk/Fz+fSYczwLH
aZDtZAbepNFTLQ1mgIvJbysZNxghXJLOwr4cPI9lpkI5GxRlHK0vjFgbjhRXAdRk
DwYEqNjsFXtBPLyuusHvXhPEKO2T/bvYxChFBWfe9VbPj4E3E5li2UbRLYcv+cXr
j11eaBjYo9kNq8vCMXKXeF4qQlvXe7ZyArBmRHKu8jrSYiXGeZxNJzJRlzIvys1p
4XyAHZZ9FKO47qk/kukRXBq737SZby+TCEPm8O/ILvu+F0nPjbyIZadj989MFBjM
EG7YgVZTyZzvXYuBnJRP
=00uq
-END PGP SIGNATURE-
___
Openmama-dev mailing list
openmama-...@lists.openmama.org
https://lists.openmama.org/mailman/listinfo/openmama-dev



This message may contain confidential information and is intended for specific 
recipients unless explicitly noted otherwise. If you have reason to believe you 
are not an intended recipient of this message, please delete it and notify the 
sender. This message may not represent the opinion of IntercontinentalExchange 
Group, Inc. (ICE), NYSE Euronext or any of their subsidiaries or affiliates, 
and does not constitute a contract or guarantee. Unencrypted electronic mail is 
not secure and the recipient of this message is expected to provide safeguards 
from viruses and pursue alternate means of communication where privacy or a 
binding message is desired.



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#750354: linux-image-3.2.0-4-kirkwood: usbip-core.ko and usbip-host.ko missing

[Damian Philipp]

Package: src:linux
Version: 3.2.57-3+deb7u1
Severity: important

Dear Maintainer,

modules usbip-core.ko and usbip-host.ko (and possibly other
usbip-related modules) are missing from the Debian kernel. As usbip
itself is offered as a package, I believe the modules should be present.

I suspect the modules' absence is due to the following line, extracted
from /boot/config-3.2.0-4-kirkwood:

 # CONFIG_USBIP_CORE is not set

* What led up to the situation?

$ apt-get install usbip
$ sudo usbipd -D
usbipd: error: please load usbip-core.ko and usbip-host.ko!
$ sudo modprobe usbip-core
FATAL: Module usbip-core not found.

* What outcome did you expect instead?

I expected the module(s) to load and, subsequently, usbip to work.

-- Package-specific info:
** Version:
Linux version 3.2.0-4-kirkwood (debian-ker...@lists.debian.org) (gcc version 
4.6.3 (Debian 4.6.3-14) ) #1 Debian 3.2.57-3

** Command line:
console=ttyS0,115200 root=/dev/ram initrd=0xa0,0x90 ramdisk=34816

** Tainted: C (1024)
 * Module from drivers/staging has been loaded.

** Kernel log:
[2070899.969390] Did not find alt setting 1 for intf 0, config 1
[2070945.026027] Did not find alt setting 1 for intf 0, config 1
[2070990.025258] Did not find alt setting 1 for intf 0, config 1
[2071035.024697] Did not find alt setting 1 for intf 0, config 1
[2071069.408365] Did not find alt setting 1 for intf 0, config 1
[2071071.422382] Did not find alt setting 1 for intf 0, config 1
[2071073.422756] Did not find alt setting 1 for intf 0, config 1
[2071075.423107] Did not find alt setting 1 for intf 0, config 1
[2071076.344966] usb 1-1.4.1: USB disconnect, device number 9
[2071087.587514] usb 1-1.4.1: new high-speed USB device number 10 using 
orion-ehci
[2071087.708092] usb 1-1.4.1: New USB device found, idVendor=03f0, 
idProduct=5611
[2071087.715525] usb 1-1.4.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[2071087.723284] usb 1-1.4.1: Product: Photosmart C3100 series
[2071087.728926] usb 1-1.4.1: Manufacturer: HP
[2071087.733130] usb 1-1.4.1: SerialNumber: CN738C300N04P9
[2071087.743934] usblp0: USB Bidirectional printer dev 10 if 1 alt 0 proto 2 
vid 0x03F0 pid 0x5611
[2071087.766213] scsi7 : usb-storage 1-1.4.1:1.3
[2071088.784305] scsi 7:0:0:0: Direct-Access HP   Photosmart C3180 1.00 
PQ: 0 ANSI: 2
[2071088.795830] sd 7:0:0:0: Attached scsi generic sg2 type 0
[2071088.805155] sd 7:0:0:0: [sdc] Attached SCSI removable disk
[2071188.195281] usblp0: removed
[2071188.199283] Did not find alt setting 1 for intf 0, config 1
[2071258.658264] Did not find alt setting 1 for intf 0, config 1
[2071303.657639] Did not find alt setting 1 for intf 0, config 1
[2071348.657189] Did not find alt setting 1 for intf 0, config 1
[2071393.657947] Did not find alt setting 1 for intf 0, config 1
[2071438.657431] Did not find alt setting 1 for intf 0, config 1
[2071483.657072] Did not find alt setting 1 for intf 0, config 1
[2071542.776966] usb 1-1.4.1: USB disconnect, device number 10
[2071555.812751] usb 1-1.4.1: new high-speed USB device number 11 using 
orion-ehci
[2071555.923467] usb 1-1.4.1: New USB device found, idVendor=03f0, 
idProduct=5611
[2071555.930830] usb 1-1.4.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[2071555.938571] usb 1-1.4.1: Product: Photosmart C3100 series
[2071555.944246] usb 1-1.4.1: Manufacturer: HP
[2071555.948446] usb 1-1.4.1: SerialNumber: CN738C300N04P9
[2071555.956686] usblp0: USB Bidirectional printer dev 11 if 1 alt 0 proto 2 
vid 0x03F0 pid 0x5611
[2071556.037585] scsi8 : usb-storage 1-1.4.1:1.3
[2071557.035680] scsi 8:0:0:0: Direct-Access HP   Photosmart C3180 1.00 
PQ: 0 ANSI: 2
[2071557.047034] sd 8:0:0:0: Attached scsi generic sg2 type 0
[2071557.055650] sd 8:0:0:0: [sdc] Attached SCSI removable disk
[2071658.232967] usb 1-1.4.1: USB disconnect, device number 11
[2071658.239682] usblp0: removed
[2071670.499250] usb 1-1.4.1: new high-speed USB device number 12 using 
orion-ehci
[2071670.609866] usb 1-1.4.1: New USB device found, idVendor=03f0, 
idProduct=5611
[2071670.617130] usb 1-1.4.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[2071670.624848] usb 1-1.4.1: Product: Photosmart C3100 series
[2071670.630482] usb 1-1.4.1: Manufacturer: HP
[2071670.634680] usb 1-1.4.1: SerialNumber: CN738C300N04P9
[2071670.662883] usblp0: USB Bidirectional printer dev 12 if 1 alt 0 proto 2 
vid 0x03F0 pid 0x5611
[2071670.715658] scsi9 : usb-storage 1-1.4.1:1.3
[2071671.719794] scsi 9:0:0:0: Direct-Access HP   Photosmart C3180 1.00 
PQ: 0 ANSI: 2
[2071671.733703] sd 9:0:0:0: Attached scsi generic sg2 type 0
[2071671.742153] sd 9:0:0:0: [sdc] Attached SCSI removable disk
[2071902.710106] usblp0: removed
[2071902.725344] Did not find alt setting 1 for intf 0, config 1
[2071956.944911] Did not find alt setting 1 for intf 0, config 1
[2072102.190400] Did not find alt setting 1 for intf 0, config 1
[2072155.218286] Did not find alt setting 1 for intf 0, config 1
[2072185.219128] Did 

Bug#745099: [Openmama-dev] OpenJDK 1.8?

[Damian Maguire]

Hey Daniel,

I haven't taken a look at OpenJDK 1.8 at all yet to be honest, though it's
certainly something I'm interested in getting to. I believe there are a few
others in the community who have been running with it during the last 1.8
release candidates, and I haven't heard any real complaints from them. I'd
expect as 1.8 becomes more popular a they may start hitting any issues
there are out there anyway, which will likely drive through a few fixes in
the coming months. That said, it's not really on my roadmap at present, so
unless there's a bit of demand from the community we're unlikely to be
spending too much time on it.

In terms of official support from NYSE for the Enterprise Edition of
OpenMAMA, they don't at present support any version of the OpenJDK at all
(due to some legacy issues), and I don't believe that's likely to change
any time soon.

Cheers,

Damian


On Sat, May 3, 2014 at 7:08 AM, Daniel Pocock dan...@pocock.com.au wrote:



 Debian/Ubuntu try to follow recent JVMs.

 OpenMAMA wiki suggests JDK 1.6 and above.

 The next stable releases of Debian and Ubuntu (end of 2014/early 2015)
 may have OpenJDK 1.8, the previous OpenMAMA release is troublesome with
 that, I haven't checked if 2.3.0 fixes it:

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

 Is there likely to be any testing with OpenJDK 1.8 in the next few months?


   compile.locks:
   [javac] /«PKGBUILDDIR»/mamda/java/build.xml:145: warning:
 'includeantruntime' was not set, defaulting to build.sysclasspath=last;
 set to false for repeatable builds
   [javac] Compiling 2 source files to
 /«PKGBUILDDIR»/mamda/java/classes_orderbook
   [javac] warning: [options] bootstrap class path not set in
 conjunction with -source 1.4
   [javac] warning: [options] source value 1.4 is obsolete and will
 be removed in a future release
   [javac] warning: [options] target value 1.4 is obsolete and will
 be removed in a future release
   [javac] warning: [options] To suppress warnings about obsolete
 options, use -Xlint:-options.
   [javac]
 /«PKGBUILDDIR»/mamda/java/temp/com/wombat/mamda/locks/MamdaLock14.java:24:
 error: class MamdaLock is public, should be declared in a file named
 MamdaLock.java
   [javac] public class MamdaLock
   [javac]^
   [javac]
 /«PKGBUILDDIR»/mamda/java/temp/com/wombat/mamda/locks/MamdaLock15.java:25:
 error: class MamdaLock is public, should be declared in a file named
 MamdaLock.java
   [javac] public class MamdaLock extends ReentrantReadWriteLock
   [javac]^
   [javac] 2 errors
   [javac] 4 warnings


 The full build log is available from:


 http://87.98.165.193/debian/openjdk8-rebuild/logs-failed-jdk8/openmama_2.2.2.1-10_unstable_jdk8.log
 ___
 Openmama-dev mailing list
 openmama-...@lists.openmama.org
 https://lists.openmama.org/mailman/listinfo/openmama-dev

Bug#746477: /usr/bin/conky: conky terminates after several minutes with you don't need that many fonts message

[Damian]

Hi,

I have created a pull request on github.

Regards
 Damian

Am 01.05.2014 06:42, schrieb Vincent Cheng:

On Wed, Apr 30, 2014 at 4:12 AM, Me m...@arcsin.de wrote:

Package: conky-std
Version: 1.9.0-2
Severity: normal
File: /usr/bin/conky

Dear Maintainer,

conky terminates reproducibly after several minutes on my system logging the
following:

Conky: desktop window (183) is subwindow of root window (d3)
Conky: window type - desktop
Conky: drawing to created window (0x2e2)
Conky: drawing to double buffer
Conky: you don't need that many fonts, sorry.

In between, conky works as expected. The following patch helps:

--- conky-1.9.0.orig/src/specials.c
+++ conky-1.9.0/src/specials.c
@@ -330,6 +330,15 @@ void new_gauge(struct text_object *obj,
  }

  #ifdef X11
+int find_font(char *name)
+{
+int i;
+for (i = 0; i  font_count; i++)
+if (strncmp(name, fonts[i].name, DEFAULT_TEXT_BUFFER_SIZE)
== EQUAL)
+return i;
+return 0;
+}
+
  void new_font(char *buf, char *args)
  {
 if ((output_methods  TO_X) == 0)
@@ -337,6 +346,13 @@ void new_font(char *buf, char *args)

 if (args) {
 struct special_t *s = new_special(buf, FONT);
+   int index;
+
+if (index = find_font(args))
+{
+s-font_added = index;
+return;
+}

 if (s-font_added  font_count || !s-font_added ||
(strncmp(args, fonts[s-font_added].name, DEFAULT_TEXT_BUFFER_SIZE) !=
EQUAL) ) {
 int tmp = selected_font;


Can you forward the patch upstream [1]? Thanks!

Regards,
Vincent

[1] https://github.com/brndnmtthws/conky



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#721547: libregexp-grammars-perl: Currently incompatible with Perl 5.18

[Damian Conway]

Thanks for the CC, Salvatore.

I've added a note to my ToDo list to revisit the module within the next month.

BTW, only 4 of the module's 921 tests fail under 5.19.9, so we're very
very close
to okay for Perl 5.20. :-)

Damian


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#734808: jitsi: Extra JavaEmbeddedFrame window, broken tray, unable to un-minimize (Gnome 3)

[Damian Minkov]

I believe this is a java problem, more on the subject:

https://bugzilla.redhat.com/show_bug.cgi?id=683768
https://bugzilla.gnome.org/show_bug.cgi?id=648773

Regards
damencho



On Fri, Jan 10, 2014 at 2:15 AM, Gerald Turner gtur...@unzane.com wrote:

 There is an email thread on jitsi-dev from March 2013 that describes
 these same problems with an older version of Jitsi and on Fedora, Arch,
 and Mint.

   http://lists.jitsi.org/pipermail/dev/2013-March/000150.html
   http://lists.jitsi.org/pipermail/dev/2013-June/017618.html

 Sorry, I probably should've reported upstream.

 --
 Gerald Turner   Email: gtur...@unzane.com   JID: gtur...@unzane.com
 GPG: 0xFA8CD6D5  21D9 B2E8 7FE7 F19E 5F7D  4D0C 3FA0 810F FA8C D6D5

Bug#729992: jitsi: settings dialog box doesn't have a way to close it

[Damian Minkov]

Java dialogs cannot control the appearance/disappearance of a window's close
button. Eclipse (which uses SWT) also lacks the close button in Gnome,
so we assume this is a problem with a theme design.

On Wed, Nov 20, 2013 at 1:23 AM, Kurt Roeckx k...@roeckx.be wrote:
 Package: jitsi
 Version: 2.3.4909-1

 Hi,

 If I go to the menu Tools - Options I get different behavior
 depending on what machine I use:
 - On amd64 in xfce there are icons to maximize, and close
   the the dialog in the upper right corner.  And one to just
   show the window caption.
   (The main window and chat windows all have an additional
   minimize icon)
 - On i386 with gnome there are no icons in the option window.
   (The other windows have minimize, maximize, close.)

 I'm not sure if this is a jitsi problem, or maybe some problem
 with some toolkit.  Please reassign if you think this is a bug
 somewhere else.


 Kurt


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#719585: jitsi: Reports time in UTC instead of the local timezone

[Damian Minkov]

Is it properly set in /etc/timezone?

I see a lot of reports for java wrong detecting the timezone on
Internet, so this can be related, do you have another java application
to check whether date is correctly displayed?

On Mon, Nov 18, 2013 at 10:59 PM, Kurt Roeckx k...@roeckx.be wrote:
 Hi,

 I'm still seeing this with 2.3.4909-1

 This is for messages comming and going to facebook.  The clock on
 my PC reported 21:28, facebook shows that it was at 9:28pm, but
 jitsi shows it as 20:28.

 My locale is set to en_US, my /etc/localtime is set for
 Europe/Brussels and everything shows the time properly.

 jitsi shows it as Nov 18, 2013 20:28:48


 Kurt

 On Fri, Aug 23, 2013 at 02:13:40PM +0300, Damian Minkov wrote:
 Hi,

 did you change the timezone while jitsi was running? Currently
 timezone change while running is not supported.
 Timestamps are normally shown on my side. If I change timezone (using
 # dpkg-reconfigure tzdata as described in
 https://wiki.debian.org/TimeZoneChanges) and then start jitsi
 everything seems fine and timestamps of history are updated correctly
 and those for incoming and outgoing messages also shows the localtime
 of the machine.

 Regards
 damencho


 On Tue, Aug 13, 2013 at 1:43 PM, Kurt Roeckx k...@roeckx.be wrote:
  Package: jitsi
  Version: 2.3.4687.9786-1
 
  When chatting with someone, the timestamps are shown in UTC
  instead of the local time zone that I set on the system.
 
 
  Kurt



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#726652: #726652: jitsi fails to build on Wheezy

[Damian Minkov]

We have dependency on libbcpkix-java, but while building libjitsi
library a symlink to that lib is missing.
Working on updating the package and will fix it.


On Fri, Nov 8, 2013 at 7:00 PM, Kurt Roeckx k...@roeckx.be wrote:
 On Fri, Nov 08, 2013 at 05:26:40PM +0100, Tzafrir Cohen wrote:
 More information:

 The sole missing build dependency was libbcpkix-java . I rebuilt the
 source package (bouncycastle) on wheezy in a clean chroot and then tried
 building jitsi in a chroot of wheezy+(backported bouncycastle).

 Result: http://tzafrir.org.il/~tzafrir/jitsi_2.3.4687.9786-1_amd64.build

 I'm not sure what you're saying.  There is a build-dependency on
 libbcpkix-java already.  Are you saying we need a versioned
 depedency?


 Kurt


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#719517: jitsi: FTBFS against libav9

[Damian Minkov]

We will be updating the package, and fixing this and several other
bugs in the following days.


On Wed, Nov 6, 2013 at 6:37 PM, Maarten Aertsen spam-deb...@rtsn.nl wrote:
 Package: jitsi
 Version: 2.3.4687.9786-1
 Followup-For: Bug #719517

 Dear Maintainer,

 with libavfilter2 no longer available in testing or unstable, jitsi has 
 become effectively uninstallable. I have been looking through the jitsi 
 mailinglist archives (dev, user), but cannot find any further discussion of 
 this issue.

 After the debconf talks and the announcement that jitsi got accepted into 
 Debian, I convinced a lot of my immediate friends and family to try jitsi and 
 have succesfully used it for cross-platform rtc (brilliant!). But having 
 recently switched from Ubuntu to Debian testing, this issue renders it 
 impossible to continue using it myself :-)

 Could you please provide a status update, or perhaps point to the relevant 
 resources tracking progress if you feel this is not the right place to do so?


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

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


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#719517: Processed: tagging 719517

[Damian Minkov]

Yeah we know about it, but there are more errors than those that were
spotted at the time of writing the pointed email. Errors for missing
functions like ff_set_common_formats, cause it is now a private one
for internal use,  ... now all the logic used for hflipping the video
preview needs to be rewritten.


On Fri, Aug 30, 2013 at 6:30 PM, Moritz Muehlenhoff j...@inutil.org wrote:
 On Thu, Aug 29, 2013 at 10:16:01AM +0300, Damian Minkov wrote:
 Hi,
 we will be working on this these days, hope to provide a fix soon. The
 initial effort show there needs to be done some more work cause of a
 change in libav filter api.

 I suppose you've been 
 https://java.net/projects/jitsi/lists/dev/archive/2013-04/message/223
 already?

 Cheers,
 Moritz


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#719517: Processed: tagging 719517

[Damian Minkov]

Hi,
we will be working on this these days, hope to provide a fix soon. The
initial effort show there needs to be done some more work cause of a
change in libav filter api.

Regards
damencho



On Thu, Aug 29, 2013 at 9:55 AM, Raphael Hertzog hert...@debian.org wrote:
 Hi,

 On Wed, 28 Aug 2013, Kurt Roeckx wrote:
  Bug #719517 [jitsi] jitsi: FTBFS against libav9

 This make no sense at all.  The sid tag probably doesn't do what
 you expect.

 It does only affect sid, because it's only in sid.  But tagging it
 sid will now has effect that it could move to testing since it
 doesn't affect testing.

 That's precisely my goal. The package does work in testing, doesn't it?

 It does mean that it would get entangled in the current transition
 but that shouldn't be a problem assuming that Damian can provide
 a fix for this bug.

 Cheers,
 --
 Raphaël Hertzog ◈ Debian Developer

 Discover the Debian Administrator's Handbook:
 → http://debian-handbook.info/get/


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#719201: jitsi: Has it's own spelling check dictionaries

[Damian Minkov]

Hi,

yes for different operating system we download spellchecks from our
location on user request. Till now we haven't make use of any locally
installed dictionaries, but we will be working on that, to provide use
of debian installed dictionaries if any.

Cheers


On Fri, Aug 9, 2013 at 11:26 AM, Kurt Roeckx k...@roeckx.be wrote:
 Package: jitsi
 Version: 2.0.4506.10553-1

 Hi,

 It seems jitsi supports spell checking.  But it seems to download
 them and store them in ~/.jitsi/spellingDictionaries/.


 We ship spelling dictionaries already in debian, they are in
 /usr/share/hunspell/, and are used by all programs making use
 of hunspell.  For Dutch it now downloads an old version, while
 Debian has had a newer version for ages.

 It would be good that jitsi could make use of the dictionaries
 provided by the system.  This should maybe be optional, I guess
 not all systems where jitsi runs have a central place to store
 dictionaries.


 Kurt


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#719999: jitsi: unable to register an account on first start

[Damian Minkov]

Control: tag -1 fixed-upstream

Hi,

this was already fixed in upstream jitsi. We will be updating the
package soon with some other fixes and with this one, so stay tuned.

Regards
damencho


On Sat, Aug 17, 2013 at 7:50 PM, Vincent Bernat ber...@debian.org wrote:
  ❦ 17 août 2013 18:03 CEST, Kurt Roeckx k...@roeckx.be :

 On Sat, Aug 17, 2013 at 04:44:51PM +0200, Vincent Bernat wrote:
 Package: jitsi
 Version: 2.3.4687.9786-1
 Severity: normal

 Hi!

 I have tried to just Jitsi with my XMPP account. Unfortunately, when I
 enter my credentials in the XMPP box and click Sign In, I get the
 following traceback in the console:

 Can you try openjdk-6 instead of -7?

 I get the exact same error:

 18:48:14.996 GRAVE: [13] util.UtilActivator.uncaughtException().109 An 
 uncaught exception occurred in thread=Thread[AWT-EventQueue-0,6,main] and 
 message was: No user ID provided.
 java.lang.IllegalStateException: No user ID provided.
 at 
 net.java.sip.communicator.plugin.jabberaccregwizz.JabberAccountRegistrationForm.commitPage(JabberAccountRegistrationForm.java:286)
 at 
 net.java.sip.communicator.plugin.jabberaccregwizz.FirstWizardPage.commitPage(FirstWizardPage.java:121)
 at 
 net.java.sip.communicator.plugin.jabberaccregwizz.JabberAccountRegistrationWizard.signin(JabberAccountRegistrationWizard.java:245)
 at 
 net.java.sip.communicator.plugin.simpleaccreg.InitialAccountRegistrationFrame$AccountRegistrationPanel.signin(InitialAccountRegistrationFrame.java:474)
 at 
 net.java.sip.communicator.plugin.simpleaccreg.InitialAccountRegistrationFrame$SigninActionListener.actionPerformed(InitialAccountRegistrationFrame.java:569)
 at 
 javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2012)
 at 
 javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2335)
 at 
 javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:404)
 at 
 javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:259)
 at 
 javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:252)
 at java.awt.Component.processMouseEvent(Component.java:6288)
 at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
 at java.awt.Component.processEvent(Component.java:6053)
 at java.awt.Container.processEvent(Container.java:2045)
 at java.awt.Component.dispatchEventImpl(Component.java:4649)
 at java.awt.Container.dispatchEventImpl(Container.java:2103)
 at java.awt.Component.dispatchEvent(Component.java:4475)
 at 
 java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4633)
 at 
 java.awt.LightweightDispatcher.processMouseEvent(Container.java:4297)
 at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4227)
 at java.awt.Container.dispatchEventImpl(Container.java:2089)
 at java.awt.Window.dispatchEventImpl(Window.java:2587)
 at java.awt.Component.dispatchEvent(Component.java:4475)
 at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:675)
 at java.awt.EventQueue.access$300(EventQueue.java:96)
 at java.awt.EventQueue$2.run(EventQueue.java:634)
 at java.awt.EventQueue$2.run(EventQueue.java:632)
 at java.security.AccessController.doPrivileged(Native Method)
 at 
 java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:108)
 at 
 java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:119)
 at java.awt.EventQueue$3.run(EventQueue.java:648)
 at java.awt.EventQueue$3.run(EventQueue.java:646)
 at java.security.AccessController.doPrivileged(Native Method)
 at 
 java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:108)
 at java.awt.EventQueue.dispatchEvent(EventQueue.java:645)
 at 
 java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
 at 
 java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
 at 
 java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
 at 
 java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
 at 
 java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
 at java.awt.EventDispatchThread.run(EventDispatchThread.java:138)

 OpenJDK Runtime Environment (IcedTea6 1.12.6) (6b27-1.12.6-1)
 OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)

 Also, at start, I have this:

 Auto-properties install: reference:file:sc-bundles/galagonotification.jar 
 (org.osgi.framework.BundleException: Unable to cache bundle: 
 reference:file:sc-bundles/galagonotification.jar - java.io.IOException: 
 Referenced file does not exist: sc-bundles/galagonotification.jar)
 org.osgi.framework.BundleException: Unable to cache bundle: 
 

Bug#719199: jitsi: Support more arches

[Damian Minkov]

Hi,

we never have tried using other arches, although we had some reports
of building for them (some arm arches), of course the only problem can
be some of the natives we use. And never had tested there also.

Regards
damencho


On Fri, Aug 9, 2013 at 11:08 AM, Kurt Roeckx k...@roeckx.be wrote:
 Package: jitsi
 Version: 2.0.4506.10553-1
 Severity: wishlist

 Hi,

 The package currently only builds on i386 and amd64.  I would like
 to see this supported on more of our arches.

 What are the reasons this is currently on those arches other than
 that are the only ones that upstreams tests?


 Kurt


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#719278: Same Problem on my Debian Sid AMD64

[Damian Minkov]

Hi,

_JITSI_LIBAV_ is always defined when building the debian package. In
upstream we use ffmpeg.
The problem you see is because of the update of libav package to
version 0.9... This will be fixed while fixing bug#719517.
Currently looking at it.

Regards
damencho


On Sat, Aug 10, 2013 at 4:54 PM, MERLIN Philippe
phil-deb1.mer...@laposte.net wrote:
 Me too, On my Debian Sid  AMD64 jitsi crashes when i goto the options video.
 Same message :
 warning: The VAD has been replaced by a hack pending a complete rewrite
 /usr/bin/java: symbol lookup error: /usr/lib/jni/libjnffmpeg.so: undefined
 symbol: ff_make_format_list.
 Cheers
 Philippe Merlin


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#719996: jitsi: Display broken with jdk7

[Damian Minkov]

Hi,

could you also add what is the desktop environment you use?
Using latest sid of debian-7 with jre7 and gnome3 works fine.
Any exceptions in the logs?

Thanks
damencho



On Sat, Aug 17, 2013 at 5:18 PM, Edward Allcutt edw...@allcutt.me.ukwrote:

 Package: jitsi
 Version: 2.3.4687.9786-1
 Severity: normal

 Dear Maintainer,

 After installing openjdk-7-jre, on starting jitsi the main window displays
 just a grey box.

 Switching back to java6 with update-alternatives currently works as a
 workaround.

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

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

 Versions of packages jitsi depends on:
 ii  default-jre [java6-runtime]1:1.7-49
 ii  libbcprov-java 1.44+dfsg-3.1
 ii  libcommons-codec-java  1.8-1
 ii  libcommons-logging-java1.1.3-1
 ii  libdbus-java   2.8-4
 ii  libdnsjava-java2.1.5-0.1
 ii  libfelix-framework-java4.0.1-2
 ii  libfelix-main-java 4.0.1-2
 ii  libhttpclient-java 4.2.5-2
 ii  libhttpcore-java   4.3-1
 ii  libhttpmime-java   4.2.5-2
 ii  libjgoodies-forms-java 1.6.0-4
 ii  libjitsi-jni   2.3.4687.9786-1
 ii  libjmdns-java  3.4.1-2
 ii  libjna-java3.2.7-4+b1
 ii  libjson-simple-java1.1-dfsg1-2
 ii  libjzlib-java  1.1.2-1
 ii  liblaf-widget-java 4.3-2
 ii  liblog4j1.2-java   1.2.17-3
 ii  libmac-widgets-java0.9.5+svn369-dfsg1-3
 ii  libunixsocket-java 0.7.3-1
 ii  libxpp3-java   1.1.4c-2
 ii  openjdk-6-jre [java6-runtime]  6b27-1.12.5-2
 ii  openjdk-7-jre [java6-runtime]  7u21-2.3.9-5

 jitsi recommends no packages.

 jitsi suggests no packages.

 -- no debconf information

Bug#719585: jitsi: Reports time in UTC instead of the local timezone

[Damian Minkov]

Hi,

did you change the timezone while jitsi was running? Currently
timezone change while running is not supported.
Timestamps are normally shown on my side. If I change timezone (using
# dpkg-reconfigure tzdata as described in
https://wiki.debian.org/TimeZoneChanges) and then start jitsi
everything seems fine and timestamps of history are updated correctly
and those for incoming and outgoing messages also shows the localtime
of the machine.

Regards
damencho


On Tue, Aug 13, 2013 at 1:43 PM, Kurt Roeckx k...@roeckx.be wrote:
 Package: jitsi
 Version: 2.3.4687.9786-1

 When chatting with someone, the timestamps are shown in UTC
 instead of the local time zone that I set on the system.


 Kurt


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#708692: Package update

[Damian Minkov]

Hi,

I've updated the package. Sorry it was by mistake that I used an old
package. Now it must be ok.


On Fri, Jul 26, 2013 at 1:06 PM, Raphael Hertzog hert...@debian.org wrote:
 Hi Damian,

 On Tue, 23 Jul 2013, Damian Minkov wrote:
 dnsjava package was updated with new upstream version and was updated
 to remove the internet connectivity requirement and the package
 download.

 The respective dsc file can be found at:
 http://mentors.debian.net/debian/pool/main/d/dnsjava/dnsjava_2.1.5-0.1.dsc

 The debdiff between this package and the former version shows many
 unexpected changes, including changing the changelog entry of 2.1.4-0.1.

 Is this on purpose or is it a mistake because you prepared the update on
 top of an obsolete version of the package ?

 In any case, don't do that. If you have to revert changes made in the
 version before, say so explicitely but don't touch the former changelog
 entry.

 Please prepare an updated package based on the .dsc which is in
 Debian:
 http://http.debian.net/debian/pool/main/d/dnsjava/dnsjava_2.1.4-0.1.dsc

 BTW, since I sponsored the former upload you should have put me in CC...
 it's by pure luck that I found this mail.

 iDebdiff:
 --- dnsjava-2.1.4/debian/changelog  2013-03-26 16:16:37.0 +0100
 +++ dnsjava-2.1.5/debian/changelog  2013-07-23 10:26:48.0 +0200
 @@ -1,25 +1,20 @@
 +dnsjava (2.1.5-0.1) unstable; urgency=low
 +
 +  * Non-maintainer upload.
 +  * New upstream release.
 +  * Update to remove internet connectivity requirement. (Closes: #708692)
 +
 + -- Damian Minkov damen...@jitsi.org  Tue, 23 Jul 2013 11:25:28 +0300
 +
  dnsjava (2.1.4-0.1) unstable; urgency=low

 -  [ Damian Minkov ]
* Non-maintainer upload.
 -  * New upstream release. (Closes: #699033)
 +  * New upstream release.
* Changed the source format to 3.0 (quilt).
 -  * Switched debhelper's compatibility level from 5 to 9.
 -  * Added patch to build bundle jar by default, that adds support
 -  for an OSGi bundle.
 -  * Removed a bad field from debian/control (XSBC-Original-Maintainer).
 -  * Changed Build-Depends switched debhelper version to 9.
 -  * Increased Standards-Version to 3.9.3.
 -  * Changed debian/rules to rename the built jar OSGi bundle file to the name
 -  used in the package.
 -
 -  [ Raphaël Hertzog ]
 -  * Sponsoring the upload.
 -  * Drop Dm-Upload-Allowed field from debian/control since it's no longer 
 used
 -by dak.
 -  * Drop the useless debian/libdnsjava-java.jlibs.
 +  * Switched debhelper's compatility level from 5 to 9.
 +  * Added patch

 - -- Damian Minkov damen...@jitsi.org  Tue, 26 Mar 2013 10:45:35 +0200
 + -- Damian Minkov damen...@jitsi.org  Mon, 18 Mar 2013 17:05:45 +0200

 --
 Raphaël Hertzog ◈ Debian Developer

 Discover the Debian Administrator's Handbook:
 → http://debian-handbook.info/get/

 --
 To unsubscribe, send mail to 708692-unsubscr...@bugs.debian.org.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#708692: Package update

[Damian Minkov]

Now it should be fine, sorry once again.

On Fri, Jul 26, 2013 at 5:01 PM, Raphael Hertzog hert...@debian.org wrote:
 On Fri, 26 Jul 2013, Damian Minkov wrote:
 Hi,

 I've updated the package. Sorry it was by mistake that I used an old
 package. Now it must be ok.

 Hum, I don't find the fix for this bug anymore on your updated package
 (no Build-Depends on bnd, no corresponding patch).

 Did I miss something?

 Cheers,
 --
 Raphaël Hertzog ◈ Debian Developer

 Discover the Debian Administrator's Handbook:
 → http://debian-handbook.info/get/


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#708692: Package update

[Damian Minkov]

dnsjava package was updated with new upstream version and was updated
to remove the internet connectivity requirement and the package
download.

The respective dsc file can be found at:
http://mentors.debian.net/debian/pool/main/d/dnsjava/dnsjava_2.1.5-0.1.dsc


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#695588: RFS: jitsi/1.1.4365-1 [ITP]

[Damian Minkov]

Hi,

we've just updated the package on mentors.debian.net following the
comments we recieved:
The dsc file can be found at:
http://mentors.debian.net/debian/pool/main/j/jitsi/jitsi_2.0.4506.10553-1.dsc

Regards
Damian

On Mon, Dec 10, 2012 at 3:13 PM, Damian Minkov damen...@jitsi.org wrote:
   Package: sponsorship-requests
   Severity: wishlist


   Dear mentors,

   We are looking for a sponsor for our package jitsi

  * Package name: jitsi
Version : 1.1.4365-1
Upstream Author : Jitsi Community d...@jitsi.java.net
  * URL : https://jitsi.org/
  * License : LGPL v2
Section : net

   It builds those binary packages:

 jitsi - Java VoIP and Instant Messaging client
  jitsi-jni  - Jitsi JNI library

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

   http://mentors.debian.net/package/jitsi

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

 dget -x
 http://mentors.debian.net/debian/pool/main/j/jitsi/jitsi_1.1.4365-1.dsc

   More information about Jitsi can be obtained from https://jitsi.org and
 the developers mailinglist: d...@jitsi.java.net.

   Regards,
Damian Minkov


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#702651: nvidia-glx-legacy-96xx: NVIDIA driver is not working after installation, due to wrong alternatives configuration

[Damian]

Package: nvidia-glx-legacy-96xx
Version: 96.43.23-3
Severity: important

At the first place, to get the bug, you need to have set:

APT::Install-Recommends true;

in your apt configuration (I have it in /etc/apt/apt.conf.d/99synaptic). 

It is set by Synaptic package in my case, which is not instlaled by default if 
I remember correctly (default Debian installation from CD), so most people may 
not have this bug in their system until they install Synaptic. 

More, I am not even sure, if default Synaptic installation sets this config 
option for apt, it may be set, by me manually (not by editing 
/etc/apt/apt.conf.d/99synaptic, but in Synaptic Options in GUI).


What is the possible problem?

After apt-get install nvidia-glx-legacy-96xx (with recommended) you get this in 
console (Polish language version):
---
root@XXX:/home/YYY apt-get install nvidia-glx-legacy-96xx
Czytanie list pakietów... Gotowe
Budowanie drzewa zależności   
Odczyt informacji o stanie... Gotowe
Zostaną zainstalowane następujące dodatkowe pakiety:
  dkms glx-alternative-mesa glx-alternative-nvidia glx-diversions 
libgl1-nvidia-alternatives
  libgl1-nvidia-legacy-173xx-glx libgl1-nvidia-legacy-96xx-glx 
libglx-nvidia-alternatives
  linux-headers-3.2.0-4-686-pae linux-headers-3.2.0-4-common 
linux-headers-686-pae
  linux-kbuild-3.2 nvidia-alternative-legacy-173xx 
nvidia-alternative-legacy-96xx
  nvidia-installer-cleanup nvidia-kernel-common nvidia-kernel-legacy-96xx-dkms
  nvidia-settings-legacy-173xx nvidia-support pkg-config
  xserver-xorg-video-nvidia-legacy-173xx xserver-xorg-video-nvidia-legacy-96xx
Sugerowane pakiety:
  nvidia-glx nvidia-kernel-legacy-173xx-dkms nvidia-kernel-legacy-173xx-source
Zostaną zainstalowane następujące NOWE pakiety:
  dkms glx-alternative-mesa glx-alternative-nvidia glx-diversions 
libgl1-nvidia-alternatives
  libgl1-nvidia-legacy-173xx-glx libgl1-nvidia-legacy-96xx-glx 
libglx-nvidia-alternatives
  linux-headers-3.2.0-4-686-pae linux-headers-3.2.0-4-common 
linux-headers-686-pae
  linux-kbuild-3.2 nvidia-alternative-legacy-173xx 
nvidia-alternative-legacy-96xx
  nvidia-glx-legacy-96xx nvidia-installer-cleanup nvidia-kernel-common
  nvidia-kernel-legacy-96xx-dkms nvidia-settings-legacy-173xx nvidia-support 
pkg-config
  xserver-xorg-video-nvidia-legacy-173xx xserver-xorg-video-nvidia-legacy-96xx
0 aktualizowanych, 23 nowo instalowanych, 0 usuwanych i 0 nieaktualizowanych.
Konieczne pobranie 9197 kB/16,3 MB archiwów.
Po tej operacji zostanie dodatkowo użyte 95,0 MB miejsca na dysku.
Kontynuować [T/n]?  
---

What you see, is a lot of packages, which is not wrong by itself, but we have 
some 173xx versions here, and we are installing 96xx version! So the question 
is, are these packages really needed (libgl1-nvidia-legacy-173xx-glx and 
nvidia-alternative-legacy-173xx)? Shouldn't there be 96xx equivalent of them 
created? 


OK so what is the problem?

After insallation, Xorg.conf reconfiguration for nvidia driver and reboot, 
Xorg fails to start. I have found that the problem is here:

update-alternatives --config nvidia

  Wybór   Ścieżka Priorytet  Status

* 0/usr/lib/nvidia/legacy-173xx   173   tryb auto
  1/usr/lib/nvidia/legacy-173xx   173   tryb ręczny
  2/usr/lib/nvidia/legacy-96xx96tryb ręczny

As you see we have auto mode which selects /usr/lib/nvidia/legacy-173xx as it 
is having higer priority (173), but we need to have it set to 
/usr/lib/nvidia/legacy-96xx. Simply by manually forcing this alternative 
configuration to position 2:

  Wybór   Ścieżka Priorytet  Status

  0/usr/lib/nvidia/legacy-173xx   173   tryb auto
  1/usr/lib/nvidia/legacy-173xx   173   tryb ręczny
* 2/usr/lib/nvidia/legacy-96xx96tryb ręczny

problem disappears, and Xorg is working properly.

So you need to check where the bug really is:
1. are these, wrong recommended 173xx version packages, that are not suitable 
for 96xx nvidia
2. or recommended packages are OK, and the problem is only with wrong 
alternatives configuration set by one of them

At the end, I will say, the problem is introduced in 96.43.23-3 version of 
nvidia-glx-legacy-96xx. Earlier version worked OK for me.
 
-- Package-specific info:
uname -a:
Linux debest.dodus.orge.pl 3.2.0-4-686-pae #1 SMP Debian 3.2.35-2 i686 GNU/Linux

/proc/version:
Linux version 3.2.0-4-686-pae (debian-ker...@lists.debian.org) (gcc version 
4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.35-2

/proc/driver/nvidia/version:
NVRM version: NVIDIA Linux x86 Kernel Module  96.43.23  Fri Aug 31 14:52:31 PDT 
2012
GCC version:  gcc version 4.6.3 (Debian 4.6.3-14) 

lspci 'VGA compatible controller [0300]':
01:00.0 VGA compatible controller [0300]: NVIDIA 

Bug#695588: RFS: jitsi/1.1.4365-1 [ITP]

[Damian Minkov]

Package: sponsorship-requests
Severity: wishlist


Dear mentors,

We are looking for a sponsor for our package jitsi

Package name: jitsi
Version : 1.1.4365-1
Upstream Author : Jitsi Community d...@jitsi.java.net
URL : https://jitsi.org/
License : LGPL v2
Section : net

It builds those binary packages:

 jitsi - Java VoIP and Instant Messaging client
 jitsi-jni  - Jitsi JNI library

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

  http://mentors.debian.net/package/jitsi


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

  dget -x 
http://mentors.debian.net/debian/pool/main/j/jitsi/jitsi_1.1.4365-1.dsc

More information about Jitsi can be obtained from https://jitsi.org
and the developers mailinglist: d...@jitsi.java.net.

Regards,
Damian Minkov

Bug#690880: phpldapadmin: Fails to work until php5-cgi is installed

[Lisandro Damian Nicanor Perez Meyer]

Package: phpldapadmin
Version: 1.2.2-5
Severity: normal

It simply doesn't works until php5-cgi is installed.
Should it recommend/suggest it? Or even maybe depend on it?

Kinds regards, Lisandro.

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

Kernel: Linux 3.2.0-3-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages phpldapadmin depends on:
ii  apache2 2.2.22-11
ii  apache2-mpm-worker [httpd]  2.2.22-11
ii  debconf [debconf-2.0]   1.5.46
ii  php5-cli5.4.4-7
ii  php5-ldap   5.4.4-7
ii  ucf 3.0025+nmu3

phpldapadmin recommends no packages.

phpldapadmin suggests no packages.

-- Configuration Files:
/etc/phpldapadmin/templates/creation/alias.xml [Errno 13] Permission denied: 
u'/etc/phpldapadmin/templates/creation/alias.xml'
/etc/phpldapadmin/templates/creation/courierMailAccount.xml [Errno 13] 
Permission denied: 
u'/etc/phpldapadmin/templates/creation/courierMailAccount.xml'
/etc/phpldapadmin/templates/creation/courierMailAlias.xml [Errno 13] Permission 
denied: u'/etc/phpldapadmin/templates/creation/courierMailAlias.xml'
/etc/phpldapadmin/templates/creation/dNSDomain.xml [Errno 13] Permission 
denied: u'/etc/phpldapadmin/templates/creation/dNSDomain.xml'
/etc/phpldapadmin/templates/creation/example.xml [Errno 13] Permission denied: 
u'/etc/phpldapadmin/templates/creation/example.xml'
/etc/phpldapadmin/templates/creation/inetOrgPerson.xml [Errno 13] Permission 
denied: u'/etc/phpldapadmin/templates/creation/inetOrgPerson.xml'
/etc/phpldapadmin/templates/creation/kolabPerson.xml [Errno 13] Permission 
denied: u'/etc/phpldapadmin/templates/creation/kolabPerson.xml'
/etc/phpldapadmin/templates/creation/mozillaOrgPerson.xml [Errno 13] Permission 
denied: u'/etc/phpldapadmin/templates/creation/mozillaOrgPerson.xml'
/etc/phpldapadmin/templates/creation/organizationalRole.xml [Errno 13] 
Permission denied: 
u'/etc/phpldapadmin/templates/creation/organizationalRole.xml'
/etc/phpldapadmin/templates/creation/ou.xml [Errno 13] Permission denied: 
u'/etc/phpldapadmin/templates/creation/ou.xml'
/etc/phpldapadmin/templates/creation/posixAccount.xml [Errno 13] Permission 
denied: u'/etc/phpldapadmin/templates/creation/posixAccount.xml'
/etc/phpldapadmin/templates/creation/posixGroup.xml [Errno 13] Permission 
denied: u'/etc/phpldapadmin/templates/creation/posixGroup.xml'
/etc/phpldapadmin/templates/creation/sambaDomain.xml [Errno 13] Permission 
denied: u'/etc/phpldapadmin/templates/creation/sambaDomain.xml'
/etc/phpldapadmin/templates/creation/sambaGroupMapping.xml [Errno 13] 
Permission denied: u'/etc/phpldapadmin/templates/creation/sambaGroupMapping.xml'
/etc/phpldapadmin/templates/creation/sambaMachine.xml [Errno 13] Permission 
denied: u'/etc/phpldapadmin/templates/creation/sambaMachine.xml'
/etc/phpldapadmin/templates/creation/sambaSamAccount.xml [Errno 13] Permission 
denied: u'/etc/phpldapadmin/templates/creation/sambaSamAccount.xml'
/etc/phpldapadmin/templates/creation/sendmailMTAAliasObject.xml [Errno 13] 
Permission denied: 
u'/etc/phpldapadmin/templates/creation/sendmailMTAAliasObject.xml'
/etc/phpldapadmin/templates/creation/sendmailMTAClass.xml [Errno 13] Permission 
denied: u'/etc/phpldapadmin/templates/creation/sendmailMTAClass.xml'
/etc/phpldapadmin/templates/creation/sendmailMTACluster.xml [Errno 13] 
Permission denied: 
u'/etc/phpldapadmin/templates/creation/sendmailMTACluster.xml'
/etc/phpldapadmin/templates/creation/sendmailMTAMapObject.xml [Errno 13] 
Permission denied: 
u'/etc/phpldapadmin/templates/creation/sendmailMTAMapObject.xml'
/etc/phpldapadmin/templates/creation/sendmailVirtualDomain.xml [Errno 13] 
Permission denied: 
u'/etc/phpldapadmin/templates/creation/sendmailVirtualDomain.xml'
/etc/phpldapadmin/templates/creation/sendmailVirtualUser.xml [Errno 13] 
Permission denied: 
u'/etc/phpldapadmin/templates/creation/sendmailVirtualUser.xml'
/etc/phpldapadmin/templates/creation/simpleSecurityObject.xml [Errno 13] 
Permission denied: 
u'/etc/phpldapadmin/templates/creation/simpleSecurityObject.xml'
/etc/phpldapadmin/templates/modification/inetOrgPerson.xml [Errno 13] 
Permission denied: u'/etc/phpldapadmin/templates/modification/inetOrgPerson.xml'
/etc/phpldapadmin/templates/modification/posixGroup.xml [Errno 13] Permission 
denied: u'/etc/phpldapadmin/templates/modification/posixGroup.xml'
/etc/phpldapadmin/templates/template.dtd [Errno 13] Permission denied: 
u'/etc/phpldapadmin/templates/template.dtd'

-- debconf information:
* phpldapadmin/restart-webserver: true
  phpldapadmin/ldap-bindpw: secret
* phpldapadmin/ldap-tls: false
* phpldapadmin/ldap-binddn: cn=admin,dc=gisee,dc=uns,dc=edu,dc=ar
* phpldapadmin/reconfigure-webserver: apache2
* phpldapadmin/ldap-basedn: dc=gisee,dc=uns,dc=edu,dc=ar
* phpldapadmin/ldap-server: 127.0.0.1
* 

Bug#680555: installation-reports bug

[Damian Montaldo]

Package: installation-reports

Boot method:  netboot
Image version: 
http://ftp.nl.debian.org/debian/dists/wheezy/main/installer-amd64/current/images/netboot/netboot.tar.gz
Date: 06 July 2012

Machine:
Processor: Intel Core i7 CPU 950 @3.07GHz
Memory: 4GB
Partitions: not partion

Output of lspci -knn (or lspci -nn):
00:00.0 Host bridge [0600]: Intel Corporation 5520/5500/X58 I/O Hub to
ESI Port [8086:3405] (rev 13)
Subsystem: Intel Corporation Device [8086:5042]
00:01.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI
Express Root Port 1 [8086:3408] (rev 13)
Kernel driver in use: pcieport
00:03.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI
Express Root Port 3 [8086:340a] (rev 13)
Kernel driver in use: pcieport
00:07.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI
Express Root Port 7 [8086:340e] (rev 13)
Kernel driver in use: pcieport
00:10.0 PIC [0800]: Intel Corporation 5520/5500/X58 Physical and Link
Layer Registers Port 0 [8086:3425] (rev 13)
00:10.1 PIC [0800]: Intel Corporation 5520/5500/X58 Routing and
Protocol Layer Registers Port 0 [8086:3426] (rev 13)
00:14.0 PIC [0800]: Intel Corporation 5520/5500/X58 I/O Hub System
Management Registers [8086:342e] (rev 13)
Kernel driver in use: i7core_edac
00:14.1 PIC [0800]: Intel Corporation 5520/5500/X58 I/O Hub GPIO and
Scratch Pad Registers [8086:3422] (rev 13)
00:14.2 PIC [0800]: Intel Corporation 5520/5500/X58 I/O Hub Control
Status and RAS Registers [8086:3423] (rev 13)
00:14.3 PIC [0800]: Intel Corporation 5520/5500/X58 I/O Hub Throttle
Registers [8086:3438] (rev 13)
00:19.0 Ethernet controller [0200]: Intel Corporation 82567LM-2
Gigabit Network Connection [8086:10cc]
Subsystem: Intel Corporation Device [8086:]
Kernel driver in use: e1000e
00:1a.0 USB controller [0c03]: Intel Corporation 82801JI (ICH10
Family) USB UHCI Controller #4 [8086:3a37]
Subsystem: Intel Corporation Device [8086:5042]
Kernel driver in use: uhci_hcd
00:1a.1 USB controller [0c03]: Intel Corporation 82801JI (ICH10
Family) USB UHCI Controller #5 [8086:3a38]
Subsystem: Intel Corporation Device [8086:5042]
Kernel driver in use: uhci_hcd
00:1a.2 USB controller [0c03]: Intel Corporation 82801JI (ICH10
Family) USB UHCI Controller #6 [8086:3a39]
Subsystem: Intel Corporation Device [8086:5042]
Kernel driver in use: uhci_hcd
00:1a.7 USB controller [0c03]: Intel Corporation 82801JI (ICH10
Family) USB2 EHCI Controller #2 [8086:3a3c]
Subsystem: Intel Corporation Device [8086:5042]
Kernel driver in use: ehci_hcd
00:1b.0 Audio device [0403]: Intel Corporation 82801JI (ICH10 Family)
HD Audio Controller [8086:3a3e]
Subsystem: Intel Corporation Device [8086:0022]
Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family)
PCI Express Root Port 1 [8086:3a40]
Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family)
PCI Express Port 2 [8086:3a42]
Kernel driver in use: pcieport
00:1c.4 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family)
PCI Express Root Port 5 [8086:3a48]
Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation 82801JI (ICH10
Family) USB UHCI Controller #1 [8086:3a34]
Subsystem: Intel Corporation Device [8086:5042]
Kernel driver in use: uhci_hcd
00:1d.1 USB controller [0c03]: Intel Corporation 82801JI (ICH10
Family) USB UHCI Controller #2 [8086:3a35]
Subsystem: Intel Corporation Device [8086:5042]
Kernel driver in use: uhci_hcd
00:1d.2 USB controller [0c03]: Intel Corporation 82801JI (ICH10
Family) USB UHCI Controller #3 [8086:3a36]
Subsystem: Intel Corporation Device [8086:5042]
Kernel driver in use: uhci_hcd
00:1d.7 USB controller [0c03]: Intel Corporation 82801JI (ICH10
Family) USB2 EHCI Controller #1 [8086:3a3a]
Subsystem: Intel Corporation Device [8086:5042]
Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge
[8086:244e] (rev 90)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801JIR (ICH10R) LPC
Interface Controller [8086:3a16]
Subsystem: Intel Corporation Device [8086:5042]
00:1f.2 IDE interface [0101]: Intel Corporation 82801JI (ICH10 Family)
4 port SATA IDE Controller #1 [8086:3a20]
Subsystem: Intel Corporation Device [8086:5042]
Kernel driver in use: ata_piix
00:1f.3 SMBus [0c05]: Intel Corporation 82801JI (ICH10 Family) SMBus
Controller [8086:3a30]
Subsystem: Intel Corporation Device [8086:5042]
Kernel driver in use: i801_smbus
00:1f.5 IDE interface [0101]: Intel Corporation 82801JI (ICH10 Family)
2 port SATA IDE Controller #2 [8086:3a26]
Subsystem: Intel Corporation Device [8086:5042]
Kernel driver in use: ata_piix
02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218
[GeForce 

Bug#661832: systemconfigurator: Grub2 support

[Damian Montaldo]

Package: systemconfigurator
Version: 2.2.11-1
Severity: normal

systemconfigurator doesn't support Grub2
The script Boot/Grub.pm build a config file for an old and deprecated grub 
version and fail to install grub2 bootloader.
I also reported the bug in the sourceforge support page of this project but 
there is no releases or news until 2007 (5 years)

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

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages systemconfigurator depends on:
ii  libappconfig-perl  1.56-2Perl module for configuration file
ii  libnet-netmask-perl1.9015-4  parse, manipulate and lookup IP ne
ii  perl   5.10.1-17squeeze3 Larry Wall's Practical Extraction 

systemconfigurator recommends no packages.

systemconfigurator suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#646080:

[Damian Johnson]

Thanks Jeff! Fixed those issues in the snapshot handler...
https://gitweb.torproject.org/arm.git/commitdiff/c40d50313588cc472b426f9b6d4450dbe9d49084



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org