Bug#1041327: RFS: libtypec/0.3-1 [RFP] -- Development files for an interface for USB-C port management

2023-12-01 Thread Colin King (gmail)

Hi Balint,


On 16/11/2023 18:55, Bálint Réczey wrote:

Hi Colin,

Colin King (gmail)  ezt írta (időpont: 2023.
nov. 16., Cs, 17:46):


Hi Balint,


Since libtypec installs include files and libs to the standard
locations actually there is no need to set those paths.
I think I would use the following patch:

--- a/libtypec.pc.in
+++ b/libtypec.pc.in
@@ -1,12 +1,9 @@
   prefix=/usr
   exec_prefix=/usr
-libdir=${exec_prefix}/lib/x86_64-linux-gnu
-includedir=${prefix}/

   Name: libtypec
   Description: USB-Type C and USB Power Delivery class devices
   Version: 0.4.0

   Requires:
-Libs: -L${libdir} -llibtypec
-Cflags: -I${includedir}
+Libs: -llibtypec



I think this patch application did not work out as intended, please
check the patched file.

The symbols file's first line is also still off and now the symbos
have debian package revisions.

Those are issues automatically detected by Lintian. I suggest running
lintian on the built binary packages' .changes file or populating the
packaging repository on Salsa where CI runs include lintian and many
other checks.


I ran lintian but I didn't see the errors, I used:

lintian --profile=debian --pedantic libtypec_0.4-3_source.changes

perhaps there are some extra lintian flags or config settings that I'm 
missing. Any suggestions?


Colin





Cheers,
Balint


Ah, good idea. I've refreshed package with this change. Also updated the
.symbols file and uploaded a -4 to mentors.

Colin




Bug#1056183: texlive-luatex: lualatex exits immediately due to new zlib

2023-11-18 Thread Nick Black (Public gmail account)
Package: texlive-luatex
Version: 2023.20231007-1
Severity: important
X-Debbugs-Cc: dankamong...@gmail.com

Dear Maintainer,

I recently updated zlib1g:amd64 (1:1.2.13.dfsg-3, 1:1.3.dfsg-2) in unstable.

lualatex immediately stopped working, with the error:

[schwarzgerat](0) $ lualatex
PANIC: unprotected error in call to Lua API (zlib library version does not
match - header: 1.2.13, library: 1.3)
Aborted (core dumped)
[schwarzgerat](134) $

Should just need a rebuild, but perhaps this (unnecessary?) check ought be
removed? Isn't this what SOVERSIONs are for?


-- Package-specific info:
IMPORTANT INFORMATION: We will only consider bug reports concerning
the packaging of TeX Live as relevant. If you have problems with
combination of packages in a LaTeX document, please consult your
local TeX User Group, the comp.text.tex user group, the author of
the original .sty file, or any other help resource. 

In particular, bugs that are related to up-upstream, i.e., neither
Debian nor TeX Live (upstream), but the original package authors,
will be closed immediately.

   *** The Debian TeX Team is *not* a LaTeX Help Desk ***

If you report an error when running one of the TeX-related binaries 
(latex, pdftex, metafont,...), or if the bug is related to bad or wrong
output, please include a MINIMAL example input file that produces the
error in your report.

Please run your example with
(pdf)latex -recorder ...
(or any other program that supports -recorder) and send us the generated
file with the extension .fls, it lists all the files loaded during
the run and can easily explain problems induced by outdated files in
your home directory.

Don't forget to also include minimal examples of other files that are 
needed, e.g. bibtex databases. Often it also helps
to include the logfile. Please, never send included pictures!

If your example file isn't short or produces more than one page of
output (except when multiple pages are needed to show the problem),
you can probably minimize it further. Instructions on how to do that
can be found at

http://www.minimalbeispiel.de/mini-en.html (english)

or 

http://www.minimalbeispiel.de/mini.html (german)

##
minimal input file


##
other files

##
 List of ls-R files

-rw-r--r-- 1 root root 2496 2023-11-10 04:56 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 2022-10-12 17:25 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 2023-10-08 16:00 /usr/share/texlive/texmf-dist/ls-R 
-> /var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 2023-10-08 16:00 /usr/share/texlive/texmf-dist/ls-R 
-> /var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 475 2023-08-28 14:30 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 2023-10-08 16:00 /usr/share/texmf/web2c/fmtutil.cnf 
-> /var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 2023-10-08 16:00 /usr/share/texmf/web2c/updmap.cfg -> 
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 5289 2023-11-10 04:54 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 2016-02-22 09:54 mktex.cnf
-rw-r--r-- 1 root root 475 2023-08-28 14:30 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf

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

Kernel: Linux 6.5.9nlb2 (SMP w/64 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages texlive-luatex depends on:
ii  libjs-jquery  3.6.1+dfsg+~3.5.14-1
ii  lmodern   2.005-1
ii  tex-common6.18
ii  texlive-base  2023.20231007-1
ii  texlive-binaries  2023.20230311.66589-7

texlive-luatex recommends no packages.

texlive-luatex suggests no packages.

Versions of packages tex-common depends on:
ii  ucf  3.0043+nmu1

Versions of packages tex-common suggests:
ii  debhelper  13.11.8

Versions of packages texlive-luatex is related to:
ii  tex-common6.18
ii  texlive-binaries  2023.20230311.66589-7

-- no debconf information



Bug#1041327: RFS: libtypec/0.3-1 [RFP] -- Development files for an interface for USB-C port management

2023-11-16 Thread Colin King (gmail)

Hi Balint,


Since libtypec installs include files and libs to the standard
locations actually there is no need to set those paths.
I think I would use the following patch:

--- a/libtypec.pc.in
+++ b/libtypec.pc.in
@@ -1,12 +1,9 @@
  prefix=/usr
  exec_prefix=/usr
-libdir=${exec_prefix}/lib/x86_64-linux-gnu
-includedir=${prefix}/

  Name: libtypec
  Description: USB-Type C and USB Power Delivery class devices
  Version: 0.4.0

  Requires:
-Libs: -L${libdir} -llibtypec
-Cflags: -I${includedir}
+Libs: -llibtypec



Ah, good idea. I've refreshed package with this change. Also updated the 
.symbols file and uploaded a -4 to mentors.


Colin



Bug#1041327: RFS: libtypec/0.3-1 [RFP] -- Development files for an interface for USB-C port management

2023-11-16 Thread Colin King (gmail)

Hi again Balint,

On 16/11/2023 11:35, Bálint Réczey wrote:

Hi Colin,

Thanks for the quick response.
Please check my other observations, too, in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041327#58


You mentioned:

"The .pc file is now at the right location, but contains multiarch
strings which will differ across architectures.
I suggest hardcoding the paths in the patch."

I'm not quite sure what is incorrect here, this file is patched already 
via debian/patches/0001-fix-libtypec-libdir.patch


For an i386 build, the .pc file in usr/share/pkgconfig contains:

prefix=/usr
exec_prefix=/usr
libdir=${exec_prefix}/lib/i386-linux-gnu
includedir=${prefix}/include/i386-linux-gnu
..

For a x86-64 build, the .pc file in usr/share/pkgconfig contains:
prefix=/usr
exec_prefix=/usr
libdir=${exec_prefix}/lib/x86_64-linux-gnu
includedir=${prefix}/include/x86_64-linux-gnu
..

For an arm64 build, the .pc file in usr/share/pkgconfig contains:
prefix=/usr
exec_prefix=/usr
libdir=${exec_prefix}/lib/aarch64-linux-gnu
includedir=${prefix}/include/aarch64-linux-gnu
..

..so I'm a bit confused. Do you mind clarifying for me.

Colin



Bug#1041327: RFS: libtypec/0.3-1 [RFP] -- Development files for an interface for USB-C port management

2023-11-16 Thread Colin King (gmail)

On 15/11/2023 13:47, Bálint Réczey wrote:

Hi Colin,

There are a few upstream source files licensed under GPL.
Please update debian/copyright to cover all the used licenses.


Updated and uploaded -3 to mentors

Thanks for the prompt review feedback. Much appreciated.

Colin



You can run 'cme update dpkg-copyright' in the source directory or any 
other tool from https://wiki.debian.org/CopyrightReviewTools 
<https://wiki.debian.org/CopyrightReviewTools> to help with the manual 
labor.


Cheers,
Balint

On 2023. Nov 15., Wed at 10:27, Bálint Réczey <mailto:bal...@balintreczey.hu>> wrote:


Hi Colin,

    Colin King (gmail) mailto:colin.i.k...@gmail.com>> ezt írta (időpont: 2023.
nov. 14., K, 17:58):
 >
 > Hi Balint,
 >
 > I've uploaded 0.4.0-2 with the suggested fixes.
 >
 > reply inlined below:
 >
 > On 09/11/2023 16:23, Bálint Réczey wrote:
 > > Hi Colin,
 > >
 > > Colin King (gmail) mailto:colin.i.k...@gmail.com>> ezt írta (időpont: 2023.
 > > nov. 7., K, 15:18):
 > >>
 > >> Hi Balint,
 > >>
 > >> Thanks for responding with the review. I was waiting for the
upstream
 > >> project to release a 0.4 with some minor fixes before
re-uploading to
 > >> mentors.
 > >>
 > >> I've addressed the issues you found as below:
 > >
 > > Please see my observations below.
 > >
 > >> On 22/10/2023 22:38, Bálint Réczey wrote:
 > >>> Hi Colin,
 > >>>
 > >>> I've checked the second upload at [1].
 > >>> As you can see in the Lintian warnings there is a .git
directory which
 > >>> is not ideal for a source package.
 > >>> I suggest using the most widely used git-buildpackage based
workflow
 > >>> where the gbp command takes care of exporting the source package
 > >>> without the .git dir from the packaging repository.
 > >>> I'd be happy to set up a packaging repo for you at
 > >>> https://salsa.debian.org/debian/libtypec
<https://salsa.debian.org/debian/libtypec> and add you as a maintainer
 > >>> as described in [2]
 > >
 > > I still hold up my offer about setting up a git repo for
packaging on
 > > Salsa. That comes with the benefit of automated fixes from Debian
 > > Janitor and I could also comment on changes right where they
happened.
 >
 > Thank you for your kind offer; I definitely think this is a good
idea,
 > please can you set this up for me. Much appreciated!

I've created the repo at https://salsa.debian.org/debian/libtypec
<https://salsa.debian.org/debian/libtypec> and
added you as a maintainer.
I've also set up CI, thus when you push your branches the pipelines
will start.

You may already be familiar with
https://dep-team.pages.debian.net/deps/dep14/
<https://dep-team.pages.debian.net/deps/dep14/> , but if not, please
check it before pushing your packaging repository.

...

 > > I think my comment here was misleading, sorry for that.
 > > Shipping *.pc is desired, shipping it in the .../libtypec.pc/
dir as a
 > > result of specifying .../libtypec.pc as the target dir in the
.install
 > > file was not desired. It was even patched to have the right
content.
 > > Please ship the .pc file in the -dev package.
 >
 > Fixed.

The .pc file is now at the right location, but contains multiarch
strings which will differ across architectures.
I suggest hardcoding the paths in the patch.

...

 > > * As you switched back to use upstream's 0.4.0 SO version the
.symbols
 > > file became wrong  not matching the shipped SO version. Please fix
 > > that and also switch to the libtypec0 package name since it
needs to
 > > match upstream's major SO version
 >
 > Fixed.

The .symbols file's first line should be:
  libtypec.so.0 libtypec0 #MINVER#

See deb-symbols(5) for more details.

 > .
 > >
 > > * I'd recommend asking upstream to switch to semantic SO versioning
 > > instead of using the project's version and switching to major
version
 > > 1 when the API stabilized.
 >
 > Good idea. Will do when API changes and stabilizes.

Great!

Cheers,
Balint

 > Colin
 >
 > >
 > > Cheers,
 > > Balint
 > >
 > >> Kind regards,
 > >>
 > >> Colin
 > >>
 > >>
 > >>>

Bug#1041327: RFS: libtypec/0.3-1 [RFP] -- Development files for an interface for USB-C port management

2023-11-14 Thread Colin King (gmail)

Hi Balint,

I've uploaded 0.4.0-2 with the suggested fixes.

reply inlined below:

On 09/11/2023 16:23, Bálint Réczey wrote:

Hi Colin,

Colin King (gmail)  ezt írta (időpont: 2023.
nov. 7., K, 15:18):


Hi Balint,

Thanks for responding with the review. I was waiting for the upstream
project to release a 0.4 with some minor fixes before re-uploading to
mentors.

I've addressed the issues you found as below:


Please see my observations below.


On 22/10/2023 22:38, Bálint Réczey wrote:

Hi Colin,

I've checked the second upload at [1].
As you can see in the Lintian warnings there is a .git directory which
is not ideal for a source package.
I suggest using the most widely used git-buildpackage based workflow
where the gbp command takes care of exporting the source package
without the .git dir from the packaging repository.
I'd be happy to set up a packaging repo for you at
https://salsa.debian.org/debian/libtypec and add you as a maintainer
as described in [2]


I still hold up my offer about setting up a git repo for packaging on
Salsa. That comes with the benefit of automated fixes from Debian
Janitor and I could also comment on changes right where they happened.


Thank you for your kind offer; I definitely think this is a good idea, 
please can you set this up for me. Much appreciated!





Other observations regarding the packaging:

* There is debian/install and also there are binary package specific
*.install files which is slightly confusing.
 I suggest dropping debian/install.


Fixed


* In the debian/*.install files you need to specify only the target
dir, not the target file.


Fixed


In libtypec-dev
/usr/share/pkgconfig/${DEB_HOST_MULTIARCH}/libtypec.pc/libtypec.pc
gets shipped, which is not desired.


Fixed


I think my comment here was misleading, sorry for that.
Shipping *.pc is desired, shipping it in the .../libtypec.pc/ dir as a
result of specifying .../libtypec.pc as the target dir in the .install
file was not desired. It was even patched to have the right content.
Please ship the .pc file in the -dev package.


Fixed




* libtypec.h seems to be the same on all architectures. Does it have
to be shipped in a multiarch include location?


Fixed. Now in /usr/include and in the multiarch include location


* Binary packages in debian/control are not marked as Multi-Arch: same
* Please target experimental. The package needs to pass NEW and to
migrate to testing it will need a new source-only upload anyway.



Fixed.

Please review the 0.4 release upload and let me know if this can be
sponsored further to the changes I made.


* Both libtypec-dev.install and libtypec1.install lists
usr/lib/${DEB_HOST_MULTIARCH} and as a result both packages ship the
*.so symlink and *.so.0.4.0.
Please ship *.so.0.4.0 in the library package and the *.so symlink in
the -dev package only.


Fixed.



* As you switched back to use upstream's 0.4.0 SO version the .symbols
file became wrong  not matching the shipped SO version. Please fix
that and also switch to the libtypec0 package name since it needs to
match upstream's major SO version


Fixed.

.


* I'd recommend asking upstream to switch to semantic SO versioning
instead of using the project's version and switching to major version
1 when the API stabilized.


Good idea. Will do when API changes and stabilizes.

Colin



Cheers,
Balint


Kind regards,

Colin



Cheers,
Balint

[1] https://mentors.debian.net/package/libtypec/
[2] 
https://wiki.debian.org/Salsa/Doc#Collaborative_Maintenance:_.22Debian.22_group

On Thu, 3 Aug 2023 17:00:58 +0100 "Colin King (gmail)"
 wrote:

Hi,

I've uploaded a fixed package that addresses these issues.

Colin

On 18/07/2023 08:50, Adam Borowski wrote:

On Mon, Jul 17, 2023 at 03:29:13PM +0100, Colin King (gmail) wrote:

* Package name : libtypec
  Version  : 0.3-1
* URL  : https://github.com/Rajaram-Regupathy/libtypec



 libtypec1 - generic interface for efficient USB-C port management
 libtypec-dev - Development files for an interface for USB-C port management



libtypec (0.3-1) unstable; urgency=low
.
  * Initial release (Closes: #1023477)
  * Add patch 0001-fix-libtypec-so-version.patch to fix .so name version


Hi!
Before doing manual review, let's start with lintian:

E: libtypec1: pkg-config-multi-arch-wrong-dir full text contains architecture 
specific dir x86_64-linux-gnu [usr/share/pkgconfig/libtypec.pc]
W: libtypec-dev: empty-binary-package
W: libtypec1: lacks-unversioned-link-to-shared-library example: 
usr/lib/x86_64-linux-gnu/libtypec.so 
[usr/lib/x86_64-linux-gnu/libtypec.so.0.3.0]
W: libtypec1: link-to-shared-library-in-wrong-package 
usr/lib/x86_64-linux-gnu/libtypec.so.0.3.0 
[usr/lib/x86_64-linux-gnu/libtypec.so]


Meow!













Bug#1041327: RFS: libtypec/0.3-1 [RFP] -- Development files for an interface for USB-C port management

2023-11-07 Thread Colin King (gmail)

Hi Balint,

Thanks for responding with the review. I was waiting for the upstream 
project to release a 0.4 with some minor fixes before re-uploading to 
mentors.


I've addressed the issues you found as below:

On 22/10/2023 22:38, Bálint Réczey wrote:

Hi Colin,

I've checked the second upload at [1].
As you can see in the Lintian warnings there is a .git directory which
is not ideal for a source package.
I suggest using the most widely used git-buildpackage based workflow
where the gbp command takes care of exporting the source package
without the .git dir from the packaging repository.
I'd be happy to set up a packaging repo for you at
https://salsa.debian.org/debian/libtypec and add you as a maintainer
as described in [2]

Other observations regarding the packaging:

* There is debian/install and also there are binary package specific
*.install files which is slightly confusing.
I suggest dropping debian/install.


Fixed


* In the debian/*.install files you need to specify only the target
dir, not the target file.


Fixed


   In libtypec-dev
/usr/share/pkgconfig/${DEB_HOST_MULTIARCH}/libtypec.pc/libtypec.pc
gets shipped, which is not desired.


Fixed


* libtypec.h seems to be the same on all architectures. Does it have
to be shipped in a multiarch include location?


Fixed. Now in /usr/include and in the multiarch include location


* Binary packages in debian/control are not marked as Multi-Arch: same
* Please target experimental. The package needs to pass NEW and to
migrate to testing it will need a new source-only upload anyway.



Fixed.

Please review the 0.4 release upload and let me know if this can be 
sponsored further to the changes I made.


Kind regards,

Colin



Cheers,
Balint

[1] https://mentors.debian.net/package/libtypec/
[2] 
https://wiki.debian.org/Salsa/Doc#Collaborative_Maintenance:_.22Debian.22_group

On Thu, 3 Aug 2023 17:00:58 +0100 "Colin King (gmail)"
 wrote:

Hi,

I've uploaded a fixed package that addresses these issues.

Colin

On 18/07/2023 08:50, Adam Borowski wrote:

On Mon, Jul 17, 2023 at 03:29:13PM +0100, Colin King (gmail) wrote:

   * Package name : libtypec
 Version  : 0.3-1
   * URL  : https://github.com/Rajaram-Regupathy/libtypec



libtypec1 - generic interface for efficient USB-C port management
libtypec-dev - Development files for an interface for USB-C port management



   libtypec (0.3-1) unstable; urgency=low
   .
 * Initial release (Closes: #1023477)
 * Add patch 0001-fix-libtypec-so-version.patch to fix .so name version


Hi!
Before doing manual review, let's start with lintian:

E: libtypec1: pkg-config-multi-arch-wrong-dir full text contains architecture 
specific dir x86_64-linux-gnu [usr/share/pkgconfig/libtypec.pc]
W: libtypec-dev: empty-binary-package
W: libtypec1: lacks-unversioned-link-to-shared-library example: 
usr/lib/x86_64-linux-gnu/libtypec.so 
[usr/lib/x86_64-linux-gnu/libtypec.so.0.3.0]
W: libtypec1: link-to-shared-library-in-wrong-package 
usr/lib/x86_64-linux-gnu/libtypec.so.0.3.0 
[usr/lib/x86_64-linux-gnu/libtypec.so]


Meow!










Bug#1051290: Acknowledgement (fonts-sil-gentiumplus: gentium plus v6.200 has been released)

2023-09-20 Thread Nick Black (Public gmail account)
i've uploaded 6.200, and it has entered unstable. this bug can be closed.



Bug#1051290: fonts-sil-gentiumplus: gentium plus v6.200 has been released

2023-09-05 Thread Nick Black (Public gmail account)
Package: fonts-sil-gentiumplus
Version: 6.101-1
Severity: normal
X-Debbugs-Cc: dankamong...@gmail.com

Dear Maintainer,

Gentium Plus v6.200 was released 2023-02-01.

I'd really like to be able to use U+2227/U+2228 from this great font, among
other recent changes.

Please package the new version when you find time. Thank you!


-- Package-specific info:
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version   Architecture Description
+++-==-=--=
ii  fontconfig 2.14.2-5  amd64generic font configuration 
library - support binaries
ii  libfreetype6:amd64 2.13.2+dfsg-1 amd64FreeType 2 font engine, 
shared library files
ii  libxft2:amd64  2.3.6-1   amd64FreeType-based font drawing 
library for X

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

Kernel: Linux 6.4.9nlb2 (SMP w/64 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information



Bug#955954: thermald: Depends on deprecated dbus-glib

2023-08-31 Thread Colin King (gmail)

This issue has been reported to the upstream project:

https://github.com/intel/thermal_daemon/issues/416

..looking like it will be resolved in the next release of thermald



Bug#1041327: RFS: libtypec/0.3-1 [RFP] -- Development files for an interface for USB-C port management

2023-08-03 Thread Colin King (gmail)

Hi,

I've uploaded a fixed package that addresses these issues.

Colin

On 18/07/2023 08:50, Adam Borowski wrote:

On Mon, Jul 17, 2023 at 03:29:13PM +0100, Colin King (gmail) wrote:

  * Package name : libtypec
Version  : 0.3-1
  * URL  : https://github.com/Rajaram-Regupathy/libtypec



   libtypec1 - generic interface for efficient USB-C port management
   libtypec-dev - Development files for an interface for USB-C port management



  libtypec (0.3-1) unstable; urgency=low
  .
* Initial release (Closes: #1023477)
* Add patch 0001-fix-libtypec-so-version.patch to fix .so name version


Hi!
Before doing manual review, let's start with lintian:

E: libtypec1: pkg-config-multi-arch-wrong-dir full text contains architecture 
specific dir x86_64-linux-gnu [usr/share/pkgconfig/libtypec.pc]
W: libtypec-dev: empty-binary-package
W: libtypec1: lacks-unversioned-link-to-shared-library example: 
usr/lib/x86_64-linux-gnu/libtypec.so 
[usr/lib/x86_64-linux-gnu/libtypec.so.0.3.0]
W: libtypec1: link-to-shared-library-in-wrong-package 
usr/lib/x86_64-linux-gnu/libtypec.so.0.3.0 
[usr/lib/x86_64-linux-gnu/libtypec.so]


Meow!




Bug#1041327: RFS: libtypec/0.3-1 [RFP] -- Development files for an interface for USB-C port management

2023-07-18 Thread Colin King (gmail)

On 18/07/2023 08:50, Adam Borowski wrote:

On Mon, Jul 17, 2023 at 03:29:13PM +0100, Colin King (gmail) wrote:

  * Package name : libtypec
Version  : 0.3-1
  * URL  : https://github.com/Rajaram-Regupathy/libtypec



   libtypec1 - generic interface for efficient USB-C port management
   libtypec-dev - Development files for an interface for USB-C port management



  libtypec (0.3-1) unstable; urgency=low
  .
* Initial release (Closes: #1023477)
* Add patch 0001-fix-libtypec-so-version.patch to fix .so name version


Hi!
Before doing manual review, let's start with lintian:


Thanks, which lintian options did you use so I can santicy check my fixes?

Colin



E: libtypec1: pkg-config-multi-arch-wrong-dir full text contains architecture 
specific dir x86_64-linux-gnu [usr/share/pkgconfig/libtypec.pc]
W: libtypec-dev: empty-binary-package
W: libtypec1: lacks-unversioned-link-to-shared-library example: 
usr/lib/x86_64-linux-gnu/libtypec.so 
[usr/lib/x86_64-linux-gnu/libtypec.so.0.3.0]
W: libtypec1: link-to-shared-library-in-wrong-package 
usr/lib/x86_64-linux-gnu/libtypec.so.0.3.0 
[usr/lib/x86_64-linux-gnu/libtypec.so]


Meow!




Bug#1041327: RFS: libtypec/0.3-1 [RFP] -- Development files for an interface for USB-C port management

2023-07-17 Thread Colin King (gmail)

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

 * Package name : libtypec
   Version  : 0.3-1
   Upstream contact : Rajaram Regupathy 
 * URL  : https://github.com/Rajaram-Regupathy/libtypec
 * License  : MIT
 * Vcs  : [fill in URL of packaging vcs]
   Section  : utils

The source builds the following binary packages:

  libtypec1 - generic interface for efficient USB-C port management
  libtypec-dev - Development files for an interface for USB-C port 
management


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


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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/libt/libtypec/libtypec_0.3-1.dsc


Changes for the initial release:

 libtypec (0.3-1) unstable; urgency=low
 .
   * Initial release (Closes: #1023477)
   * Add patch 0001-fix-libtypec-so-version.patch to fix .so name version

Regards,

Colin Ian King



Bug#1023477: ITP: libtypec: progress request

2023-07-11 Thread Colin King (gmail)

Hi,

The ITP for this library was placed back in 5th Nov 2022; I was 
wondering if there is any progress on this?  If not, is it possible for 
me to take ownership and package this as I'm keen to ensure this is in 
Debian sooner than later.


Regards,

Colin



Bug#1038726: ITP: qatlib -- Intel(R) QuickAssist Technology hardware accelleration for security authentication and compression

2023-06-20 Thread Colin King (gmail)

Package: wnpp
Severity: wishlist
Owner: Colin Ian King 
X-Debbugs-Cc: debian-de...@lists.debian.org, colin.i.k...@gmail.com

* Package name: qatlib
  Version : 23.02.0
  Upstream Contact: giovanni.cabi...@intel.com
* URL : https://github.com/intel/qatlib
* License : BSD-3-Clause
  Programming Lang: C, x86 assemvler
  Description : Intel(R) QuickAssist Technology hardware 
accelleration for security authentication and compression


Intel(R) QuickAssist Technology (Intel(R) QAT) provides hardware
acceleration for offloading security, authentication and compression
services from the CPU, thus significantly increasing the performance
and efficiency of standard platform solutions.

Its services include symmetric encryption and authentication, asymmetric
encryption, digital signatures, RSA, DH and ECC, and lossless data
compression.

It provides user space libraries that allow access to Intel(R) 
QuickAssist devices and expose the Intel(R) QuickAssist APIs and sample 
codes.


See also: https://wiki.debian.org/QAT

I intend to maintain this much like other Intel related Debian packages

Sincerely,

Colin Ian King



Bug#1036960: plocate: coredump on any search

2023-05-30 Thread Nick Black (Public gmail account)
Package: plocate
Version: 1.1.18-1
Severity: normal
Tags: upstream
X-Debbugs-Cc: dankamong...@gmail.com

Dear Maintainer,

   * What led up to the situation?

I've been using plocate for many months on all my machines without problems.
Recently, I get a coredump on any search, on all the machines on which I've
tested. I've got a stack trace that points at do_search_file():

Thread 1 (Thread 0x7f426c687740 (LWP 914015) "locate"):
#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
#1  0x7f426c2a9d2f in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78
#2  0x7f426c25aef2 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#3  0x7f426c245472 in __GI_abort () at ./stdlib/abort.c:79
#4  0x7f426c29e2d0 in __libc_message (action=action@entry=do_abort,
fmt=fmt@entry=0x7f426c3b8459 "%s\n") at ../sysdeps/posix/libc_fatal.c:155
#5  0x7f426c2b364a in malloc_printerr (str=str@entry=0x7f426c3b60b1
"free(): invalid pointer") at ./malloc/malloc.c:5660
#6  0x7f426c2b53d4 in _int_free (av=, p=,
have_lock=have_lock@entry=0) at ./malloc/malloc.c:4435
#7  0x7f426c2b7d2f in __GI___libc_free (mem=) at
./malloc/malloc.c:3385
#8  0x5617abf86e1a in do_search_file (needles=std::vector of length 1,
capacity 1 = {...}, filename="plocate.db") at ../plocate.cpp:491
#9  0x5617abf804b8 in main (argc=, argv=) at
../plocate.cpp:995

this also happens with an empty database.


-- System Information:
Debian Release: 12.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (300, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.3.4nlb2 (SMP w/64 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages plocate depends on:
ii  adduser 3.134
ii  libc6   2.36-9
ii  libgcc-s1   12.2.0-14
ii  libstdc++6  12.2.0-14
ii  liburing2   2.3-3
ii  libzstd11.5.4+dfsg2-5

plocate recommends no packages.

Versions of packages plocate suggests:
ii  nocache 1.1-1+b1
ii  powermgmt-base  1.37
ii  systemd-sysv252.6-1

-- Configuration Files:
/etc/updatedb.conf changed:
PRUNE_BIND_MOUNTS="yes"
PRUNEPATHS="/tmp /var/spool /media/usb /media/dank /media/mtp /media/killermike 
/var/lib/os-prober /var/lib/ceph /home/.ecryptfs /var/lib/schroot"
PRUNEFS="NFS afs autofs binfmt_misc ceph cgroup cgroup2 cifs coda configfs 
curlftpfs debugfs devfs devpts devtmpfs ecryptfs ftpfs fuse.ceph fuse.cryfs 
fuse.encfs fuse.glusterfs fuse.gocryptfs fuse.gvfsd-fuse fuse.mfs fuse.rclone 
fuse.rozofs fuse.sshfs fusectl fusesmb hugetlbfs iso9660 lustre lustre_lite mfs 
mqueue ncpfs nfs nfs4 ocfs ocfs2 proc pstore rpc_pipefs securityfs shfs smbfs 
sysfs tmpfs tracefs udev udf usbfs"


-- no debconf information



Bug#1036356: stress-ng: autopkgtest failures on 32 bit architectures

2023-05-20 Thread Colin King (gmail)
Thanks for the update, I'm planning to make a stress-ng release that 
contains this fix before the end of next week to address this and 
several other issues.


Colin


On 19/05/2023 16:21, Benjamin Drung wrote:

Package: stress-ng
Version: 0.15.07-1
Severity: serious
Tags: patch
Justification: autopkgtest failures
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu mantic ubuntu-patch
X-Debbugs-Cc: bdr...@debian.org

Dear Maintainer,

The autopkg tests on 32 bit architectures fail. In Ubuntu, the attached
patch was applied to fix the autopkgtest:

   * Cherry-pick upstream commit "stress-pthread: use 64 bit tid_addr to fix
 stack clobbering on 32 bit platforms" and "stress-pthread: fix big endian
 tid addr for 32 bit systems" to fix test failures on 32 bit architectures
 (LP: #2019079)


Thanks for considering the patch.





Bug#1032620: doctest: new 2.4.10 out, fixes pernicious bugs

2023-03-10 Thread Nick Black (Public gmail account)
Source: doctest
Version: 2.4.9~ds-1
Severity: normal
X-Debbugs-Cc: dankamong...@gmail.com

Dear Maintainer,

Hello! My package notcurses depends on doctest. doctest 2.4.9 was released with
some issues that led to FTBFS without patchery. Thankfully, 2.4.10 has these
fixed. Hopefully it's possible to get an upgrade in before hard freeze. Thanks!


-- System Information:
Debian Release: 12.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (300, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.2.2nlb2 (SMP w/64 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)



Bug#1027976: ITP: libcpucycles -- Microlibrary for counting CPU cycles

2023-01-05 Thread Nick Black (Public gmail account)
Package: wnpp
Severity: wishlist
Owner: nick black  
X-Debbugs-Cc: debian-de...@lists.debian.org, dankamong...@gmail.com

* Package name: libcpucycles
  Version : 20230105
  Upstream Contact: Daniel J. Bernstein 
* URL : https://cpucycles.cr.yp.to/download.html
* License : Public domain
  Programming Lang: C
  Description : Microlibrary for counting CPU cycles

libcpucycles understands machine-level cycle counters for amd64 (both PMC and
TSC), arm32, arm64 (both PMC and VCT), mips64, ppc32, ppc64, riscv32, riscv64,
sparc64, and x86. libcpucycles also understands four OS-level mechanisms, which
give varying levels of accuracy: mach_absolute_time, perf_event,
CLOCK_MONOTONIC, and, as a fallback, microsecond-resolution gettimeofday.

When the program first calls cpucycles(), libcpucycles automatically benchmarks
the available mechanisms and selects the mechanism that does the best job.
Subsequent cpucycles() calls are thread-safe and very fast. An accompanying
cpucycles-info program prints a summary of cycle-counter accuracy.



Bug#1027035: libcpuset1: cpuset.3 references nonexistent bootcpuset.8, bootcpuset.conf.5

2022-12-26 Thread Nick Black (Public gmail account)
Package: libcpuset1
Version: 1.0-6+b1
Severity: minor
Tags: upstream
X-Debbugs-Cc: dankamong...@gmail.com

Dear Maintainer,

The cpuset.3 man page references bootcpuset.8 and bootcpuset.conf.5. Neither of
these man pages appear to exist in any package.


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

Kernel: Linux 6.1.0nlb2 (SMP w/64 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libcpuset1 depends on:
ii  libbitmask1  2.0-5
ii  libc62.36-7

libcpuset1 recommends no packages.

libcpuset1 suggests no packages.

-- no debconf information



Bug#1024089: ITP: accel-config -- Utility for configuring the DSA subsystem for Linux

2022-11-15 Thread Colin King (gmail)

Hi Nick,

I hadn't realized you were going to help the Intel folks on this, so 
apologies for usurping you. I've been maintaining quite a few Intel 
packages in Debian and I picked this up since I'm a new Intel employee 
and thought it would be useful to help on the final iterations of the

packaging.

I'm 99% the way to getting this sponsored so I think I'm almost complete 
on this work item now.


Colin

On 14/11/2022 19:56, nick black wrote:

Colin Ian King left as an exercise for the reader:

Package: wnpp
Severity: wishlist
Owner: Colin Ian King 
X-Debbugs-Cc: debian-de...@lists.debian.org


Hey Colin! I'm hoping to work with the Intel folks on this, and
it seems you started the endeavor and guided it thus far. Can I
assist you in any way at the moment?





Bug#1021639: wayfire: symbol lookup error: wayfire: undefined symbol: wlr_backend_get_renderer

2022-10-11 Thread Nick Black (Public gmail account)
Version: 0.7.4-2
close 1021639


i'm stupid. /usr/local strikes again. sorry!


signature.asc
Description: PGP signature


Bug#1021639: wayfire: symbol lookup error: wayfire: undefined symbol: wlr_backend_get_renderer

2022-10-11 Thread Nick Black (Public gmail account)
Package: wayfire
Version: 0.7.4-2
Severity: important
X-Debbugs-Cc: dankamong...@gmail.com

Dear Maintainer,

I installed wayfire 0.7.4-2, and attempted to run wayfire. It refused to start,
due to an undefined symbol. Prior to this, it printed several diagnostics, so
I'm guessing this symbol is used by some plugin or dynlib.

[schwarzgerat](0) $ wayfire
II 11-10-22 21:58:23.668 - [src/main.cpp:288] Starting wayfire version
0.8.0-bbe63a72 (Dec  1 2021, branch 'master')
II 11-10-22 21:58:23.669 - [backend/x11/backend.c:397] Creating X11 backend
II 11-10-22 21:58:23.669 - [backend/x11/backend.c:480] X11 does not support
shared pixmaps
EE 11-10-22 21:58:23.669 - [backend/x11/backend.c:609] Failed to query DRI3 DRM
FD
wayfire: symbol lookup error: wayfire: undefined symbol:
wlr_backend_get_renderer

Also, is the version number correct? The diagnostic indicates 0.8.0, but the
package is 0.7.4.


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

Kernel: Linux 5.19.14nlb2 (SMP w/64 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages wayfire depends on:
ii  libc62.35-3
ii  libcairo21.16.0-6
ii  libgcc-s112.2.0-5
ii  libgles2 1.5.0-1
ii  libglib2.0-0 2.74.0-2
ii  libinput10   1.21.0-1
ii  libjpeg62-turbo  1:2.1.2-1+b1
ii  libpango-1.0-0   1.50.10+ds-1
ii  libpangocairo-1.0-0  1.50.10+ds-1
ii  libpixman-1-00.40.0-1
ii  libpng16-16  1.6.38-2
ii  libstdc++6   12.2.0-5
ii  libwayland-server0   1.21.0-1
ii  libwf-config10.7.1-2
ii  libwf-utils0 0.7.4-2
ii  libwlroots10 0.15.1-3
ii  libxcb1  1.15-1
ii  libxkbcommon01.4.1-1

wayfire recommends no packages.

wayfire suggests no packages.

-- no debconf information



Bug#1021049: fritzing: new version 0.9.10 is available

2022-10-01 Thread Nick Black (Public gmail account)
Package: fritzing
Version: 0.9.6+dfsg-2+b1
Severity: normal
X-Debbugs-Cc: dankamong...@gmail.com

Dear Maintainer,

Version 0.9.10 of fritzing was released 2022-05-22. It includes a beta
simulator, a powerful new addition to fritzing. It would be great to have it in
Debian. If you need assistance updating, I'm happy to help out; if you were
unaware of the new version, just making you aware =].

Thanks for your efforts.


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

Kernel: Linux 5.19.11nlb2 (SMP w/64 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages fritzing depends on:
ii  fritzing-data0.9.6+dfsg-2
ii  fritzing-parts   0.9.6~unreleased-1
ii  libc62.35-1
ii  libgcc-s112.2.0-3
ii  libgit2-1.3  1.3.0+dfsg.1-3
ii  libqt5core5a 5.15.4+dfsg-5
ii  libqt5gui5   5.15.4+dfsg-5
ii  libqt5network5   5.15.4+dfsg-5
ii  libqt5printsupport5  5.15.4+dfsg-5
ii  libqt5serialport55.15.4-2
ii  libqt5sql5   5.15.4+dfsg-5
ii  libqt5sql5-sqlite5.15.4+dfsg-5
ii  libqt5svg5   5.15.4-2
ii  libqt5widgets5   5.15.4+dfsg-5
ii  libqt5xml5   5.15.4+dfsg-5
ii  libstdc++6   12.2.0-3
ii  zlib1g   1:1.2.11.dfsg-4.1

fritzing recommends no packages.

fritzing suggests no packages.

-- no debconf information



Bug#1020676: prometheus-mqtt-exporter: new version available (0.1.6)

2022-09-24 Thread Nick Black (Public gmail account)
Package: prometheus-mqtt-exporter
Version: 0.1.4-2+b9
Severity: normal
X-Debbugs-Cc: dankamong...@gmail.com

Dear Maintainer,

I was attempting to determine why promtheus-mqtt-exporter as packaged in Debian
wasn't honoring the MQTT2PROM_MQTT_USER and _PASSWORD variables defined in a
systemd override file. It appears that the version being shipped is 0.1.4.
Version 0.1.6 has been available from upstream for some time now (since
January), and adds support for these variables. It would be good to upgrade, I
think.

I'm also wondering whether this fixes a problem I was seeing where metrics were
being dropped. I'm going to grab 0.1.6, built it myself, and see what happens.


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

Kernel: Linux 5.19.10nlb2 (SMP w/64 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages prometheus-mqtt-exporter depends on:
ii  init-system-helpers  1.65.2
ii  libc62.35-1
ii  systemd-sysv 251.4-3

prometheus-mqtt-exporter recommends no packages.

prometheus-mqtt-exporter suggests no packages.

-- Configuration Files:
/etc/prometheus/mqtt-exporter.yaml changed:
mqtt:
  # The MQTT broker to connect to
  server: tcp://localhost:1883
  # user and password are specified in systemd dropin
  topic_path: mora3
  # Optional: Regular expression to extract the device ID from the topic path. 
The default regular expression, assumes
  # that the last "element" of the topic_path is the device id.
  # The regular expression must contain a named capture group with the name 
deviceid
  # For example the expression for tasamota based sensors is 
"tele/(?P.*)/.*"
  # device_id_regex: "(.*/)?(?P.*)"
  # The MQTT QoS level
  qos: 0
cache:
  # Timeout. Each received metric will be presented for this time if no update 
is send via MQTT.
  # Set the timeout to -1 to disable the deletion of metrics from the cache. 
The exporter presents the ingest timestamp
  # to prometheus.
  timeout: 60m
metrics:
  -
prom_name: mora3coolant
mqtt_name: therm
help: Coolant temperature as measured at MO-RA3
type: gauge
const_labels:
  sensor_type: k10
  -
prom_name: mora3rpm
mqtt_name: rpm
help: RPM measurements from MO-RA3 fans
type: gauge
const_labels:
  sensor_type: arcticp14


-- no debconf information



Bug#1016883: prometheus service ought depend on time-sync

2022-08-08 Thread Nick Black (Public gmail account)
Package: prometheus
Version: 2.24.1+ds-1
Severity: normal
X-Debbugs-Cc: dankamong...@gmail.com

Dear Maintainer,

I run prometheus on a Libre Computer Potato SBC, lacking an RTC,
collecting from prometheus-node-exporter on my workstation. In the
default configuration, prometheus fills logs with errors along the lines
of:

Aug 08 17:00:40 amoled prometheus[2337]: level=warn ts=2022-08-08T21:00:40.522Z 
caller=scrape.go:1372 component="scrape manager" scrape_pool=prometheus 
target=http://localhost:9090/metrics msg="Error on ingesting out-of-order 
samples" num_dropped=404

and doesn't append to my records. Upon restarting promtheus with

  systemctl restart prometheus

the problem goes away, and I can begin collecting stats anew.

I believe this is due to the prometheus service not depending on
time-sync.target. I've added

  [Unit]
  Before=time-sync.target
  Wants=time-sync.target

to a drop-in, and with this change, I do not hit the problem.

Given prometheus's fundamental dependency on time-ordered databases, I
feel this dependency ought be present in the default prometheus systemd
unit.

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

Kernel: Linux 5.18.15nlb2 (SMP w/64 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages prometheus depends on:
ii  adduser  3.123
ii  fonts-glyphicons-halflings   1.009~3.4.1+dfsg-2
ii  init-system-helpers  1.64
ii  libc62.34-1
ii  libjs-bootstrap4 4.6.1+dfsg1-3
pn  libjs-eonasdan-bootstrap-datetimepicker  
ii  libjs-jquery 3.6.0+dfsg+~3.5.13-1
ii  libjs-jquery-hotkeys 0~20130707+git2d51e3a9+dfsg-2.1
pn  libjs-moment 
pn  libjs-moment-timezone
pn  libjs-mustache   
ii  libjs-popper.js  1.16.1+ds-5
pn  libjs-rickshaw   

Versions of packages prometheus recommends:
ii  prometheus-node-exporter  1.3.1-1+b1

prometheus suggests no packages.



Bug#1009050: libcpuset1: man page references wrong path for documentation

2022-04-06 Thread Nick Black (Public gmail account)
Package: libcpuset1
Version: 1.0-6
Severity: normal
X-Debbugs-Cc: dankamong...@gmail.com

Dear Maintainer,

CPUSET.3 claims

"For  additional  documentation  on  cpusets,  and  for  details  of  the  all  
the   other,   advanced,   routines,   see
 /usr/share/doc/packages/libcpuset/libcpuset.html and
 /usr/share/doc/packages/libbitmask/libbitmask.html.   These  same  documents  
are  available  in  plain  text  format  as
 /usr/share/doc/packages/libcpuset/libcpuset.txt and
 /usr/share/doc/packages/libbitmask/libbitmask.txt."

The actual paths are /usr/share/doc/libcpuset-dev/*


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

Kernel: Linux 5.17.1nlb2 (SMP w/64 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libcpuset1 depends on:
ii  libbitmask1  2.0-4
ii  libc62.33-7

libcpuset1 recommends no packages.

libcpuset1 suggests no packages.

-- no debconf information



Bug#1005791: diagnosticator package

2022-02-14 Thread Diagnosticator Gmail
Please find attached

Enrico Cocchi


diagnosticator_0.1.0-1_all.deb
Description: application/vnd.debian.binary-package


Bug#1004473: mutrace -d fails to load missing _sch_istable symbol

2022-01-28 Thread Nick Black (Public gmail account)
Package: mutrace
Version: 0.2.0-3.4+b2
Severity: normal
X-Debbugs-Cc: dankamong...@gmail.com

Dear Maintainer,

Trying to use mutrace with the -d option fails:

[schwarzgerat](1) $ mutrace -d ls
ls: symbol lookup error: /usr/lib/mutrace/libmutrace-backtrace-symbols.so: 
undefined symbol: _sch_istable
[schwarzgerat](127) $

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

Kernel: Linux 5.16.1nlb2 (SMP w/64 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mutrace depends on:
ii  libc6  2.33-5

mutrace recommends no packages.

mutrace suggests no packages.

-- no debconf information



Bug#1004100: stterm: new upstream release 0.8.5 fixes OSC4 failure

2022-01-20 Thread Nick Black (Public gmail account)
Package: stterm
Version: 0.8.4-1
Severity: normal
X-Debbugs-Cc: dankamong...@gmail.com

Dear Maintainer,

I'm the developer of Notcurses, a TUI library. I ran into a bug with st
on Debian Unstable, where the OSC4 palette query resulted in a
diagnostic and emitted garbage characters:

  https://github.com/dankamongmen/notcurses/issues/2561

It turned out the upstream doesn't have this problem, and that it has
been fixed in the 0.8.5 release from two weeks ago. Please consider
updating the package. Thanks!

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

Kernel: Linux 5.16.0nlb (SMP w/64 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages stterm depends on:
ii  libc6   2.33-3
ii  libfontconfig1  2.13.1-4.2
ii  libx11-62:1.7.2-2+b1
ii  libxft2 2.3.2-2
ii  ncurses-term6.3-2

stterm recommends no packages.

stterm suggests no packages.

-- no debconf information



Bug#1001815: transition: notcurses

2022-01-01 Thread Nick Black (Public gmail account)
> No, only in unstable [1]. Testing should still work.

hrmm, i'm a bit confused about how this works then. i can only
upload into unstable, and it then needs to pass autopkgtests to
get into testing. oh, i guess those autopkgtests are being run
in the "testing" context? if so, that makes sense.

anyway, uploading 1.2.38-3 to unstable now in the hope of
getting some useful debugging information.


signature.asc
Description: PGP signature


Bug#1001815: transition: notcurses

2021-12-31 Thread Nick Black (Public gmail account)
I see that growlight's autopkgtests are disabled in testing
right now due to the timeout. Can we please remove that, so I
can try something? 

I noticed just now in the growlight testing logs that we have
output of the form e.g.:

xvda14 -> ../../devices/vbd-51712/block/xvda/xvda14
Partition 14 at xvda14
Partition 1 at xvda1
Partition 15 at xvda15
Logical sector size: 512B Physical sector size: 512B

but this isn't "blockdev -v" output; it's just general startup
diagnostics due to calling "growlight-readline -v". we then see
a prompt in the logs:

[growlight](0)> 

that never seems to get any input. i.e. the "echo blockdev -v"
is never hitting it, and that's why it's not shutting down.

success should look like:

^[[64;1H^A^[[0;35m^B[^A^[[0;36m^Bgrowlight^A^[[0;35m^B]^A^[[1;32m^B(0)> 
^A^[[1;37m^B^[[64;1H^[[Kb^[[64;2H^[[64;1H^[[Kbl^[[64;3H^[[64;1H^[[Kblo^[[64;4H^[[64;1H^[[Kbloc^[[64;5H^[[64;1H^[[Kblock^[[64;6H^[[64;1H^[[Kblockd^[[64;7H^[[64;1H^[[Kblockde^[[64;8H^[[64;1H^[[Kblockdev^[[64;9H^[[64;1H^[[Kblockdev
 ^[[64;10H^[[64;1H^[[Kblockdev -^[[64;11H^[[64;1H^[[Kblockdev 
-v^[[64;12H^[[64;1H^[[Kblockdev -v ^[[64;13H
^[[1m^[[38;2;255;255;255mDevice Model Rev   Bytes PSect Flags 
Table WWN  PHY
^[[22m^[[38;2;249;241;165msdjST16000NM000J-2T SN02  16.00T 4096B 
M-bM-^\M-^TOWM-bM-^ZM- . none  5000c500c94d9fd7 SAT3
^[[1m^[[38;2;19;161;14m^[[22mUnused sectors 0:31251759104 (14.55Ti)
^[[38;2;249;241;165msdlST12000NM0007-2A SN02  12.00T 4096B 
M-bM-^\M-^TOWM-bM-^ZM- . gpt   5000c500b49867e5 SAT3
^[[1m^[[38;2;19;161;14m^[[22mUnused sectors 0:2047 (1Mi)
^[[1m^[[38;2;59;120;255msdl1   53316a63-ce0b-644f-b0de-586da7e95a07  12.00T 
Oth zfs-7f5ed1aa1ce6dbc4
^[[38;2;19;161;14m^[[38;2;59;120;255msdl9   
703b1cea-95bf-a840-8bb8-4336b78ba231   8.39M Oth n/a
^[[38;2;19;161;14m^[[22mUnused sectors 23437768704:23437770752 (1.00Mi)
^[[38;2;249;241;165msdhST12000NM0007-2A SN03  12.00T 4096B M-bM-^XM- 
OWM-bM-^ZM- . gpt   5000c500a5c0e61d SAT3
^[[1m^[[38;2;19;161;14m^[[22mUnused sectors 0:2047 (1Mi)
^[[1m^[[38;2;59;120;255msdh1   091bbc74-d66a-3849-af41-42ec40116171  12.00T 
Oth zfs-d60b954b8cc5eae0
^[[38;2;19;161;14m^[[38;2;59;120;255msdh9   
4bcb8333-fb23-d244-8d70-34e9378155d9   8.39M Oth n/a
^[[38;2;19;161;14m^[[22mUnused sectors 23437768704:23437770752 (1.00Mi)
^[[38;2;249;241;165msdkST18000NM000J-2T SN02  18.00T 4096B 
M-bM-^\M-^TOWM-bM-^ZM- . none  5000c500dbd49a2a SAT3
^[[1m^[[38;2;19;161;14m^[[22mUnused sectors 0:35156656128 (16.37Ti)
^[[38;2;249;241;165msdiST16000NM000J-2T SN02  16.00T 4096B 
M-bM-^\M-^TOWM-bM-^ZM- . none  5000c500db183d56 SAT3
^[[1m^[[38;2;19;161;14m^[[22mUnused sectors 0:31251759104 (14.55Ti)
^[[38;2;249;241;165msdbST12000NM0007-2A SN02  12.00T 4096B 
M-bM-^\M-^TOWM-bM-^ZM- . gpt   5000c500b4104bf5 SAT3
^[[1m^[[38;2;19;161;14m^[[22mUnused sectors 0:2047 (1Mi)

or, with the control sequences stripped:

blockdev -v
Device Model Rev   Bytes PSect Flags Table WWN  PHY
sdjST16000NM000J-2T SN02  16.00T 4096B ✔OW⚠. none  5000c500c94d9fd7 SAT3
Unused sectors 0:31251759104 (14.55Ti)
sdlST12000NM0007-2A SN02  12.00T 4096B ✔OW⚠. gpt   5000c500b49867e5 SAT3
Unused sectors 0:2047 (1Mi)
sdl1   53316a63-ce0b-644f-b0de-586da7e95a07  12.00T Oth zfs-7f5ed1aa1ce6dbc4
sdl9   703b1cea-95bf-a840-8bb8-4336b78ba231   8.39M Oth n/a
Unused sectors 23437768704:23437770752 (1.00Mi)
sdhST12000NM0007-2A SN03  12.00T 4096B ☠OW⚠. gpt   5000c500a5c0e61d SAT3
Unused sectors 0:2047 (1Mi)
sdh1   091bbc74-d66a-3849-af41-42ec40116171  12.00T Oth zfs-d60b954b8cc5eae0
sdh9   4bcb8333-fb23-d244-8d70-34e9378155d9   8.39M Oth n/a
Unused sectors 23437768704:23437770752 (1.00Mi)
sdkST18000NM000J-2T SN02  18.00T 4096B ✔OW⚠. none  5000c500dbd49a2a SAT3
Unused sectors 0:35156656128 (16.37Ti)
sdiST16000NM000J-2T SN02  16.00T 4096B ✔OW⚠. none  5000c500db183d56 SAT3
Unused sectors 0:31251759104 (14.55Ti)
sdbST12000NM0007-2A SN02  12.00T 4096B ✔OW⚠. gpt   5000c500b4104bf5 SAT3
Unused sectors 0:2047 (1Mi)

so i've changed up the autopkgtests to try something.


signature.asc
Description: PGP signature


Bug#1002724: ITP: openfec -- Forward Error Correction codes

2021-12-28 Thread Nick Black (Public gmail account)
Package: wnpp
Severity: wishlist
Owner: "Nick Black (Public gmail account)" 
X-Debbugs-Cc: debian-de...@lists.debian.org, dankamong...@gmail.com

  Package name: openfec
  Version : 1.4.2.4
  Upstream Author : Victor Gaydov  et al
  URL : http://www.example.org/
  License : CeCILL-C
  Programming Lang: C
  Description : Forward Error Correction codes

Application-Level Forward Error Correction codes add
redundancy in order to be able to recover from erasures.

this library is required by the Roc Project, whose PipeWire
modules are currently disabled. With the addition of this
dependency, we will be able to build roc-toolkit, and thus
enable the PipeWire Roc sink and source. indeed, this active
fork of the original OpenFEC is maintained by Roc.

It uses a CeCILL-C license; see [0] for discussion on debian-legal.
In addition, small parts come under Radford Neal's LDPC simulator
license and Luigi Rizzo's Reed-Solomon license ([1]); I have
reviewed both, and they seem trivially compatible with the DFSG.

As a lowly DM, I'll be uploading this through a Sponsor, Dylan Aïssi
from the Utopia team.

[0] https://lists.debian.org/debian-legal/2017/03/msg00019.html
[1] http://openfec.org/patents.html


Bug#1002630: pipewire: enable roc module

2021-12-25 Thread Nick Black (Public gmail account)
Package: pipewire
Version: 0.3.42-1
Severity: wishlist
X-Debbugs-Cc: dankamong...@gmail.com

Dear Maintainer,

I see in the changelog "disble roc module, at least for now", but I was
hoping to use this module for synchronized audio.

Ahh, I see libroc isn't yet packaged in Debian. Were I to package it,
would you have any interest in Sponsoring the upload (I'm only a DM
at the moment, not yet a DD)? I built it from source, and was able
to build pipewire 0.3 with ROC support.

Kernel: Linux 5.15.9nlb (SMP w/64 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pipewire depends on:
ii  init-system-helpers  1.61
ii  libpipewire-0.3-modules  0.3.42-1
ii  pipewire-bin 0.3.42-1

pipewire recommends no packages.

pipewire suggests no packages.

-- no debconf information



Bug#1001815: transition: notcurses

2021-12-16 Thread Nick Black (Public gmail account)
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: dankamong...@gmail.com

Hello transition team!

Notcurses has bumped the SOVERSION from 2 to 3 as of its 3.0.0 release,
reflecting a changed ABI and API both.

The only reverse-dep of notcurses is growlight. I am the upstream author
of both. The 1.2.38 release of Growlight is necessary and sufficient
to compile against Notcurses 3. I have already packaged it, and am
simply waiting on the entry of libnotcurses3 into unstable.

Ben file:

title = "notcurses";
is_affected = .depends ~ "libnotcurses2" | .depends ~ "libnotcurses++2" | 
.depends ~ "libnotcurses-core2" | .depends ~ "libnotcurses3" | .depends ~ 
"libnotcurses++3" | .depends ~ "libnotcurses-core3";
is_good = .depends ~ "libnotcurses3" | .depends ~ "libnotcurses++3" | .depends 
~ "libnotcurses-core3";
is_bad = .depends ~ "libnotcurses2" | .depends ~ "libnotcurses++2" | .depends ~ 
"libnotcurses-core2";



Bug#1001666: stress-ng: flaky autopkgtest

2021-12-13 Thread Colin King (gmail)

Hi Sebastian,

thanks for reporting this. Is is OK to ask a few questions as I've never 
seen this before on a wide range of kit that I test this on.


1. Is this failure repeatable? (I'm not sure how it occurs since there 
is a SIGSEGV handler for these cases).

2. Does it fail on specific machines?
3. What CPU model is the machine it fails on?

I've tried to understand this failure, but so far I'm quite perplexed by 
it, so maybe it's a CPU specific caching behavior that I have misunderstood.


Any assistance with the questions above would be most useful,

Regards,

Colin


On 13/12/2021 21:48, Sebastian Ramacher wrote:

Source: stress-ng
Version: 0.13.08-1
Severity: important
X-Debbugs-Cc: sramac...@debian.org

The autopkgtests of stress-ng fail from time to time:
| stress-ng: 20:49:12.58 info:  [1091] unsuccessful run completed in 0.51s
| stress-ng: 20:49:12.58 fail:  [1091] cache instance 3 corrupted bogo-ops 
counter, 2 vs 0
| stress-ng: 20:49:12.58 fail:  [1091] cache instance 3 hash error in bogo-ops 
counter and run flag, 796547380 vs 0
| stress-ng: 20:49:12.58 fail:  [1091] metrics-check: stressor metrics 
corrupted, data is compromised
| cache FAILED
...
| zlib PASSED
| 42 PASSED
| 1 FAILED, cache
| 0 SKIPPED

See
https://ci.debian.net/data/autopkgtest/testing/amd64/s/stress-ng/17550292/log.gz
for a recent failure

Cheers





Bug#939540: libgpm-dev: Does not provide .pc file

2021-10-31 Thread Nick Black (Public gmail account)
> Wouldn't really be happy about an NMU. A patch is clearly preferred.
> But feel free to submit that patch as a Merge Request on Salsa
> including an appropriate debian/changelog entry in the same commit.
> (Please also post the link to the MR in this bug report. TIA!)
> I'll include it then in the next upload.

I totally understand, and agree that this is the way to go. So
long as sramacher is good with it, I'm more than happy to
proceed this way.



Bug#939540: libgpm-dev: Does not provide .pc file

2021-10-30 Thread Nick Black (Public gmail account)
Package: libgpm-dev
Version: 1.20.7-9
Followup-For: Bug #939540
X-Debbugs-Cc: dankamong...@gmail.com

Dear Maintainer,

I'm going to go ahead and prepare a suitable pkg-config file for libgpm,
and submit it to you. This is part of my DD application (AM: sramacher),
so performing an NMU is also desirable, if that's amenable to you.

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

Kernel: Linux 5.14.15nlb (SMP w/64 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libgpm-dev depends on:
ii  libc6-dev [libc-dev]  2.32-4
ii  libgpm2   1.20.7-9

libgpm-dev recommends no packages.

libgpm-dev suggests no packages.

-- no debconf information



Bug#996176: xrdp: gnome shell crash related to https://github.com/neutrinolabs/xorgxrdp/issues/156, solved upstream please update to 0.9.17

2021-10-11 Thread denis gmail

Package: xrdp
Version: 0.9.12-1.1
Severity: important
Tags: upstream

Dear Maintainer,

When using Gnome desktop, xrdp is broken, resulting in
gnome crash with "Oh no ! ..."  error.

Upgrading xrdp and xorgxrdp to version 0.9.17 from bookworm
solves the problem.

The problem is probably related to bug
https://github.com/neutrinolabs/xorgxrdp/issues/156. By the way,
as the problem is solved upstream, is it possible to update bullseye
package to 0.9.17 ? This bug prevents any remote use of Bullseye stations.

Altough a quick fix is included in bug above, consisting in reverting to 
0.9.7 version, the author himself says that
it is not the good solution. So backporting all changes related to 
0.9.12 is probably not an option.



-- 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/6 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE 
not set

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xrdp depends on:
ii  adduser  3.118
ii  init-system-helpers  1.60
ii  libc6    2.32-4
ii  libfuse2 2.9.9-5
ii  libjpeg62-turbo  1:2.0.6-4
ii  libopus0 1.3.1-0.1
ii  libpam0g 1.4.0-9+deb11u1
ii  libssl1.1    1.1.1k-1+deb11u1
ii  libx11-6 2:1.7.2-1
ii  libxfixes3   1:5.0.3-2
ii  libxrandr2   2:1.5.1-1
ii  lsb-base 11.1.0
ii  ssl-cert 1.1.0+nmu1

Versions of packages xrdp recommends:
ii  fuse3 [fuse]  3.10.3-2
ii  xorgxrdp  1:0.2.17-1

Versions of packages xrdp suggests:
pn  guacamole  

Versions of packages xorgxrdp depends on:
ii  libc6  2.32-4
ii  libepoxy0  1.5.5-1
pn  xorg-input-abi-24  
ii  xserver-xorg-core [xorg-video-abi-24]  2:1.20.11-1

Versions of packages xorgxrdp recommends:
ii  xorg  1:7.7+22

Versions of packages xrdp is related to:
pn  vnc-server   
ii  xserver-xorg-legacy  2:1.20.11-1

-- no debconf information



Bug#990798: Switch to fork?

2021-09-25 Thread Nick Black (Public gmail account)
Source: libsixel
Version: 1.8.6-2
Followup-For: Bug #990798
X-Debbugs-Cc: dankamong...@gmail.com

Dear Maintainer,

Hi. I'm the maintainer of the new fork of libsixel at libsixel/libsixel on
GitHub. I've been maintaining it for several months now.

I see you merged my PR on salsa:

  https://salsa.debian.org/debian/libsixel/-/merge_requests/2

We just need a new release now to switch to the new fork, with its
many security fixes (it would close several outstanding Important
bugs on this package). With that said, you might as well pull down
the newest version, 1.10.2, just released tonight. You can go
ahead and drop `libbsd-dev` from the Build-Dependencies when you
do so, as it is no longer used.

Please make a new release.

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

Kernel: Linux 5.13.18nlbschwarzgerat (SMP w/64 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not
set
Shell: /bin/sh linked to /bin/dash



Bug#990089: linux-image-4.19.0-17-amd64: lxc-attach fails with Failed to set AppArmor label unconfined

2021-06-21 Thread Gmail
Salvatore,

On Sun, 2021-06-20 at 20:39 +0200, Salvatore Bonaccorso wrote:
> Hi Mark,
> 
> On Sun, Jun 20, 2021 at 10:44:29AM +0100, Mark Grant wrote:
> > Package: src:linux
> > Version: 4.19.194-1
> > Severity: normal
> > 
> > Dear Maintainer,
> > 
> > After upgrading from linux-image-4.19.0-16-amd64 to linux-image-
> > 4.19.0-17-amd64
> > attaching an unprivileged linux container fails with the message:
> > lxc-attach: debian-buster-amd64-basic: lsm/lsm.c:
> > lsm_process_label_set_at: 174
> > Operation not permitted - Failed to set AppArmor label "unconfined"
> > Rebooting into linux-image-4.19.0-16-amd64 with no other changes,
> > the lxc
> > system works as expected.
> 
> I think this is the same issue as in #990072, would you be able to
> test the patch as commited
> https://salsa.debian.org/kernel-team/linux/-/commit/d3fc7c8514bed949d8797cfd3a50a1bed95629c0
> ?
> 
I can confirm that the patch fixed the problem. Many thanks.

Regards,
Mark

> Regards,
> Salvatore



Bug#989525: kbd: resizecons.8 references obsolete disalloc.8

2021-06-06 Thread Nick Black (Public gmail account)
Package: kbd
Version: 2.3.0-3
Severity: normal
Tags: patch upstream
X-Debbugs-Cc: dankamong...@gmail.com

Dear Maintainer,

The resizecons.8 man page refers to disalloc.8, which no longer exists. It
ought reference deallocvt.8. I've created a merge request at
https://salsa.debian.org/debian/kbd/-/merge_requests/3 with the correction.

-- System Information:
Debian Release: 11.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (300, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.12.9nlb (SMP w/64 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not
set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kbd depends on:
ii  libc6  2.31-12

Versions of packages kbd recommends:
ii  console-setup  1.203

kbd suggests no packages.



Bug#988195: wine-development: starting wine-development failed due to wrong prefix

2021-05-09 Thread gmail

Dear maintainer,

This message to tell that version 5.9.2 fix actually the issue on my system.

Thank you !

invar



Bug#988195: wine-development: starting wine-development failed due to wrong prefix

2021-05-08 Thread gmail

Dear maintainer,

I have the same issue, exactly in the same conditions that for the 
previous message.


Moreover I met the same issue with the version 5.8.1

And when I create the directory whose the app complains, there is no 
more the message "no such directory", but then the wine server freezes 
for a "mysterious reason" (dixit)



best regards

invar



Bug#977922: iproute2 should probably only Suggest libatm1

2020-12-22 Thread Nick Black (Public gmail account)
Package: iproute2
Version: 5.10.0-1
Severity: wishlist
Tags: patch
X-Debbugs-Cc: dankamong...@gmail.com

Dear Maintainer,

[ A patch has been provided for this bug at
  https://salsa.debian.org/debian/iproute2/-/merge_requests/4 ]

Recommends "should list packages that would be found together with this one in
all but unusual installations." That might have been true ten years ago, but
surely in 2020 iproute2 installations vastly outnumber the number making active
use of ATM hardware or the q_atm.so module.

I've provided a MR in Salsa, linked above. Please apply if you agree.



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

Kernel: Linux 5.10.1nlb (SMP w/64 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages iproute2 depends on:
ii  debconf [debconf-2.0]  1.5.74
ii  libbsd00.10.0-1
ii  libc6  2.31-6
ii  libcap21:2.44-1
ii  libcap2-bin1:2.44-1
ii  libdb5.3   5.3.28+dfsg1-0.6
ii  libelf10.182-1
ii  libmnl01.0.4-3
ii  libselinux13.1-2+b2
ii  libxtables12   1.8.6-1

Versions of packages iproute2 recommends:
pn  libatm1  

Versions of packages iproute2 suggests:
pn  iproute2-doc  

-- debconf information:
* iproute2/setcaps: false



Bug#977691: libc6: would be great to have 2.32's Unicode 13 support in bullseye

2020-12-18 Thread Nick Black (Public gmail account)
Package: libc6
Version: 2.31-6
Severity: normal
X-Debbugs-Cc: dankamong...@gmail.com

Dear Maintainer,

Unstable currently contains GNU libc 2.31. I assume that this is the version
expected to go into Bullseye. If 2.32 is intended, please ignore this bug.

2.32 added Unicode 13 support, including wcwidth() tables for the new Unicode
13 characters, introduced in March 2020. 2.31 wcwidth() returns -1 for these
characters. GNU libc's wcwidth() implementation is table-driven, and generated
from Unicode data files. It is thus pretty well self-contained.

If Bullseye will be shipping 2.31, it would be very desirable to include the
Unicode 13 support from 2.32. At the very least, the updated wcwidth() tables
would be a boon. I'd be happy to prepare a backport in the form of a patch, but
wanted to submit this bug and get feedback from the glibc maintainers before
doing so.

Would such a patch be welcome, assuming I could get it done by some date?
Alternatively, are there plans to ship 2.32 in Bullseye?

Thanks!



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

Kernel: Linux 5.10.1nlb (SMP w/64 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libc6 depends on:
ii  libcrypt1  1:4.4.17-1
ii  libgcc-s1  10.2.1-1

Versions of packages libc6 recommends:
ii  libidn2-0   2.3.0-4
ii  libnss-nis  3.1-4
ii  libnss-nisplus  1.3-4

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.74
ii  glibc-doc  2.31-6
ii  libc-l10n  2.31-6
ii  locales2.31-6

-- debconf information:
  glibc/restart-failed:
* glibc/disable-screensaver:
* libraries/restart-without-asking: true
  glibc/kernel-not-supported:
  glibc/kernel-too-old:
  glibc/restart-services:
  glibc/upgrade: true



Bug#974711: check-all-the-things: recommends transitional dummy package "afl"

2020-11-13 Thread Nick Black (Public gmail account)
Package: check-all-the-things
Version: 2017.05.20+nmu
Severity: minor
Tags: patch
X-Debbugs-Cc: dankamong...@gmail.com

Dear Maintainer,
https://wiki.debian.org/CopyrightReviewTools
I was taking a look at check-all-the-things, having seen it on
https://wiki.debian.org/CopyrightReviewTools, when I noticed that it Recommends
the transitional package afl. This ought probably be replaced with afl++.



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

Kernel: Linux 5.9.7nlb (SMP w/64 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages check-all-the-things depends on:
ii  python3  3.8.6-1

Versions of packages check-all-the-things recommends:
pn  afl 
pn  appstream   
pn  appstream-util  
ii  aspell  0.60.8-1
pn  astropy-utils   
ii  autoconf2.69-11.1
ii  autodep80.24
pn  bfbtester   
pn  blhc
pn  bls-standalone  
ii  bzip2   1.0.8-4
pn  cabal-install   
ii  chktex  1.7.6-3
ii  clang   1:9.0-49.1
ii  clang-tidy  1:9.0-49.1
pn  cme | libconfig-model-perl  
pn  codespell   
pn  complexity  
ii  cppcheck2.2-1
pn  cypher-lint 
pn  debmake 
pn  deheader
ii  desktop-file-utils  0.26-1
ii  devscripts  2.20.4
pn  dh-ocaml
pn  dodgy   
pn  duck
ii  epubcheck   4.2.2-1
pn  erlang-base 
pn  erlang-syntax-tools 
pn  fdupes  
pn  flawfinder  
pn  flightcrew  
ii  fontforge   1:20190801~dfsg-5
ii  freetype2-demos 2.10.2+dfsg-4
pn  gendarme
ii  gettext 0.19.8.1-10
pn  gettext-lint
ii  golang-go   2:1.15~1
pn  golang-golang-x-tools   
pn  golint  
pn  hardening-includes  
pn  hlint   
pn  hopenpgp-tools  
pn  i18nspector 
ii  iwyu8.0-4
ii  jpeginfo1.6.0-6+b4
ii  jsonlint1.8.2-1
pn  kwstyle 
ii  lacheck 1.26-17
pn  lcdf-typetools  
pn  libb-lint-perl  
pn  libconfig-model-dpkg-perl   
pn  libcroco-tools  
pn  libperl-critic-perl 
pn  libpod-pom-perl 
ii  libwww-perl 6.49-1
ii  libxml2-utils   2.9.10+dfsg-6.2
pn  license-reconcile   
ii  licensecheck3.0.47-1
pn  lintex  
ii  lintian 2.102.0
pn  lockdep 
pn  lua-check   
ii  lz4 [liblz4-tool]   1.9.2-2
ii  lzip1.21-8
ii  lzop1.04-1
ii  make4.3-4
ii  moreutils   0.64-1
pn  mp3check
pn  mp3val  
pn  mypy
ii  ocaml-nox   4.11.1-4
pn  oggz-tools  
pn  opencollada-tools   
ii  opus-tools  0.1.10-1+b1
ii  p7zip   16.02+dfsg-8
ii  perl5.32.0-4
ii  php-cli 2:7.4+76
ii  php7.4-cli [php-cli]7.4.11-1
ii  pkg-config  0.29.2-1
pn  pmccabe 
ii  pngcheck2.3.0-12
pn  pscan   
pn  puppet  
pn  puppet-lint 
pn  pycodestyle 
pn  pydocstyle  
pn  pyflakes3 | pyflakes
pn  pylint  
pn  pylint3 
ii  python3-argcomplete 1.8.1-1.3
pn  python3-bandit  
pn  python3-bashate 
ii  python3-debian  0.1.38
pn  python3-demjson 
pn  python3-fontforge   
pn  python3-jpylyzer
ii  python3-magic   2:0.4.15-4
ii  python3-netifaces   0.10.9-0.2+b2
pn  python3-proselint   
ii  python3-ptyprocess  0.6.0-3
pn  python3-pyroma  
pn  roodi   
pn  rpmlint 
pn  rubocop 
ii  sharutils   1:4.15.2-5
ii  shellcheck  0.7.1-1
ii  ssl-cert-check  4.14-1
pn  stylish-haskell 
ii  unzip  

Bug#973916: ITP: rust-libc-print -- Support for println and eprintln in a no_std context

2020-11-07 Thread Nick Black (Public gmail account)
Package: wnpp
Severity: wishlist
Owner: "Nick Black" 
X-Debbugs-Cc: debian-de...@lists.debian.org, dankamong...@gmail.com

* Package name: rust-libc-print
  Version : 0.1.14
  Upstream Author : Matt Mastracci 
* URL : https://github.com/mmastrac/rust-libc-print
* License : Apache-2.0 or MIT
  Programming Lang: Rust
  Description : Support for println and eprintln in a no_std context

An implementation of println! and eprintln! on the libc
crate without requiring the use of an allocator, and thus
suitable for a no_std context.

This small package is a dependency for rust-notcurses (see #972542).

This will be maintained by myself under the auspices of the Rust Packaging
Team.



Bug#972542: ITP: librust-libnotcurses-sys-dev -- Character graphics and TUI library (Rust development)

2020-10-19 Thread Nick Black (Public gmail account)
Package: wnpp
Severity: wishlist
Owner: "Nick Black (Public gmail account)" 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: librust-libnotcurses-sys-dev
  Version : 2.0.1
  Upstream Author : Nick Black 
* URL : https://nick-black.com/dankwiki/index.php/Notcurses
* License : Apache-2.0
  Programming Lang: Rust
  Description : Character graphics and TUI library (Rust development)

 Notcurses facilitates the creation of modern TUI programs,
 making full use of Unicode and 24-bit TrueColor. It presents
 an API similar to that of Curses, and rides atop Terminfo.
 .
 These files are necessary for Rust development using Notcurses.



The Notcurses C++ and Python wrappers are already being packaged. The Rust
wrappers are not yet being packaged (see
https://github.com/dankamongmen/notcurses/issues/355), but with the recent
release of Notcurses 2.0 and its stable API, that time has come. All of these
wrappers come from the same upstream source, though this package will be using
source taken from crates.io.

-- 
nick black -=- https://www.nick-black.com
to make an apple pie from scratch,
you need first invent a universe.



Bug#969408: RFS: growlight/1.2.11-1 [ITP] -- Disk manipulation and system preparation tool

2020-09-02 Thread Nick Black (Public gmail account)
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am a Debian Maintainer looking for a sponsor for my package "growlight":

 * Package name: growlight
   Version : 1.2.11-1
   Upstream Author : Nick Black 
 * URL : https://nick-black.com/dankwiki/index.php/growlight
 * License : GPL-3.0+
 * Vcs : https://github.com/dirty-south-supercomputing/growlight-
gbp
   Section : utils

It builds those binary packages:

  growlight - Disk manipulation and system preparation tool

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

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

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

  dget -x
https://mentors.debian.net/debian/pool/main/g/growlight/growlight_1.2.11-1.dsc

Changes for the initial release:

 growlight (1.2.11-1) unstable; urgency=medium
 .
   * Initial Debian packaging (Closes: #700060)

Regards,
--
  Nick Black



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

Kernel: Linux 5.8.5nlb (SMP w/64 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



Bug#923851: RFP: ghidra -- Ghidra is a software reverse engineering framework

2019-08-28 Thread Gmail
> On Thu, 21 Mar 2019 11:22:28 +0800 Yangfl wrote:
> I'm willing to package it, as long as they publish its source!

Any update on this?

As Antonio mentioned the Ghidra source has been published: 
https://github.com/NationalSecurityAgency/ghidra

Best,
Harsha


Bug#907392:

2018-08-29 Thread Pablo Sánchez [gmail]
Dam, it was my thread on the subject, before Mark adviced me to post here.
I'll try fbcopy / fbexport as backup .


Regards


Bug#859234:

2018-08-29 Thread Pablo Sánchez [gmail]
Found it ???

On x86/amd64 I usually have to config RemoteBindAddress with computer ip
number after install , as connections where rejected .
I realized I was also configuring the same on  raspberry pi. After
commenting that line con firebird.conf, after restart and power off / power
on, service started on boot .

Pablo Sánchez


Bug#859234:

2018-08-29 Thread Pablo Sánchez [gmail]
Damyan, I'm trying to find the meaning of "status=252"

Excerpt from /var/log/syslog
...
Aug 29 09:17:58 raspberrypi systemd[1]: Started Daily apt download
activities.
Aug 29 09:18:10 raspberrypi fbguard[451]: Time out waiting for fbserver
process start
Aug 29 09:18:10 raspberrypi systemd[1]: firebirAccept & closed3.0.service:
Control process exited, code=exited status=252
Aug 29 09:18:10 raspberrypi systemd[1]: firebird3.0.service: Failed with
result 'exit-code'.
Aug 29 09:18:10 raspberrypi systemd[1]: Failed to start Firebird Database
Server ( SuperServer ).
Aug 29 09:18:10 raspberrypi systemd[1]: Reached target Multi-User System.
'''
It's a normal install, with a database definition on databases.conf . After
boot, I just start firebird with "service firebird3.0 start"

root@raspberrypi:~# systemctl  status firebird3.0
● firebird3.0.service - Firebird Database Server ( SuperServer )
   Loaded: loaded (/lib/systemd/system/firebird3.0.service; enabled; vendor
preset: enabled)
   Active: failed (Result: exit-code) since Wed 2018-08-29 09:37:42 -03;
18min ago
  Process: 450 ExecStart=/usr/sbin/fbguard -pidfile
/run/firebird3.0/default.pid -daemon -forever (code=exited, status=252)

Aug 29 09:37:26 raspberrypi systemd[1]: Starting Firebird Database Server (
SuperServer )...
Aug 29 09:37:42 raspberrypi fbguard[450]: Time out waiting for fbserver
process start
Aug 29 09:37:42 raspberrypi systemd[1]: firebird3.0.service: Control
process exited, code=exited status=252
Aug 29 09:37:42 raspberrypi systemd[1]: firebird3.0.service: Failed with
result 'exit-code'.
Aug 29 09:37:42 raspberrypi systemd[1]: Failed to start Firebird Database
Server ( SuperServer ).
root@raspberrypi:~#


Pablo Sánchez


Bug#859234:

2018-08-28 Thread Pablo Sánchez [gmail]
Hi !
Bug seems to be present on armhf (raspberry pi model 3+) .

In /var/log/syslog I get :
...
Aug 28 00:04:34 raspberrypi systemd[1]: Started User Manager for UID 1001.
Aug 28 00:04:43 raspberrypi fbguard[449]: Time out waiting for fbserver
process start
Aug 28 00:04:43 raspberrypi systemd[1]: firebird3.0.service: Control
process exited, code=exited status=252
Aug 28 00:04:43 raspberrypi systemd[1]: firebird3.0.service: Failed with
result 'exit-code'.
Aug 28 00:04:43 raspberrypi systemd[1]: Failed to start Firebird Database
Server ( SuperServer ).
Aug 28 00:04:43 raspberrypi systemd[1]: Reached target Multi-User System.
Aug 28 00:04:43 raspberrypi systemd[1]: Reached target Graphical Interface.
...

Version is 3.0.3

ii  firebird3.0-common  3.0.3.32900.ds4-4
ii  firebird3.0-common-doc  3.0.3.32900.ds4-4
ii  firebird3.0-doc 3.0.3.32900.ds4-4
ii  firebird3.0-examples3.0.3.32900.ds4-4
ii  firebird3.0-server  3.0.3.32900.ds4-4
ii  firebird3.0-server-core:armhf   3.0.3.32900.ds4-4
ii  firebird3.0-utils   3.0.3.32900.ds4-4

I have to start the server manually.

Regards

Pablo Sánchez


Bug#907392: firebird3.0-utils: tables with varchar attributes with big size cannot be backed up with gbak

2018-08-27 Thread Pablo Sánchez [gmail]
Package: firebird3.0-utils
Version: 3.0.3.32900.ds4-4
Severity: grave
Justification: renders package unusable (kind of)

1- create database, and insert on column (using raspbian)

SQL> create database '/srv/data/debian-test.fdb'
CON> user 'SYSDBA'
CON> password 'masterkey'
CON> page_size 8192
CON> default character set iso8859_1;
SQL> commit ;
SQL> exit ;

2- create a table with a big size varchar and insert data into it .
CREATE TABLE TEST
(
  ID INTEGER,
  VC VARCHAR(32765)
);

INSERT INTO TABLE1 (ID, TEXT) VALUES ('1', 'abcdef123456');

3- backup database

root@raspberrypi:/srv/data# gbak -b -v  -user SYSDBA -password masterkey
/srv/data/debian-test.fdb /srv/data/debian-test.fbk
gbak:readied database /srv/data/debian-test.fdb for backup
gbak:creating file /srv/data/debian-test.fbk
gbak:starting transaction
gbak:database /srv/data/debian-test.fdb has a page size of 8192 bytes.
gbak:writing domains
gbak:writing domain RDB$1
gbak:writing domain RDB$2
gbak:writing shadow files
gbak:writing character sets
gbak:writing collations
gbak:writing tables
gbak:writing table TABLE1
gbak: writing column ID
gbak: writing column TEXT
gbak:writing types
gbak:writing filters
gbak:writing id generators
gbak:writing exceptions
gbak:writing functions
gbak:writing stored procedures
gbak:writing packages
gbak:writing data for table TABLE1
gbak: ERROR:message length error (encountered -32758, expected 32778)
gbak: ERROR:gds_$receive failed
gbak:Exiting before completion due to errors

Note that if I create db on amd64 and restore on raspberrypi, I get the
same error .
But if create db on amd64 and restore on amd64 there is no error and data
is there.
I use buster now, but on v2.5 on stretch had the same problem. After
posting on
firebrid-support , I was suggested to post here.

-- System Information:
Distributor ID:Raspbian
Description:Raspbian GNU/Linux testing (buster)
Release:testing
Codename:buster
Architecture: armv7l

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

Versions of packages firebird3.0-utils depends on:
ii  firebird3.0-common  3.0.3.32900.ds4-4
ii  firebird3.0-common-doc  3.0.3.32900.ds4-4
ii  libc6   2.27-5+rpi1
ii  libedit23.1-20180525-1
ii  libfbclient23.0.3.32900.ds4-4
ii  libgcc1 1:8.1.0-12+rpi1
ii  libncurses6 6.1+20180714-1
ii  libstdc++6  8.1.0-12+rpi1
ii  libtinfo6   6.1+20180714-1
ii  libtommath1 1.0.1-1

Versions of packages firebird3.0-utils recommends:
ii  firebird3.0-server-core  3.0.3.32900.ds4-4

Versions of packages firebird3.0-utils suggests:
pn  firebird3.0-doc 
ii  firebird3.0-server  3.0.3.32900.ds4-4

-- no debconf information
Regards

Pablo Sánchez


Bug#889595: grep -w mismatching

2018-02-04 Thread George Vasiliou (GMAIL)
Package: grep
Version: 3.1-2

Hello,

I am trying to use grep -w to match a word, but it seems that grep ignores
the -w switch and returns all occurencies.

Test case:
$ cat file1
one two three
one-two-three
one-two
two-three

$ grep -w 'two' file1 #or grep -Ew 'two'
Result: all four lines of file1 are returned.

According  to man grep:
-w, --word-regexp
  Select only those lines containing matches that form whole
words.  The test is  that  the  matching  substring  must either  be  at
the  beginning  of the line, or preceded by a non-word constituent
character.  Similarly, it must be either at the end of the line or followed
by a non-word  constituent  character. Word-constituent  characters
are letters,
digits, and the underscore.  This option has no effect if -x is also
specified.


Since dash '-' does not belong to word-constituent characters i was
expecting only first line to be matched : one two three

Just for the record , even options \, or \btwo\b will also return all
four lines.

Easy workaround for the job would be to use
grep ' two ' or grep -E '\stwo\s'

But this bug report is focused on the failure of -w flag

Cheers,

George Vasiliou


Bug#878648: gnome-color-manager: viewer-example-??.png files in wrong path

2018-02-02 Thread Daniele GMAIL

On Sun, 15 Oct 2017 14:23:24 +0200 Jonas Smedegaard  wrote:
> Package: gnome-color-manager
> Version: 3.26.0-1
> Severity: normal
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> gnome-color-manager ships with four images
> /usr/share/gnome-color-manager/figures/viewer-example-??.png
> (with "??" being 00→03).
>
> Running gcm-viewer emits the following error:
>
> (gcm-viewer:9170): GnomeColorManager-WARNING **: failed to load 
viewer-example-00.png: Failed to open file 
'/usr/share/gnome-software/figures/viewer-example-00.png': No such file 
or directory

>
> Inside the gcm-viewer tool, "From sRGB" and "To sRGB" shows no image.
>
> After hacking the system with this commands, images show:
>
> ln -sT /usr/share/gnome-color-manager /usr/share/gnome-software
>
> I don't know if the proper solution is to install those images below
> /usr/share/gnome-software or to patch/configure the tool to instead look
> below /usr/share/gnome-color-manager where the images actually exist.
>
>
> - Jonas
>
> - -- System Information:
> Debian Release: buster/sid
> APT prefers buildd-unstable
> APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 
'experimental')

> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8), 
LANGUAGE=da_DK.UTF-8 (charmap=UTF-8)

> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages gnome-color-manager depends on:
> ii colord 1.3.3-2
> ii libc6 2.24-17
> ii libcairo2 1.14.10-1
> ii libcanberra-gtk3-0 0.30-3
> ii libcanberra0 0.30-3
> ii libcolord-gtk1 0.1.26-1.1
> ii libcolord2 1.3.3-2
> ii libexif12 0.6.21-2.1
> ii libexiv2-14 0.25-3.1
> ii libgcc1 1:7.2.0-10
> ii libgdk-pixbuf2.0-0 2.36.11-1
> ii libglib2.0-0 2.54.1-1
> ii libgtk-3-0 3.22.24-1
> ii liblcms2-2 2.8-4
> ii libpango-1.0-0 1.40.12-1
> ii libstdc++6 7.2.0-10
> ii libtiff5 4.0.8-5
> ii libvte-2.91-0 0.50.1-1
> ii policykit-1 0.105-18
>

just sudo copied files from /usr/share/gnome-color-manager/figures/ into 
/usr/share/gnome-software (which in my case already existed with other 
files, so create a simlink with that name could not be a good idea)




Bug#880028: One more test

2017-10-29 Thread George Vasiliou (GMAIL)
In case that makes any difference, the bug mentioned in linux image 4.13 is
also present in the 4.14 linux image available at experimental repos :
linux-image-4.14.0-rc5-amd64/experimental 4.14~rc5-1~exp1 amd64

George Vasiliou


Bug#876136: [boomaga] Can't open file from .cache folder

2017-09-18 Thread Gmail
Package: boomaga
Version: 0.7.1-1+b4
Severity: grave

--- Please enter the report below this line. ---
Hi, boomaga is completly unusable due bug in upstream, see 
https://github.com/Boomaga/boomaga/issues/50




--- System information. ---
Architecture: 
Kernel:   Linux 4.12.0-1-amd64

Debian Release: buster/sid
  900 testing www.deb-multimedia.org 
  900 testing packages.x2go.org 
  900 testing http.debian.net 
  500 stretch download.docker.com 
  500 stable  people.debian.org 
  500 stable  dl.google.com 
  500 jessie  deb.playonlinux.com 
  500 all liveusb.info 

--- Package information. ---
Depends   (Version) | Installed
===-+-
cups| 2.2.4-6
libc6 (>= 2.14) | 
libcups2 (>= 1.4.0) | 
libgcc1  (>= 1:3.0) | 
libpoppler-cpp0v5   (>= 0.46.0) | 
libpoppler68(>= 0.57.0) | 
libqt5core5a(>= 5.9.0~beta) | 
libqt5dbus5  (>= 5.0.2) | 
libqt5gui5   (>= 5.8.0) | 
libqt5printsupport5  (>= 5.0.2) | 
libqt5widgets5   (>= 5.7.0) | 
libsnappy1v5| 
libstdc++6 (>= 5.2) | 


Package's Recommends field is empty.

Package's Suggests field is empty.





-- 
Regards,
Andrey Spitsyn



Bug#859289: Plasma has error QXcbConnection: XCB error

2017-04-01 Thread gmail

Package: plasma-desktop

Version: 4:5.8.4-1

Hello!

I use debian 9 stretch with DE KDE plasma (5.8.6 in info center) with 
latest updates.



uname -a:

Linux windows 4.9.0-2-amd64 #1 SMP Debian 4.9.13-1 (2017-02-27) x86_64 
GNU/Linux


When i work in my system i has some errors in terminal with text:

QXcbConnection: XCB error: 2 (BadValue), sequence: 22586, resource id: 
106954753, major code: 142 (Unknown), minor code: 3


Id is different, for example in attachment's files.


QXcbConnection: XCB error: 2 (BadValue), sequence: 21904, resource id: 
148897798, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 22005, resource id: 
39845894, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 24304, resource id: 
123731974, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 24329, resource id: 
119537680, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 25431, resource id: 
100663300, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 25914, resource id: 
119537680, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 25939, resource id: 
146800645, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 26045, resource id: 
39845894, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 26133, resource id: 
146800645, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 26199, resource id: 
119537680, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 26283, resource id: 
123731974, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 26380, resource id: 
39845894, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 26439, resource id: 
146800645, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 26498, resource id: 
39845894, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 26540, resource id: 2097156, 
major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 27714, resource id: 
92274694, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 27971, resource id: 
119537680, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 27998, resource id: 
123731974, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 28965, resource id: 
146800645, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 29012, resource id: 
106954753, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 29064, resource id: 
92274694, major code: 142 (Unknown), minor code: 3
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:99: 
TypeError: Cannot read property of null
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:99: 
TypeError: Cannot read property of null
QXcbConnection: XCB error: 2 (BadValue), sequence: 35725, resource id: 
119537680, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 35758, resource id: 
146800645, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 36514, resource id: 
146800645, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 36543, resource id: 
119537680, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 36627, resource id: 
123731974, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 36675, resource id: 
39845894, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 40248, resource id: 
146800645, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 40273, resource id: 
148897798, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 40364, resource id: 2097156, 
major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 43080, resource id: 
92274694, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 43109, resource id: 
148897798, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 43139, resource id: 2097156, 
major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 43272, resource id: 
106954753, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 43320, resource id: 
92274694, 

Bug#854573: kernel BUG: stack guard page was hit at

2017-02-08 Thread gmail

Package: kernel
Version: 4.9.2-2

  When I go to Standby my laptop (dell xps 13 2015, BIOS A09) it not do it.
I can see that my screen has black screen (backlight is on) about 10 sec after 
it the laptop comeback to KDE plasma but i can do nothing before it (if i input 
to an terminal an command then it is input but not running and I can see the 
black field below the cursor).
Wifi network is down too.
I can not run powerdown or any actions this results to restart xserver (It 
looks like but not true may be). I need press and holder the power button and 
it wil be power down.
If after I run an konsole and repeat the actions in the konsole i can see the 
message:
kernel:[100577.835841] BUG: stack guard page was hit at b2a1817c41d8 (stack 
is b2a1817c..b2a1817c3fff)

I am using Debian GNU/Linux 9 stretch 4.9.0-1-amd64 #1 SMP Debian 4.9.2-2 
(2017-01-12) x86_64 GNU/Linux
In attached dmesg file (before the error after the error i can not run the 
command).

[0.00] microcode: microcode updated early to revision 0x24, date = 
2016-04-29
[0.00] Linux version 4.9.0-1-amd64 (debian-ker...@lists.debian.org) 
(gcc version 6.3.0 20161229 (Debian 6.3.0-2) ) #1 SMP Debian 4.9.2-2 
(2017-01-12)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-1-amd64 
root=UUID=b5866ade-330b-414a-8ec0-f66a832d10e4 ro quiet splash pcie_aspm=force
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, 
using 'standard' format.
[0.00] x86/fpu: Using 'eager' FPU context switches.
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x00057fff] usable
[0.00] BIOS-e820: [mem 0x00058000-0x00058fff] reserved
[0.00] BIOS-e820: [mem 0x00059000-0x0009dfff] usable
[0.00] BIOS-e820: [mem 0x0009e000-0x0009] reserved
[0.00] BIOS-e820: [mem 0x0010-0xc86eefff] usable
[0.00] BIOS-e820: [mem 0xc86ef000-0xc8ba8fff] reserved
[0.00] BIOS-e820: [mem 0xc8ba9000-0xdadcefff] usable
[0.00] BIOS-e820: [mem 0xdadcf000-0xdae91fff] reserved
[0.00] BIOS-e820: [mem 0xdae92000-0xdaebbfff] ACPI data
[0.00] BIOS-e820: [mem 0xdaebc000-0xdb7f3fff] ACPI NVS
[0.00] BIOS-e820: [mem 0xdb7f4000-0xdba9cfff] reserved
[0.00] BIOS-e820: [mem 0xdba9d000-0xdbafdfff] type 20
[0.00] BIOS-e820: [mem 0xdbafe000-0xdbafefff] usable
[0.00] BIOS-e820: [mem 0xdd00-0xdf7f] reserved
[0.00] BIOS-e820: [mem 0xf800-0xfbff] reserved
[0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved
[0.00] BIOS-e820: [mem 0xfed0-0xfed03fff] reserved
[0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] reserved
[0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved
[0.00] BIOS-e820: [mem 0xff00-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00021f7f] usable
[0.00] NX (Execute Disable) protection: active
[0.00] efi: EFI v2.31 by American Megatrends
[0.00] efi:  ACPI=0xdae9a000  ACPI 2.0=0xdae9a000  SMBIOS=0xf 
[0.00] SMBIOS 2.8 present.
[0.00] DMI: Dell Inc. XPS 13 9343/0TM99H, BIOS A09 08/29/2016   


   
[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved 


   
[0.00] e820: remove [mem 0x000a-0x000f] usable  


   
[0.00] e820: last_pfn = 0x21f800 max_arch_pfn = 0x4 


   
[0.00] MTRR default type: uncachable

Bug#850178: not work AutoInput

2017-01-04 Thread gmail

Package: keepassx
Version: 2.0.3

When i want use autoInput to firefox (the browser is not important). 
AutoInput is working only first time. In other time keepassx randomly 
select item.
I am using debian testing Linux 4.8.0-1-amd64 #1 SMP Debian 4.8.7-1 
(2016-11-13) x86_64 GNU/Linux.





Bug#847390: hard freeze on laptop dell xps 13 2015

2017-01-04 Thread gmail

On Wed, 7 Dec 2016 22:20:48 +0300 gmail <iorlo...@gmail.com> wrote:
> Package: xserver-xorg
>
> Version: 1:7.7+18
>
> When i work to my laptop (dell xps 13 2015, BIOS A9) i have got
> sometimes (i can not get the freeze 1-2 days) hard freeze (keyboard not
> work, touch pad don't work too, fan is work on 100%). I has guaranteed
> the error when i start play to games but i can get the error in random
> time when i work to browser or libreoffice. After the freeze i do power
> down and powerup and i can play to the game without problems.
>
> In .xsessions-errors i see QXcbConnection: XCB error: 3 (BadWindow),
> sequence: 40719, resource id: 41943865, major code: 18 (ChangeProperty),
> minor code: 0.
>
>
> http://pastebin.com/Gji2CJXQ - dpkg --status xserver-xorg
>
> http://pastebin.com/R80SNdK5 - .xsession-errors
>
> http://pastebin.com/N3sQCarU - dmesg
>
> I am using debian testing Linux 4.8.0-1-amd64 #1 SMP Debian 4.8.7-1
> (2016-11-13) x86_64 GNU/Linux.
>
>
>
>
>
>
Now i can see that RAM on the laptop is use on 100% (8 Gb/ 8 Gb). But I 
can not see that the use of the entire RAM. It occur randomly.


Bug#847390: hard freeze on laptop dell xps 13 2015

2016-12-07 Thread gmail

Package: xserver-xorg

Version: 1:7.7+18

When i work to my laptop (dell xps 13 2015, BIOS A9) i have got 
sometimes (i can not get the freeze 1-2 days) hard freeze (keyboard not 
work, touch pad don't work too, fan is work on 100%). I has guaranteed 
the error when i start play to games but i can get the error in random 
time when i work to browser or libreoffice. After the freeze i do power 
down and powerup and i can play to the game without problems.


In .xsessions-errors i see QXcbConnection: XCB error: 3 (BadWindow), 
sequence: 40719, resource id: 41943865, major code: 18 (ChangeProperty), 
minor code: 0.



http://pastebin.com/Gji2CJXQ - dpkg --status xserver-xorg

http://pastebin.com/R80SNdK5 - .xsession-errors

 http://pastebin.com/N3sQCarU - dmesg

I am using debian testing Linux 4.8.0-1-amd64 #1 SMP Debian 4.8.7-1 
(2016-11-13) x86_64 GNU/Linux.




Bug#845207: CMST and ConnMan stopped working after last sid update

2016-11-21 Thread George Vasiliou (GMAIL)
Sorry, i forgot to attach the apt log file of yesterday to have a look of
all the files upgraded.
I have to point out that before yesterday evening upgrade, everything was
working ok with cmst and connman.
Start-Date: 2016-11-21  00:38:07
Commandline: apt-get upgrade
Upgrade: 
libreoffice-wiki-publisher:i386 (1.2.0+LibO5.2.3~rc3-1, 1.2.0+LibO5.2.3-2), 
libportmidi0:i386 (1:184-2.2, 1:217-4), 
libreoffice-math:i386 (1:5.2.3~rc3-1+b1, 1:5.2.3-2), 
libmpx2:i386 (6.2.0-13, 6.2.1-4), 
exim4-base:i386 (4.88~RC4-2, 4.88~RC5-1), 
libgcj17:i386 (6.2.0-13, 6.2.1-4), 
iso-codes:i386 (3.70-1, 3.71-1), 
xserver-xorg-input-synaptics:i386 (1.8.3-2, 1.9.0-1), 
libreoffice-script-provider-js:i386 (1:5.2.3~rc3-1, 1:5.2.3-2), 
xserver-xorg-video-r128:i386 (6.10.1-1, 6.10.1-2), 
libreoffice-report-builder-bin:i386 (1:5.2.3~rc3-1+b1, 1:5.2.3-2), 
libservlet3.1-java:i386 (8.0.38-2, 8.0.39-1), 
icedove:i386 (1:45.4.0-1, 1:45.5.0-1), 
libseccomp2:i386 (2.3.1-2, 2.3.1-2.1), 
libao4:i386 (1.1.0-3, 1.2.2-1), 
libclutter-1.0-0:i386 (1.26.0+dfsg-1, 1.26.0+dfsg-2), 
libreoffice-sdbc-postgresql:i386 (1:5.2.3~rc3-1+b1, 1:5.2.3-2), 
libgroupsock8:i386 (2016.11.06-1, 2016.11.17-1), 
iptables:i386 (1.6.0-4, 1.6.0+snapshot20161117-1), 
libdrm-nouveau2:i386 (2.4.71-1, 2.4.73-1), 
xserver-xorg-video-amdgpu:i386 (1.1.2-1, 1.2.0-1), 
linux-libc-dev:i386 (4.8.5-1, 4.8.7-1), 
libspeechd2:i386 (0.8.5-3, 0.8.5-4), 
oxygen-icon-theme:i386 (5:5.27.0-1, 5:5.28.0-1), 
libdiscid0:i386 (0.6.1-5, 0.6.1-6), 
qt5-gtk-platformtheme:i386 (5.7.1~20161021+dfsg-5, 5.7.1~20161021+dfsg-6), 
gir1.2-clutter-1.0:i386 (1.26.0+dfsg-1, 1.26.0+dfsg-2), 
lxpanel-data:i386 (0.8.2-1, 0.9.0-1), 
libproxy1v5:i386 (0.4.13-1, 0.4.13-1.1), 
va-driver-all:i386 (1.7.3-1, 1.7.3-2), 
libgnutls-openssl27:i386 (3.5.6-2, 3.5.6-7), 
libreoffice-java-common:i386 (1:5.2.3~rc3-1, 1:5.2.3-2), 
p7zip:i386 (16.02+dfsg-1, 16.02+dfsg-2), 
git-man:i386 (1:2.10.2-2, 1:2.10.2-3), 
libsystemd0:i386 (232-3, 232-5), 
libvisual-0.4-plugins:i386 (1:0.4.0+dfsg1-9, 1:0.4.0+dfsg1-10), 
libreoffice-base:i386 (1:5.2.3~rc3-1+b1, 1:5.2.3-2), 
libzmq5:i386 (4.2.0-1, 4.2.0-2), 
gstreamer1.0-plugins-good:i386 (1.10.0-1, 1.10.1-1), 
libreoffice-core:i386 (1:5.2.3~rc3-1+b1, 1:5.2.3-2), 
cpp-6:i386 (6.2.0-13, 6.2.1-4), 
libpsl5:i386 (0.14.0-1, 0.15.0-1), 
libofa0:i386 (0.9.3-12, 0.9.3-13), 
libgda-5.0-common:i386 (5.2.4-2, 5.2.4-3), 
binutils:i386 (2.27.51.20161108-1, 2.27.51.20161118-2), 
libgpg-error0:i386 (1.24-2, 1.25-1), 
xserver-xorg-video-trident:i386 (1:1.3.7-1+b2, 1:1.3.7-2), 
libitm1:i386 (6.2.0-13, 6.2.1-4), 
lightdm-gtk-greeter:i386 (2.0.1-2, 2.0.2-1), 
at-spi2-core:i386 (2.22.0-3, 2.22.0-4), 
gdebi-core:i386 (0.9.5.7, 0.9.5.7+nmu1), 
libqt5dbus5:i386 (5.7.1~20161021+dfsg-5, 5.7.1~20161021+dfsg-6), 
xserver-xorg-input-libinput:i386 (0.20.0-1, 0.22.0-1), 
git:i386 (1:2.10.2-2, 1:2.10.2-3), 
exim4-daemon-light:i386 (4.88~RC4-2, 4.88~RC5-1), 
libqt5widgets5:i386 (5.7.1~20161021+dfsg-5, 5.7.1~20161021+dfsg-6), 
libfbclient2:i386 (3.0.1.32609.ds4-9, 3.0.1.32609.ds4-10), 
gstreamer1.0-plugins-bad:i386 (1.10.0-1, 1.10.1-1), 
libip6tc0:i386 (1.6.0-4, 1.6.0+snapshot20161117-1), 
udev:i386 (232-3, 232-5), 
libcilkrts5:i386 (6.2.0-13, 6.2.1-4), 
gstreamer1.0-plugins-base:i386 (1.10.0-1, 1.10.1-1), 
xfce4-panel:i386 (4.12.1-1, 4.12.1-2), 
libasan3:i386 (6.2.0-13, 6.2.1-4), 
libquadmath0:i386 (6.2.0-13, 6.2.1-4), 
libreoffice-librelogo:i386 (1:5.2.3~rc3-1, 1:5.2.3-2), 
libassuan0:i386 (2.4.3-1, 2.4.3-2), 
gcc-6-base:i386 (6.2.0-13, 6.2.1-4), 
gdebi:i386 (0.9.5.7, 0.9.5.7+nmu1), 
xserver-xorg-video-savage:i386 (1:2.3.8-1+b1, 1:2.3.8-2), 
python3-uno:i386 (1:5.2.3~rc3-1+b1, 1:5.2.3-2), 
debianutils:i386 (4.8, 4.8.1), 
libudev1:i386 (232-3, 232-5), 
rsyslog:i386 (8.22.0-2+b1, 8.23.0-1), 
libgcc1:i386 (1:6.2.0-13, 1:6.2.1-4), 
libreoffice-script-provider-python:i386 (1:5.2.3~rc3-1, 1:5.2.3-2), 
libreoffice-style-galaxy:i386 (1:5.2.3~rc3-1, 1:5.2.3-2), 
libreoffice-base-core:i386 (1:5.2.3~rc3-1+b1, 1:5.2.3-2), 
libiptc0:i386 (1.6.0-4, 1.6.0+snapshot20161117-1), 
libdrm-amdgpu1:i386 (2.4.71-1, 2.4.73-1), 
libinput-bin:i386 (1.5.0-1, 1.5.1-1), 
libreoffice-ogltrans:i386 (1:5.2.3~rc3-1+b1, 1:5.2.3-2), 
dpkg:i386 (1.18.14, 1.18.15), 
libtiff5:i386 (4.0.6-3, 4.0.7-1), 
libreoffice-impress:i386 (1:5.2.3~rc3-1+b1, 1:5.2.3-2), 
libqt5gui5:i386 (5.7.1~20161021+dfsg-5, 5.7.1~20161021+dfsg-6), 
libva1:i386 (1.7.3-1, 1.7.3-2), 
libao-common:i386 (1.1.0-3, 1.2.2-1), 
python3-speechd:i386 (0.8.5-3, 0.8.5-4), 
libgcc-6-dev:i386 (6.2.0-13, 6.2.1-4), 
p7zip-full:i386 (16.02+dfsg-1, 16.02+dfsg-2), 
libubsan0:i386 (6.2.0-13, 6.2.1-4), 
iceweasel:i386 (45.4.0esr-2, 45.5.0esr-1), 
g++-6:i386 (6.2.0-13, 6.2.1-4), 
exim4-config:i386 (4.88~RC4-2, 4.88~RC5-1), 
libatspi2.0-0:i386 (2.22.0-3, 2.22.0-4), 
libmplex2-2.1-0:i386 (1:2.1.0+debian-4+b1, 1:2.1.0+debian-5), 
libzvbi0:i386 (0.2.35-12, 0.2.35-13), 
libdvbpsi10:i386 (1.3.0-4, 1.3.0-5), 
libgfortran3:i386 (6.2.0-13, 6.2.1-4), 
libgda-5.0-4:i386 (5.2.4-2+b1, 5.2.4-3), 
libproxy-tools:i386 

Bug#845207: CMST and ConnMan stopped working after last sid update

2016-11-21 Thread George Vasiliou (GMAIL)
Package: cmst

Hello,
Under Debian 8 Sid 32bits with LXDE i updated yesterday my system.
On the next reboot i got the following error by cmst:

CMST: Unable to create an interface to connman on the system bus.
CMST will not be able to communicate with connman.

As a result , my wifi was dead and not able to get connected to my home
wlan (i'm using rtl8723se on laptop).

Looking at apt log, a lot of libqt5 libs in which cmst depends on have been
upgraded yesterday.

It is not clear to me if i should file this bug as a cmst bug or as a
libqt5 bug.

In any case i didn't try to operate connman by command line to verify if i
can establish a wifi connection.
I noticed though that packages libgnutls30 and libxtables11 which connman
depends on, have also been upgraded yesterday.

As a workaround i succeed to connect in my wifi network by purging connman
(but not cmst) and editing my /etc/network/interfaces file according to
Debian Wiki Command Line Section (https://wiki.debian.org/WiFi/HowToUse) .

Maybe i should reinstall connman and use a different tool than cmst or
manage connman by command line to verify if connman works ok - not tried
yet.

Regards
George V.


Bug#840650: Firmware Part 2

2016-10-14 Thread George Vasiliou (GMAIL)
Booting with the previous linux image 4.7.5.1 and after setting firmware
swtich fwlps to off , seems that established a rigid connection.

Maybe the new kernel 4.7.6.1 is more "sensitive" on the FW flags, since i
had never issues before with fwlps which had been left to it's default
value (1) for a lot of months.

Maybe i could try to upgrade again in the new linux-image 4.7.6.1 and see
how it performs with fwlps off.

I switched off fwlps by using
echo "options rtl8723be fwlps=0">/etc/modprobe.d/rtl8723be.conf
(or could be done by adding above line in the end of the existed
modsetting.conf file in the same directory).
PS: All the rest options of rtl8723be are left to default.

George V.


Bug#840650: Firmware

2016-10-13 Thread George Vasiliou (GMAIL)
I think firmware is ok.

root@debian:/lib/firmware/rtlwifi# stat rtl8723befw.bin
File: 'rtl8723befw.bin'
Size: 30746
Blocks: 64
IO Block: 4096   regular file
Device: 809h/2057d Inode: 267698  Links: 1
Access: (0644/-rw-r--r--)  Uid: (0/root)   Gid: (0/root)
Access: 2016-10-13 23:43:14.282229846 +0300
Modify: 2016-09-18 06:15:29.0 +0300
Change: 2016-09-22 00:24:27.314880254 +0300
 Birth: -

Moreover, there is only one rtl8723 firmware file in my system .
I suppose if it was a FW bug i wouldn't be capable to use wifi even with
3.16 or with 4.7.5.1 (before the upgrade).

George V


Bug#834243: [src:linux] Hibernation does not work on Lenovo e130 (intel ivy bridge)

2016-08-13 Thread Gmail
Package: src:linux
Version: linux/4.6.4-1
Severity: normal

--- Please enter the report below this line. ---
Hibernation does not work.
Laptop starts to hibernate, but fails and reboots after some time.
May be related to #833009.


Note: I booteed last working kernel. 


00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM
Controller (rev 09) Subsystem: Lenovo 3rd Gen Core processor DRAM
Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF-
FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: ivb_uncore

00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core
processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo 3rd Gen Core processor Graphics Controller Control:
I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr-
DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: 
Kernel driver in use: i915
Kernel modules: i915

00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset
Family USB xHCI Host Controller (rev 04) (prog-if 30 [XHCI]) Subsystem:
Lenovo 7 Series/C210 Series Chipset Family USB xHCI Host Controller
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+
ParErr- DEVSEL=medium >TAbort- SERR-  Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:16.0 Communication controller: Intel Corporation 7 Series/C210
Series Chipset Family MEI Controller #1 (rev 04) Subsystem: Lenovo 7
Series/C210 Series Chipset Family MEI Controller Control: I/O- Mem+
BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR-
FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast
>TAbort- SERR- pin A routed to IRQ 28
Region 0: Memory at f1715000 (64-bit, non-prefetchable)
[size=16] Capabilities: 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset
Family USB Enhanced Host Controller #2 (rev 04) (prog-if 20 [EHCI])
Subsystem: Lenovo 7 Series/C210 Series Chipset Family USB Enhanced Host
Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF-
FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR-  Kernel driver in use: ehci-pci
Kernel modules: ehci_pci

00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset
Family High Definition Audio Controller (rev 04) Subsystem: Lenovo 7
Series/C210 Series Chipset Family High Definition Audio Controller
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B-
ParErr- DEVSEL=fast >TAbort- SERR-  Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset
Family PCI Express Root Port 1 (rev c4) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B-
ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr-
SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset
Family PCI Express Root Port 2 (rev c4) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B-
ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr-
SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset
Family PCI Express Root Port 3 (rev c4) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B-
ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr-
SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1c.5 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset
Family PCI Express Root Port 6 (rev c4) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B-
ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr-
SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset
Family USB Enhanced Host Controller #1 (rev 04) 

Bug#829586: Package: iio-sensor-proxy

2016-07-04 Thread George Vasiliou (GMAIL)
Package: iio-sensor-proxy

Hello,
I would like to mention that i have sucesfully install iio-sensor-proxy in
my Debain Jessie Installation equipped with XFCE4.12 (installed by
unstable) and kernel 4.7.0.rc4 (installed by experimental), but automatic
screen rotation is not working.

Although, following all the instructions given by the iio-sensor-proxy
developer i can confirm that my accelerometer is correctly detected and it
is functional.

Moreover, running #monitor-sensor command i can get on the termina correct
info about my orientation as i turn my convertible laptop left or right or
even upside down.

Am i doing something wrong, or it is just XFCE who does not suppports
iio-sensor-proxy and i should switch to Gnome?

Regards,

George Vasiliou
Toshiba Radius 11 L10WC-10C


Bug#827828: Package: installation-reports

2016-06-21 Thread George Vasiliou (GMAIL)
Package: installation-reports

Hi there,
I would like to mention a kind of bug in your net-install iso image.

When tried to install Debian on my net book (Toshiba Radius 11 L10WC10C)
using the debian-8.5.0-amd64-netinst.iso image i got the following error:

Installer was prompting me to provide proprietary drivers for
rtlwifi/rtl8723befw.bin.

As a new user that i thought to try Debian, i didn't had this driver to
feed the installer and as a resut the installation made was a basic one
without internet connection.

Although i succeed to find this driver on web, i was not capable to make
the installer load this rtl8723 driver.
Maybe a kind of typical file browser within the Debian Installer could be a
good idea, to allow me to drive Debian Installer to where this driver file
is.

On the other hand consider a new user trying to test Debian, and the whole
thing collapses for a missing driver (while other distros like Ubuntu
provide that driver out-of-the-box).

Regards,
George Vasiliou
Greece


Bug#33975: [Bug c++/6905] Suggested g++ warning: changed semantics of conditional expressions

2016-01-14 Thread webrown.cpp at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=6905

W E Brown  changed:

   What|Removed |Added

 CC||webrown.cpp at gmail dot com

-- 
You are receiving this mail because:
You reported the bug.


Bug#793303: marking this as "won't fix" and closing the bug

2015-09-07 Thread Colin King (gmail)
Hi there, since this is not fixable, I'm marking this as won't fix.



Bug#781506: thermald: some documentation for the user

2015-09-01 Thread Colin King (gmail)
Hi Ritesh,

does man 5 thermal-conf.xml provide enough information?

Colin



Bug#783160: Further detail

2015-05-13 Thread Ugo Poddine su Gmail
Hello everyone,

 

also if it should be already known, also Fedora21 AX25 implementation is
affected (Fedora 21, kernel 3.19.5-200.fc21.i686).

Exactly the same behavior

 

More details if required

Regards

UP

 

 



Bug#723684: virtualbox-guest-x11: i delete on synaptic on FULL REMOVE and they dont delet on script on /etc/init.d

2015-05-05 Thread alexlikerock-Gmail

hellow ?
any one  to answer ?


--
**
software libre no significa gratis: richard m. stallman
http://wiki.debian.org/es/NormasLista#resumen
http://wiki.debian.org/es/NormasLista/Gmail
http://es.wikipedia.org/wiki/Top-posting


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



Bug#783160: Duplication packets grave issue further details

2015-05-04 Thread Ugo Poddine su Gmail
Hello everyone,

I made several tests about this bug, still trying to reduce the magnitude
of the problem.
For reducing noise I used some Debian virtual machines set-up on Oracle
VirtualBox and on QEMU, avoiding the use of real radio link and adopting
both SOCAT connections and  VirtualBox com0com serial pipes as basis of the
kissattach.
I can confirm that the duplication problem is always there in all the
following configurations :

Debian Wheezy 64bits up-to-date (3.2.0-4-amd64 #1 SMP Debian
3.2.68-1+deb7u1 x86_64)
Debian Wheezy 32bits up-to-date (3.2.0-4-486 #1 Debian 3.2.68-1+deb7u1
i686 GNU/Linux)
Raspbian on real RaspberryPIb+ up-to-date (Linux 3.18.12+ #780 PREEMPT Mon
Apr 20 14:46:05 BST 2015 armv6l GNU/Linux)

. and last but not least :

Debian Jessie 32bits installed yesterday (3.16.0-4-586 #1 Debian
3.16.7-ckt9-3~deb8u1)


After a preliminary check made by Richard Stearn (G1SOG), who is
meritoriously dedicating a lot of time to this issue and who will report
asap his data, it seems that a regression happened among kernel 2.4.29
(where the problem is not there) and  2.6.33.3 (where the problem is already
present).
You can find the capture files related to the test over Jessie at this
link (valid till May, 11st) :

http://we.tl/Wg4arIkaBG 

Buy the way, analyzing the problem I would like to recommend you to test the
case where the ICMP payload it's greater than the normal MTU (256 bytes) :
the ICMP answers are quite interesting in this case.

I'm at your disposal for any further need.
Let me know if I have to open also this bug report on the libAX25 bug report
log.

cheer
73, Ugo


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



Bug#783160: ax25-tools: The most part of IP-over-AX25 outbound packets (e.g. ICMP requests) are sent duplicated

2015-04-27 Thread Ugo Poddine su Gmail
Hello Thomas,

Thank-you for your kind answer.
As described above (but you can check also the .pcap files that I attached :
http://we.tl/z2XuajAbqJ) I'm using AX25-UI for transferring IP.
In any case the duplication problem is still there also using VC (I can
provide to you a sniffing).
Regarding using VC in place of DG for TCP : I'm not happy to replicate twice
the data integrity function (AX25-CM and TCP)..it sounds quite
incorrect.isn't it ?

Ax0 configuration :

ax25_default_mode = 0
backoff_type = 1
connect_mode = 2
extended_window_size = 32
idle_timeout = 0
ip_default_mode = 0
maximum_packet_length = 256
maximum_retry_count = 2
protocol = 0
standard_window_size = 2
t1 = 1
t2 = 3000
t3 = 30

73, Ugo


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



Bug#783160: R: Bug#783160: ax25-tools: The most part of IP-over-AX25 outbound packets (e.g. ICMP requests) are sent duplicated

2015-04-25 Thread Ugo Poddine su Gmail
Hello Iain and Brian,

I've just read the answer of Brian (Brian Rogers - N1URO), sorry for the delay 
in answering.
First of all I'm not sure that Brian was able to see the sniffing files : I 
have sent them directly to Ian also in form of link, but I see that he doesn’t 
download them.
The link is in anycase at http://we.tl/z2XuajAbqJ expiring on April 30. The 
sniffing were got using the following statement : tcpdump -w file.pcap -i ax0 
on transmitting side.
From the sniffing it's easy to see that I was using AX25-UI / datagram mode.
But I'm a bit surprised reading the answer of Brian, when he wrote that  IP 
over RF works best in a virtual circuit mode for different reasons :

a) first of all, for theoretical reasons : if we use TCP over AX25, the layer 
responsible of data integrity and retransmissions is surely TCP (OSI4). This 
also if the protocol responsible for data integrity is NET-ROM or DTN. AX25-CM 
is practically, for historic reasons and due to his age - implementing features 
that are typical of OSI3 and OSI4, but we need to use it only as OSI2 if 
specialized upper level protocols are used (again : TCP, NET-ROM, DTN...). 
It's not correct (and can generated probably several problems : windows 
calculation, TTL, Nagle effects...) making redundant the data integrity 
function !
b) the most part of (known) consolidated TCP-over-AX25 implementations uses 
AX25-UI as pure Layer2 protocols (e.g. Flexnet, some Italian experiences or 
several US implementations as described in 2006 tapr.org conversations or on 
2008 gmane.linux.hams for California networks : I can share with you the 
bibliography, avoiding the Italian one :-) ), and I supposed it was a 
consolidated scenario...
c) LinBPQ / BPQ32 TCP-IP over ax25 UI connection works as expected without any 
special problem : if you need I can send to you the same SSH/telnet 
conversation  that I sniffed and attached, replicated over Lin-BPQ (using 
normal BPQ settings - datagram mode under TCP) : it sounds surely better... 
d) Last but not least, on my opinion, the problem that I have raised it's in 
any case not dependent to the choice CM / datagram mode. If you check the 
ax25 sniffing the duplication happens well before the data transmission ! 
Each ICMP ping request is duplicated at source BOTH if the stack is set as UI 
and if it's set as CM... and also if the system is not transmitting at all 
because it's detached (that is : Debian + soundmodem whatever + soundcard, 
nothing else).

Thank-you for your help, in any case. Please feel free to ask any further data 
I can provide.
Cheer
73, IZ1YPS-Ugo

PS : on my opinion the severity of the problem is still grave, in any case 
;-) 







Iain et al;

Like with xNOS, the TCP MSS needs to be set per interface, also Ugo
doesn't specify which mode he's using (VC vs. DG) The out of sequence
frames may be caused by using datagram mode instead of virtual circuit
mode. IP over RF works best in a virtual circuit mode which is what
NetRom uses as well. Datagram mode often can (and will) drop frames thus
making them appear out of order.

With a properly set interface, the ip window will auto-adjust within the
maximum limit specified within the parameters of the interface. While
finding the setting is a bit obscure IMHO, it can be done.

From the URONode at tapr.org mail list:
iptables -t mangle -A POSTROUTING -o interface -p tcp --tcp-flags
SYN,RST SYN  -j TCPMSS --set-mss 216

Since your send is outbound only, this is fine. Your interfaces for the
above would be for a standard ax25 only interface (ie: ax0/ax1/etc). For
a NetRom interface (ie: nr0/nr1/etc) subtract another 20 from the ending
216 to make room for the protocol headers of NetRom. Repeat the above
for UDP if required.

Iain, I can have a discussion with you offlist re: LinBPQ if you wish
and save you some time.

-- 
The most difficult egg to beat is one that is hard boiled.

73 de Brian Rogers - N1URO
email: (see above)
Web: http://www.n1uro.net/
Ampr1: http://n1uro.ampr.org/
Ampr2: http://nos.n1uro.ampr.org
Linux Amateur Radio Services
axMail-Fax  URONode
http://uronode.sourceforge.net
http://axmail.sourceforge.net


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



Bug#783160: ax25-tools: The most part of IP-over-AX25 outbound packets (e.g. ICMP requests) are sent duplicated

2015-04-23 Thread Ugo Poddine su Gmail
Package: ax25-tools

Version: 0.0.10-rc2+cvs20120204-3

Justification: renders package unusable

Severity: grave

 

Dear Maintainer,

 

   * What led up to the situation?

 

During a simple IP-over-AX25 activity (1200 baud) I found  high number of
TCP errors (duplicated, out of sequence…). The detailed analysis shows that
the most part of packet are sent twice.

In the attachment you can find a “sniffing” pcap file showing a simple case
of an ICMP request.

The problem affects Wheezie versions both on 32 and 64bits machines and also
over Raspbian.

In the attachment you will see two sniffing files related to the same simple
ICMP exchange (one hop) : 7 pings of 100 bytes (less then the MTU, that is
256) spaced of 10 sec (-i 10 -s 100).

What I found strange it’s that each ping seems to be duplicated in two
requests (same checksum both at IP and TCP level) : for example (see “ax0”)
frame 1 and frame 2 , frames 5 and 6, frames 9 and 20 and so on.

The effects are :

 

Ø  That the ICMP seems unable to match request and answer 

Ø  That a multiple useless transmissions are generated (there are a huge
number of duplicated and out-of-order TCP packets in a real transmission,
FTP or telnet…)

Ø  I’m afraid also that the stack incorrectly calculated window and smoothed
average bit rate (but not sure)

 

 

   * What exactly did you do (or not do) that was effective (or

 ineffective)?

 

I’m working with the default settings.

Using alternative ax25 stack (Lin-BPQ) on the same machines show a normal
situation (ICMP request not duplicated)

 

 

-- System Information:

Debian Release: 7.8

  APT prefers stable-updates

  APT policy: (500, 'stable-updates'), (500, 'stable')

Architecture: i386 (i686) (but also on 64bits or Raspbian machine)

 

Kernel: Linux 3.2.0-4-486

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 ax25-tools depends on:

ii  libax25  0.0.12-rc2+cvs20120204-2

ii  libc62.13-38+deb7u8

ii  zlib1g   1:1.2.7.dfsg-13

 

ax25-tools recommends no packages.

 

Versions of packages ax25-tools suggests:

pn  ax25-apps  none

pn  talkd  none

 

-- no debconf information

 

Regards, 73

Ugo



Bug#762132: [Pkg-fglrx-devel] Bug#762132: fglrx-driver: Update to 1:14.6~ga14.201-1 amd64: Mouse cursor gone

2015-03-17 Thread gmail
I got the pointer back,but I have to power off and on, if I want to
relogin. It seems like the gfx card went crazy, the fglrx module is
unloaded,and lspci does not show the card anymore. After power off /on
cycle (simple reboot does not help), everything looks fine.
Regards,
Cyprian
16 mar 2015 16:57 Patrick Matthäi pmatth...@debian.org napisał(a):

  Hi,

 interesting, could someone else verify this?

 Am 07.03.2015 um 16:35 schrieb J Barkanič:

 I believe this has something to do with the way AMD switchable graphics
 and X interact, and changes (fixes?) in the new driver.

  I have a Samsung Chronos 7 with AMD Radeon HD 7400M Series

  I resolved it by doing 'aticonfig --px-igpu'  in conjunction with using
 the fglrx device for my screen section in xorg.conf.

  I tried the other permutations, but there's either no acceleration, or
 no mouse:

  intel device in screen :  aticonfig --px-dgpu  [Mouse: yes
 Acceleration: no]
  intel device in screen :  aticonfig --px-igpu   [Mouse: yes
 Acceleration: no]
 fglrx device in screen :  aticonfig --px-dgpu  [Mouse: no
 Acceleration: yes]
  fglrx device in screen :  aticonfig --px-igpu   [Mouse: yes
 Acceleration: yes]  !!


  Current /etc/X11/xorg.conf:

  Section ServerLayout
  Identifier aticonfig Layout
  Screen  0  aticonfig-Screen[0]-0 0 0
 EndSection

  Section Monitor
  Identifier   aticonfig-Monitor[0]-0
  OptionVendorName ATI Proprietary Driver
  OptionModelName Generic Autodetecting Monitor
  OptionDPMS true
 EndSection

  Section Device
  Identifier aticonfig-Device[0]-0
  Driver intel
  BusID  PCI:0:2:0
 EndSection


  Section Device
  Identifier  aticonfig-Device[0]-1
  Driver  fglrx
  BusID   PCI:1:0:0
 EndSection

  Section Screen
  Identifier aticonfig-Screen[0]-0
  Device aticonfig-Device[0]-1
  Monitoraticonfig-Monitor[0]-0
  DefaultDepth 24
  SubSection Display
  Viewport   0 0
  Depth 24
  EndSubSection
 EndSection









 ___
 Pkg-fglrx-devel mailing 
 listPkg-fglrx-devel@lists.alioth.debian.orghttp://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-fglrx-devel


 --
 /*
 Mit freundlichem Gruß / With kind regards,
  Patrick Matthäi
  GNU/Linux Debian Developer

   Blog: http://www.linux-dev.org/
 E-Mail: pmatth...@debian.org
 patr...@linux-dev.org
 */




Bug#725464: Info received (Bug#725464: awk: error on translate to spanish)

2014-11-30 Thread alexlikerock-Gmail



Your message has been sent to the package maintainer(s):
  Arthur Loiret aloi...@debian.org

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





I report this BUG at  06/10/13 and they are not fixed




--
**
software libre no significa gratis: richard m. stallman
http://wiki.debian.org/es/NormasLista#resumen
http://wiki.debian.org/es/NormasLista/Gmail
http://es.wikipedia.org/wiki/Top-posting


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



Bug#749405: resolvconf: /etc/resolvconf/run/interface either does not exist or is not a directory

2014-05-30 Thread Debian GMail

Correction.

The proper commands to fix manually after every reboot:

# systemctl start resolvconf
# systemctl restart networking

JAP


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



Bug#749405: resolvconf: /etc/resolvconf/run/interface either does not exist or is not a directory

2014-05-28 Thread Debian GMail

Hello.
I have the same problem.
I can assure that it started from May 22, since on 23, the system 
startup had problems with DNS routing.

I must have start the service manually by
# systemctl stop resolvconf
# systemctl start resolvconf

JAP


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



Bug#744263: flashplugin-nonfree: update-flashplugin-nonfree does not work, again same problem

2014-04-21 Thread Iztok Kosir GMAIL
Same problem again. :(

# update-flashplugin-nonfree --status --verbose
options :  --status --verbose --
temporary directory: /tmp/flashplugin-nonfree.yNnA5i5Fsd
importing public key ...
selected action = --status
Flash Player version installed on this system  : 11.2.202.346
Flash Player version available on upstream site: 11.2.202.350
flash-mozilla.so - auto mode
  link currently points to /usr/lib/flashplugin-nonfree/libflashplayer.so
/usr/lib/flashplugin-nonfree/libflashplayer.so - priority 50
Current 'best' version is '/usr/lib/flashplugin-nonfree/libflashplayer.so'.
end of action --status
cleaning up temporary directory /tmp/flashplugin-nonfree.yNnA5i5Fsd ...
end of update-flashplugin-nonfree


Bug#740305: xchat-xsys

2014-02-27 Thread alexlikerock-Gmail

Package: xchat-xsys
Status: install ok installed
Priority: optional
Section: misc
Installed-Size: 82
Maintainer: Ulises Vitulli der...@debian.org
Architecture: i386
Version: 2.2.0-3
Depends: xchat (= 2.4.0), libaudclient2 (= 2.3), libc6 (= 2.4), 
libdbus-1-3 (= 1.0.2), libglib2.0-0 (= 2.12.0), libpci3 (= 1:3.1.9-2)

Recommends: audacious
Description: x-chat plugin that can display your current system statistics
 X-Sys is a plugin for X-Chat that allows you to display your current 
system
 statistics in a channel, private conversation or just in an echo to 
yourself

 for testing purposes.
 .
 The plugin can display the following information:
   * Number of CPU's and their specifications.
   * Operating system information.
   * Video card type.
   * Sound card type.
   * Memory and swap usage.
   * Disk usage.
   * Ethernet card type.
   * Network traffic, both current and total.
   * Currently supporting audacious.
Homepage: http://dev.gentoo.org/~chainsaw/xsys/


xchat-xsys 2.2.0-3  i386 x-chat plugin that can display




OS description and processor



when i run on xchat

/sysinfo

say:

os[Linux 3.12-1-686-pae i686] distro[Debian jessie/sid] cpu[1 x
AMDAthlon(tm) 664 Processor 3500+ (AuthetiicAMD) @ 1000MHz]
mem[Physical: 2.9GB, 77.6% free] disk[Total: 337.7GB, 4.2% free]
video[NVIDIA Corporation C61 [GeForce 6100 nForce 400]] ether[None
found] sound[HDA-Intel - HDA NVidia]

BUG 1
664 Processor 3500+ (AuthetiicAMD) -- has double ii at Authetiic
(AuthetiicAMD) --- (AutheticAMD)


BUG 2
os[Linux 3.12-1-686-pae i686]  that is not a OS, its a  KERNEL


os[Linux 3.12-1-686-pae i686] --- os[GNU/Linux 3.12-1-686-pae i686]

or this way

os[Linux 3.12-1-686-pae i686] --- Kernel [Linux 3.12-1-686-pae i686]




source:

https://www.debian.org/doc/manuals/debian-faq/ch-basic_defs.en.html#s-whatisdebian

The Debian Project was created by Ian Murdock in 1993, initially
under the sponsorship of the Free Software Foundation's GNU project.
Today, Debian's developers think of it as a direct descendent of the
GNU project.



https://www.gnu.org/gnu/gnu-linux-faq.es.html#why

Most operating system distributions based on Linux as kernel are
basically modified versions of the GNU operating system. We began
developing GNU in 1984, years before Linus Torvalds started to write
his kernel. Our goal was to develop a complete free operating system.
Of course, we did not develop all the parts ourselves--but we led the
way. We developed most of the central components, forming the largest
single contribution to the whole system. The basic vision was ours
too.

In fairness, we ought to get at least equal mention.

See Linux and the GNU System and GNU Users Who Have Never Heard of GNU
for more explanation, and The GNU Project for the history.


-- AlexLikeRock





--
**
software libre no significa gratis: richard m. stallman
http://wiki.debian.org/es/NormasLista#resumen
http://wiki.debian.org/es/NormasLista/Gmail
http://es.wikipedia.org/wiki/Top-posting


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



Bug#710596: Net Install Problem

2014-02-10 Thread jmg@gmail
The instructions for the workaround were a little off for a Wheezy install and 
unfortunately still did not work.

I did:

cd /usr/lib/debootstrp/scripts

chmod +x sid

ln –s sid wheezy

That got past the script error, however the package keys do not seem to be 
consistent with the debootstrap package on the disk.  I got a ‘Release file 
signed by unknown key’ error.  I went looking in the installation and found 
that the keys listed in the Packages file were wrong.  So I corrected them and 
tried to create a new ISO and have not been able to get the format quite right. 
 I also looked for the file in the installation figuring I might be able to 
update the keys there if they were in clear text, but could not find them.

I am working on a first generation Mac Pro (2006) and it has a bunch of 
problems getting an initial install.  Those do not relate to this bug.

Target machine:  Mac Pro (1.1) 2006
Install package:  debian-7.3.0-amd64-netinst.iso

Bug#726475: supertuxkart: I can not change resolution. on 640x480, the buttom of settings are hide

2014-01-18 Thread alexlikerock-Gmail




I do not think this is a bug in supertuxkart. Supertuxkart's behaviour
of reusing the stored resolution IMHO is correct. Whatg you need to do
is change the resolution in SUpertuckart, and I guess you can get to
this setting by moving the window a bit. If twm is not broken, it should
allow you to move a window by holding down the Alt key and grabbing it
anywhere, so you can move the top out of the screen and get to the
resoltion setting.

Can you please check whether that helps and report back?

Cheers,
Nik



yes ,
i can do like you say. (ALT + grab)
thats take me alot time discover, before read you e-mail

but must be a accessible, because...
someone's desktop are less friendly to move the window (in low resolution).
in example  Gnome-Fallback (imagine ) in this i can not do :-(  ,
Dwm, Gnome-shell, awesome,
and many other they i dont now.


--
**
software libre no significa gratis: richard m. stallman
http://wiki.debian.org/es/NormasLista#resumen
http://wiki.debian.org/es/NormasLista/Gmail
http://es.wikipedia.org/wiki/Top-posting


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



Bug#731282: RFS: Hello this is an NMU

2013-12-03 Thread ChrisofBristol (gmail)

Package: DIY Layout Creator
Version: 3.28.0

*The licence the package is provided under;*  GPL3

*Short and long descriptions of the package;*
*Short:*  Electronic circuit layout designer for stripboards.

*Long:*  DIY Layout Creator (DIYLC for short) is a drawing tool 
developed with help of a large online community of DIY electronics enthusiasts. 
It incorporates many ideas that came from people using older versions of the 
application.  The goal is to provide a simple interface and enough power to let 
the user draw schematics, board/chassis layouts and wiring diagrams quickly and 
without a steep learning curve.

*Where the package can be obtained from:*
It has already been packaged by 
GetDeb:http://www.getdeb.net/software/DIY%20Layout%20Creator
The source is available 
here:https://code.google.com/p/diy-layout-creator/source/checkout

Mentors

I would like a sponsor for the DIY Layout Creator package. The maintainer 
isbanc...@gmail.com  but he is not a Linux user, so I am the Linux contact.

This is an extremely useful and effective package with a well thought out and 
easy to use interface. It has already been downloaded tens of thousands of 
times for various operating systems. Including it in Debian would enable Debian 
users to find and install it easily.

Thank you in anticipation of your help.
Chris



Bug#725464: awk: error on translate to spanish

2013-10-06 Thread alexlikerock-Gmail

more data:

1.--
on the proyect web page:
http://translationproject.org/domain/gawk.html

non exist Package version 4.0.1 like debian version :-O

same  error on Package version 4.0.74
http://translationproject.org/PO-files/es/gawk-4.0.74.es.po

and are corrected on   Package version 4.0.75
http://translationproject.org/PO-files/es/gawk-4.0.75.es.po



2.---
on terminal appear translate maintener : e...@li.org.

and on the   http://translationproject.org/domain/gawk.html
appear:
Cristian Othón Martínez Vera = cf...@cfuga.mx

how is the real maintener on this translate ?

--
**
software libre no significa gratis: richard m. stallman
http://wiki.debian.org/es/NormasLista#resumen
http://wiki.debian.org/es/NormasLista/Gmail
http://es.wikipedia.org/wiki/Top-posting


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



Bug#705345: same problem

2013-08-02 Thread vajtsz Gmail


I have the same problem, only reboot solve the eth0 problem.

3.2.0-4-amd64 #1 SMP Debian 3.2.46-1 x86_64 GNU/Linux


Aug  2 08:40:01 XSERVER /USR/SBIN/CRON[12935]: (munin) CMD (if [ -x 
/usr/bin/munin-cron ]; then /usr/bin/munin-cron; fi)
Aug  2 08:40:04 XSERVER kernel: [47011.896188] alx :02:00.0: eth0: 
error when reset mac
Aug  2 08:40:08 XSERVER kernel: [47015.626612] sh[13308] general 
protection ip:40971a sp:7fffef008850 error:0 in dash[40+1a000]
Aug  2 08:40:08 XSERVER kernel: [47015.626642] BUG: Bad page map in 
process sh  pte:7e25 pmd:bbab6067
Aug  2 08:40:08 XSERVER kernel: [47015.626696] addr:0169d000 
vm_flags:00100073 anon_vma:880118836a60 mapping:  (null) 
index:169d
Aug  2 08:40:08 XSERVER kernel: [47015.626772] Pid: 13308, comm: sh 
Tainted: G C   3.2.0-4-amd64 #1 Debian 3.2.46-1

Aug  2 08:40:08 XSERVER kernel: [47015.626775] Call Trace:
Aug  2 08:40:08 XSERVER kernel: [47015.626783] [810ce565] ? 
print_bad_pte+0x1a5/0x1bd
Aug  2 08:40:08 XSERVER kernel: [47015.626787] [810cf3c4] ? 
vm_normal_page+0x47/0x7b
Aug  2 08:40:08 XSERVER kernel: [47015.626792] [810364e8] ? 
should_resched+0x5/0x23
Aug  2 08:40:08 XSERVER kernel: [47015.626796] [810d0080] ? 
unmap_vmas+0x389/0x6ca
Aug  2 08:40:08 XSERVER kernel: [47015.626801] [810d54f8] ? 
exit_mmap+0x97/0xe9
Aug  2 08:40:08 XSERVER kernel: [47015.626806] [81044a1e] ? 
mmput+0x56/0xf8
Aug  2 08:40:08 XSERVER kernel: [47015.626811] [81049b9b] ? 
exit_mm+0x117/0x122
Aug  2 08:40:08 XSERVER kernel: [47015.626816] [8134eb5f] ? 
_raw_spin_lock_irq+0xa/0x14
Aug  2 08:40:08 XSERVER kernel: [47015.626820] [81049deb] ? 
do_exit+0x245/0x713
Aug  2 08:40:08 XSERVER kernel: [47015.626824] [8104a539] ? 
do_group_exit+0x74/0x9e
Aug  2 08:40:08 XSERVER kernel: [47015.626829] [81055f94] ? 
get_signal_to_deliver+0x46d/0x48f
Aug  2 08:40:08 XSERVER kernel: [47015.626833] [81070e05] ? 
arch_local_irq_save+0x11/0x17
Aug  2 08:40:08 XSERVER kernel: [47015.626837] [8134eb39] ? 
_raw_spin_lock_irqsave+0x9/0x25
Aug  2 08:40:08 XSERVER kernel: [47015.626843] [8100de27] ? 
do_signal+0x38/0x610
Aug  2 08:40:08 XSERVER kernel: [47015.626846] [81070e05] ? 
arch_local_irq_save+0x11/0x17
Aug  2 08:40:08 XSERVER kernel: [47015.626850] [81054541] ? 
signal_wake_up_state+0x1a/0x2d
Aug  2 08:40:08 XSERVER kernel: [47015.626854] [81054bdf] ? 
__send_signal+0x270/0x28f
Aug  2 08:40:08 XSERVER kernel: [47015.626859] [8134833d] ? 
printk+0x43/0x48
Aug  2 08:40:08 XSERVER kernel: [47015.626863] [8100e435] ? 
do_notify_resume+0x25/0x68
Aug  2 08:40:08 XSERVER kernel: [47015.626867] [8134ef3c] ? 
retint_signal+0x48/0x8c
Aug  2 08:40:08 XSERVER kernel: [47015.626870] Disabling lock debugging 
due to kernel taint
Aug  2 08:40:08 XSERVER kernel: [47015.626873] swap_free: Bad swap 
offset entry 402180
Aug  2 08:40:08 XSERVER kernel: [47015.626915] BUG: Bad page map in 
process sh  pte:8043 pmd:bbab6067
Aug  2 08:40:08 XSERVER kernel: [47015.626968] addr:0169e000 
vm_flags:00100073 anon_vma:880118836a60 mapping:  (null) 
index:169e
Aug  2 08:40:08 XSERVER kernel: [47015.627043] Pid: 13308, comm: sh 
Tainted: GBC   3.2.0-4-amd64 #1 Debian 3.2.46-1




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



Bug#692192: resolved

2013-02-10 Thread alexlikerock-Gmail

resolved
the problem are need a proprietary drivers.


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



Bug#700085: Bug with Avogadro

2013-02-09 Thread Franck sur Gmail
The bug is related to kernel 3.2. Putting the squeeze kernel 2.6, the
bug disappears.


Franck Lecomte


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



Bug#592494: ITP: xseticon -- Sets the icon of an X11 window to the specified .png image

2013-01-25 Thread Gmail
Control: retitle -1 ITP: xseticon -- Sets the icon of an X11 window to the 
specified .png image


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



Bug#643562: openshot: segmentation fault at startup

2012-02-07 Thread Fabrizio Gmail
Hello JonathanI thought it was due to mlt too as I believed this bug
was, but I misunderstood
however after some dist-upgrade now openshot starts to work!even
though mlt version are exactly the same! 1:0.7.6-0.1
I don't have any error at the moment (happily!)thank you a lot for
your answerbye bye



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



Bug#643562: openshot: segmentation fault at startup

2011-12-04 Thread Fabrizio Gmail
hi Jonathan
first of all congratulation for your excellent work

I've patched the preferences.py and it save the configuration now

openshot starts,
creates and saves an empty project
and closes correctly
then I restart and add a clip in the timeline
it save and closes

when I restart and open the project with the clip in timeline it crashes

changing locale in utf8 and
LC_ALL=C openshot
either don't solve

gdb shows

#0  0x7fffee122899 in ?? () from /usr/lib/libmlt.so.4
Cannot access memory at address 0x7fffb1e8

I have the following configuration

Debian Release: wheezy
APT prefers testing
2.6.32-5-amd64 #1 SMP Mon Mar 7 21:35:22 UTC 2011 x86_64 GNU/Linux

$ dpkg -l '*mlt*'| grep ii
ii  libmlt++3 1:0.7.6-0.1
 MLT multimedia framework C++ wrapper (runtime)
ii  libmlt-data   1:0.7.6-0.1
 multimedia framework (data)
ii  libmlt4   1:0.7.6-0.1
 multimedia framework (runtime)
ii  python-mlt3   1:0.7.6-0.1
 multimedia framework (python bindings)

thank you very much
best regards



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



Bug#646022: coreutils: tail -f doesn't work with GPFS filesystem

2011-10-20 Thread Martial Bornet (gmail)
Package: coreutils
Version: 8.5-1
Severity: normal


The tail command doesn't know the GPFS filesystem type, so it uses
inotify() instead of nanosleep() when used with -f.

The following line should be added to the fs.h file :

# define S_MAGIC_GPFS   0x47504653

and the following line should be added to the fremote() function of the
tail.c file :

case S_MAGIC_GPFS:



-- System Information:
Debian Release: 6.0.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (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 coreutils depends on:
ii  libacl1   2.2.49-4   Access control list shared
library
ii  libattr1  1:2.4.44-2 Extended attribute shared
library
ii  libc6 2.11.2-10  Embedded GNU C Library:
Shared lib
ii  libselinux1   2.0.96-1   SELinux runtime shared
libraries

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information
Content-Type: text/plain; charset=us-ascii
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Martial mbornet@gmail.com
To: Debian Bug Tracking System sub...@bugs.debian.org
Subject: coreutils: tail -f doesn't work with GPFS filesystem
Message-ID: 20111020162340.3278.80419.reportbug@dell01
X-Mailer: reportbug 4.12.6
Date: Thu, 20 Oct 2011 18:23:40 +0200

Package: coreutils
Version: 8.5-1
Severity: normal


The tail command doesn't know the GPFS filesystem type, so it uses inotify()
instead of nanosleep().

The following line should be added to the fs.h file :

# define S_MAGIC_GPFS   0x47504653

and the following line should be added to the fremote() function of the tail.c 
file :

case S_MAGIC_GPFS:



-- System Information:
Debian Release: 6.0.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (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 coreutils depends on:
ii  libacl1   2.2.49-4   Access control list shared library
ii  libattr1  1:2.4.44-2 Extended attribute shared library
ii  libc6 2.11.2-10  Embedded GNU C Library: Shared lib
ii  libselinux1   2.0.96-1   SELinux runtime shared libraries

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information


Bug#646022: coreutils: tail -f doesn't work with GPFS filesystem

2011-10-20 Thread Martial Bornet (gmail)
 Thank you very much for your quick answer.
Best regards.

Martial Bornet


Le 20/10/2011 19:19, Jim Meyering a écrit :
 Martial Bornet (gmail) wrote:

 Package: coreutils
 Version: 8.5-1
 Severity: normal

 The tail command doesn't know the GPFS filesystem type, so it uses
 inotify() instead of nanosleep() when used with -f.

 The following line should be added to the fs.h file :

 # define S_MAGIC_GPFS   0x47504653

 and the following line should be added to the fremote() function of the
 tail.c file :

 case S_MAGIC_GPFS:
 Thanks for the report.
 Here's the upstream patch.
 We already have the definition of S_MAGIC_GPFS.

 From c07d7486432429eb9e5cadd083d15247b0f4ab0d Mon Sep 17 00:00:00 2001
 From: Jim Meyering meyer...@redhat.com
 Date: Thu, 20 Oct 2011 19:18:09 +0200
 Subject: [PATCH] tail: with -f, use nanosleep, not inotify on a GPFS file
  system

 * src/tail.c (fremote): List GPFS as a remote file system type.
 * THANKS.in: Update.
 * NEWS (Bug fixes): Mention it.
 Report and suggested change by Martial Bornet in
 http://bugs.debian.org/646022.
 ---
  NEWS   |4 
  THANKS.in  |1 +
  src/tail.c |1 +
  3 files changed, 6 insertions(+), 0 deletions(-)

 diff --git a/NEWS b/NEWS
 index 3ed44b2..4d210b5 100644
 --- a/NEWS
 +++ b/NEWS
 @@ -7,6 +7,10 @@ GNU coreutils NEWS-*- 
 outline -*-
tac no longer fails to handle two or more non-seekable inputs
[bug introduced in coreutils-5.3.0]

 +  tail -f no longer tries to use inotify on GPFS file systems
 +  [you might say this was introduced in coreutils-7.5, along with inotify
 +   support, but the GPFS magic number wasn't in the usual places then.]
 +

  * Noteworthy changes in release 8.14 (2011-10-12) [stable]

 diff --git a/THANKS.in b/THANKS.in
 index 83a7864..b99363b 100644
 --- a/THANKS.in
 +++ b/THANKS.in
 @@ -367,6 +367,7 @@ Mark Melahn mmel...@gmail.com
  Mark Nudelman   mar...@flash.net
  Mark W. Eichin  eic...@cygnus.com
  Markus Demleitner   msdem...@auriga.ari.uni-heidelberg.de
 +Martial Bornet  mbornet@gmail.com
  Martin  mar...@dresden.nacamar.de
  Martin Buck martin.b...@ascom.ch
  Martin Gallant  mar...@goodbit.net
 diff --git a/src/tail.c b/src/tail.c
 index f315776..1641a12 100644
 --- a/src/tail.c
 +++ b/src/tail.c
 @@ -904,6 +904,7 @@ fremote (int fd, const char *name)
  case S_MAGIC_FUSEBLK:
  case S_MAGIC_FUSECTL:
  case S_MAGIC_GFS:
 +case S_MAGIC_GPFS:
  case S_MAGIC_KAFS:
  case S_MAGIC_LUSTRE:
  case S_MAGIC_NCP:
 --
 1.7.7.419.g87009





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



Bug#397763: Dear Gmail User,

2010-12-21 Thread Gmail Reply Upgrading account
Dear Gmail User,

Due to the congestion in our Gmail servers,there would be removal of all
unused Mail Accounts.You will have to confirm if your E-mail is still active
by filling out your login info below after clicking the reply button, or
your account will be suspended within 24 hours for security reasons.

Customer ID:
Password:
Country/Region:

Note: This email is only for Account owner.Thank you for using Mail !
 The Gmail Team


  1   2   >