Bug#1069719: [ITP] wireviz - Easily document cables and wiring harnesses.

[Angel]

Package: wnpp
Severity: wishlist

Hello, I am looking to pacakge WireViz for debian.
Upstream source: https://github.com/wireviz/WireViz
License: GPLv3

WireViz is a tool for easily documenting cables, wiring harnesses and
connector pinouts. It takes plain text, YAML-formatted files as input
and produces beautiful graphical output (SVG, PNG, ...) thanks to
GraphViz. It handles automatic BOM (Bill of Materials) creation and
has a lot of extra features.

Regards,
Angel Yankov

Bug#1065831: document package specifiers for `upgrade`

[Miguel Angel Rojas]

Hi all,

>>  No. Without a package as an argument it won't.

Thanks! You're right. Let me write it down here again:

   - "apt upgrade" (no argument) will never remove a package, only upgrade
   or install
   - "apt upgrade pkg_name" will remove, upgrade or install the required
   package to satisfy its dependencies.
   - "apt upgrade foo- bar+": advanced option that can be used to
   specifically removed or install packages.

>> Julian provided an explanation in #74,
20240312113620.ga1944...@debian.org

I can't access this link..

>> I'm not a Debian developer, never have been. Just someone who submitted
a patch or two.

And your comments have been really valuable in figuring out what's going
on! Again, my confusion was because this was the first time I reported a
bug AND several people jumped in the conversation! It is not usually the
case ;)

Regards

Bug#1065831: document package specifiers for `upgrade`

[Miguel Angel Rojas]

Hi all,

>> (modifiers btw is not a good word. I guess it was never documented so
far partly as this is a rather advanced feature and mainly because  naming
things is hard)

yes, we brought it up in our conversation but I agree it was not directly
related to the subject as it was an apt advanced option. But it was good
because we were able to compare different situations (to spice things up).
We even talked about "apt-get" and "aptitude" but I understand they are
different commands and the purpose was not to compare behaviours among
different tools.

>> Well, does it really matter who is and who isn't?

No, it doesn't as long as they have the right information ;)

Of course, the more people involved in the issue, the better perspective we
have on the problem. But it is important to know how apt is
*currently* behaving to avoid misunderstanding and wrong assumptions (even
from my side as well). We discovered that it is a documentation bug but my
initial premise when I opened the bug was that the resolver wasn't working
properly. With the right information, we usuallly get faster to the
solution. Thank you all, guys!

>> Nobody is born an APT developer, they are chosen based on their patch
offerings!
;)

Bug#1065831: document package specifiers for `upgrade`

[Miguel Angel Rojas]

Hi there,

> If "apt upgrade" is saying that it removes packages, that is a bug, yes.

@david: it is not a bug, apparently.

To put everything in a nutshell:

   - "apt upgrade" can remove packages
   - "apt upgrade" accepts specific packages to be upgraded

Therefore, this behaviour is expected and documentation needs to be
modified.

In the meantime, while the documentation is modified, can some developer
provide some explanation to the current "apt upgrade" behaviour? (*)

Thanks

(*) I'm a bit confused because I don't know which of the people involved in
this bug are actually a developer of the apt package ;)

Bug#1065831: apt upgrade : it removes packages when it shouldn't.

[Miguel Angel Rojas]

Control: retitle -1 apt upgrade : it removes packages when it shouldn't.

Bug#1065831: apt tries to uninstall kde & plasma (full-upgrade)

[Miguel Angel Rojas]

Control: retitle -1 apt upgrade : it removes packages when it
shouldn't.

The case you mentioned is a tricky one, yes: *apt upgrade foo+ bar-* (I
really don't know how apt handles it internally but having this option is
very useful. Of course, I wouldn't remove it).

I think it makes a lot of sense for "apt upgrade" to allow packages as
arguments. There should be a possibility to upgrade only a set of packages
and it comes in handy in some situations (i.e.: t64 upgrade). "apt upgrade"
also doesn't mark upgraded packages as manually installed (as expected).
But "apt install" does mark them as manually installed (as expected too).

Therefore, I see 2 options here:

a) Change apt documentation to include the current behaviour. But if so, it
should *NOT* remove any packages.
b) Remove the possibility to specify packages to upgrade as arguments
(which I don't really recommend for the reasons stated above).

Anyway, I think some clarification is needed from the developers to shed
some light on this.

Regards

On Tue, Mar 12, 2024 at 3:12 AM Wesley Schwengle 
wrote:

> On Mon, Mar 11, 2024 at 11:32:24PM +0100, Miguel Angel Rojas wrote:
> > > I see. It looks like `apt upgrade ' behaves as `apt install
> > > '. Which (to me) is unexpected behaviour, as the man page is
> > quite
> > >clear on its behaviour (man 8 apt-get):
> >
> > Well, clearly it shouldn’t. To begin with, “apt install” should mark a
> > package as manual installed while “apt upgrade” shouldn’t (my
> assumption).
> > And you’re right that “apt install” can remove a package if needed to
> > satisfy dependencies.
> >
> > On top of that, documentation clearly states that “apt upgrade” should
> not
> > remove any package, but it does when you specify an individual package to
> > upgrade.
> >
> > If this is not the expected behavior, maybe this is a bug (unless I am
> > missing something here).
>
> I do not know what the bug here is, it could be one of these options:
>
> 1) apt-get/apt upgrade accepts packages to upgrade where the docs state it
>doesn't. The behaviour needs to change to not accept packages.
>
> 2) apt-get/apt upgrade accepts packages and removes packages to satisfy
> deps
>where the docs state it doesn't. The behaviour need to change to not
> remove
>any packages. There is a small edge case where you can say: `apt
> upgrade foo
>bar-'. Technically, it shouldn't remove packages, yet you want and
> instruct
>it to remove bar.
>
> FWIW, aptitude does not remove packages where you call `aptitude
> safe-upgrade
> foo'. It does remove packages when you call `aptitude full-upgrade foo'. It
> also removes bar when you run `aptitude safe-upgrade foo bar-'.
>
> I'll leave this for the maintainers to answer.
>
> Cheers,
> Wesley
>
>

Bug#1065831: apt tries to uninstall kde & plasma (full-upgrade)

[Miguel Angel Rojas]

> I see. It looks like `apt upgrade ' behaves as `apt install
> '. Which (to me) is unexpected behaviour, as the man page is
quite
>clear on its behaviour (man 8 apt-get):

Well, clearly it shouldn’t. To begin with, “apt install” should mark a
package as manual installed while “apt upgrade” shouldn’t (my assumption).
And you’re right that “apt install” can remove a package if needed to
satisfy dependencies.

On top of that, documentation clearly states that “apt upgrade” should not
remove any package, but it does when you specify an individual package to
upgrade.

If this is not the expected behavior, maybe this is a bug (unless I am
missing something here).

Bug#1065831: apt tries to uninstall kde & plasma (full-upgrade)

[Miguel Angel Rojas]

Hi Wesley, David,

> You keep saying `apt upgrade' yet your command was `apt full-upgrade'.

Yes, maybe it didn't express itself properly. After your suggestion about
not using "apt full-upgrade" during this t64 migration, I followed your
advice and used only "apt upgrade" for individual upgrades. I was referring
to this comment you made below:

> My advice to you is: don't expect full-upgrade to work until the
transitioning
> is done. You can do `apt upgrade' without too much hassle. If you feel
like it
> you can inspect individual upgrades possibilities  via `apt list
--upgradable'
> and upgrade each package individually.

Therefore, that's the advice I'm following right now.

Now, If I type"apt upgrade" doesn't give me any option to update anything:

# apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer
required:
 linux-headers-6.6.15-amd64 linux-headers-6.6.15-common
linux-image-6.6.15-amd64 linux-kbuild-6.6.15
Use 'apt autoremove' to remove them.
The following packages have been kept back:
 gstreamer1.0-plugins-bad gstreamer1.0-plugins-good
gstreamer1.0-plugins-ugly kaddressbook kmail knotes
 libgstreamer-plugins-bad1.0-0 libkf5akonadisearch-bin
libkf5akonadisearch-plugins
 libkf5messagecomposer5abi1 libkf5messagecore5abi1 libkf5messagelist5abi1
libkf5messageviewer5abi1
 libkf5mimetreeparser5abi1 libkf5pimcommonakonadi5abi1
libkf5templateparser5 libkf5webengineviewer5abi1
 libkpimaddressbookimportexport5 libldb2 libopenconnect5 libqt5webengine5
ppp samba-libs
0 upgraded, 0 newly installed, 0 to remove and 23 not upgraded.


But, in some situations, as you mentioned, individual package upgrades can
work and remove some problems. So what I did was to try some "apt upgrade"
on individual packages from that list. This time I try the ppp package:

# apt upgrade ppp
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer
required:
 linux-headers-6.6.15-amd64 linux-headers-6.6.15-common
linux-image-6.6.15-amd64 linux-kbuild-6.6.15
Use 'apt autoremove' to remove them.
The following packages will be REMOVED: <--- PACKAGE TO BE REMOVED
 libpcap0.8
The following NEW packages will be installed:
 libpcap0.8t64
The following packages have been kept back:
 gstreamer1.0-plugins-bad gstreamer1.0-plugins-good
gstreamer1.0-plugins-ugly kaddressbook kmail knotes
 libgstreamer-plugins-bad1.0-0 libkf5akonadisearch-bin
libkf5akonadisearch-plugins
 libkf5messagecomposer5abi1 libkf5messagecore5abi1 libkf5messagelist5abi1
libkf5messageviewer5abi1
 libkf5mimetreeparser5abi1 libkf5pimcommonakonadi5abi1
libkf5templateparser5 libkf5webengineviewer5abi1
 libkpimaddressbookimportexport5 libldb2 libopenconnect5 libqt5webengine5
samba-libs
The following packages will be upgraded:
 ppp
1 upgraded, 1 newly installed, 1 to remove and 22 not upgraded.
Need to get 511 kB of archives.
After this operation, 15.4 kB disk space will be freed.
,

As you can see here, I'm typing "apt upgrade ppp" and it removes a package
in this case: libpcap0.8 (sometimes more packages are removed).

Which is good, because libpcap0.8 is replaced by libpcap0.8t64 (as expected
in this t64 migration) but "apt upgrade ppp" is REMOVING a package (which
contradicts the specification).

@David: I will send you the file as you requested.

Regards

On Mon, Mar 11, 2024 at 5:44 PM Wesley Schwengle 
wrote:

>
> Hi Miguel,
>
> On Mon, Mar 11, 2024 at 05:09:47PM +0100, Miguel Angel Rojas wrote:
> > > I do not know, at times I'm also wondering why it doesn't do it, but I
> > didn't
> > > take time to look at the code to understand what the resolver is doing.
> > Also,
> > > it was sort of expected. I think we can probably solve this is a more
> > > controlled manner. With the current t64 transitioning in unstable it is
> > > difficult to track down. Many updates so the situation now may differ
> > from the
> > > situation in an hour from now.
> >
> > Yes, it is confusing for me too. Without considering this t64 migration,
> > “apt upgrade” should *NOT* remove any package (just upgrading a package
> to
> > a newer version or install new dependencies). But it is removing packages
> > right now! i.e. again, with this t64 migration, it makes the old
> libraries
> > to be uninstalled and install the new *t64 version.
> >
> > Any thoughts why “apt upgrade” is removing packages even when
> documentation
> > says it shouldn’t? or is it a bug?
>
> You keep saying `apt upgrade' yet your command was `apt full-upgrade'. As
> said
> earlier, full-upgrade does indeed remove packages to be able to perform an
> upgrade. I haven't seen `apt upgrade' do that. So I cannot comment on apt
> doing
> something wrong when it isn't :)
>
> Cheers,
> Wesley
>

Bug#1065831: apt tries to uninstall kde & plasma (full-upgrade)

[Miguel Angel Rojas]

Hi Wesley,

Good conversation here. Let me give you some comments from my side:

> No, there is (or was) something going on with the dependencies of
gdm-minimal
> for sure. I think it is related to libdebuginfod1, which has a t64
variant.
> This one has a dependency to libelf1 and libdw1. Now the libdebuginfod1t64
> depends on libelf1t64 and libdw1t64. These two replace libelf1 and
libdw1, the
> former having a relative high count of reverse dependencies.

I didn’t catch this one (and I spent a fair amount of time trying to find
out what was going on) ;) Thank you for spotting it!

> I do not know, at times I'm also wondering why it doesn't do it, but I
didn't
> take time to look at the code to understand what the resolver is doing.
Also,
> it was sort of expected. I think we can probably solve this is a more
> controlled manner. With the current t64 transitioning in unstable it is
> difficult to track down. Many updates so the situation now may differ
from the
> situation in an hour from now.

Yes, it is confusing for me too. Without considering this t64 migration,
“apt upgrade” should *NOT* remove any package (just upgrading a package to
a newer version or install new dependencies). But it is removing packages
right now! i.e. again, with this t64 migration, it makes the old libraries
to be uninstalled and install the new *t64 version.

Any thoughts why “apt upgrade” is removing packages even when documentation
says it shouldn’t? or is it a bug?

> I disagree (or agree) to some extent. The gdb-minimal has been held back
on my
> system for a long time. I removed it after I saw it was a remnant of a KDE
> experiment I did. The fact that I can install it now is a change from a
couple
> of days ago. The bug may be the same, but with how unstable it is now with
> this big transition, it's wise to leave it where we are now and break it
down
> into a more controlled reproduction path, where we don't have so many
moving
> pieces.

Yes, I fully agreed with that! Let’s wait until packages are fully settled
down. I have a feeling that it is the same bug but there is no way to probe
it with this transition going on.

Regards



On Mon, Mar 11, 2024 at 3:04 PM Wesley Schwengle 
wrote:

>
> Hello Miguel,
>
> On Mon, Mar 11, 2024 at 09:50:12AM +0100, Miguel Angel Rojas wrote:
>
> > >This problem isn't because of apt, the problem is that gdb-minimal/gdb
> > >  dependencies cannot be satified. A full-upgrade is the equivalent of a
> > >  dist-upgrade which will remove packages to resolve the dependencies.
> The
> > > problem you are facing is the t64 transition[1][2] where not all
> packages
> > are
> > >  transitioned.
> >
> > I haven't detected any "gdb | gdb-minimal dependencies that can't be
> > satisfied at this point. Everything seems to be OK with those packages.
>
> No, there is (or was) something going on with the dependencies of
> gdm-minimal
> for sure. I think it is related to libdebuginfod1, which has a t64 variant.
> This one has a dependency to libelf1 and libdw1. Now the libdebuginfod1t64
> depends on libelf1t64 and libdw1t64. These two replace libelf1 and libdw1,
> the
> former having a relative high count of reverse dependencies.
>
> > >  My advice to you is: don't expect full-upgrade to work until the
> > transitioning
> > >   is done.
> >
> > You nail it here! I have managed to upgrade package by package but it is
> a
> > tedious process until the whole transition is completed.
>
> Some of them yes, but often after doing one, you can use `apt upgrade' to
> see if it resolved other problems (which in my case it does from time to
> time).
>
> > But "apt upgrade"
> > should not remove any packages according to its documentation (man apt)
>
> That is correct, but you were executing full-upgrade:
>
> > > On Sun, Mar 10, 2024 at 02:13:34PM +0100, Miguel Angel wrote:
> > >
> > > > # apt full-upgrade
> > > > Reading package lists... Done
> > > > Building dependency tree... Done
> > > > Reading state information... Done
> > > > Calculating upgrade... Error!
> > > > Some packages could not be installed. This may mean that you have
> > > > requested an impossible situation or if you are using the unstable
> > > > distribution that some required packages have not yet been created
> > > > or been moved out of Incoming.
> > > > The following information may help to resolve the situation:
>
> > Why is this t64 upgrade working then as it is removing deprecated
> packages
> > for *t64 packages?
>
> I do not know, at times I'm also wondering why it doesn't do it, but I
> didn't
> take time to

Bug#1065831: apt tries to uninstall kde & plasma (full-upgrade)

[Miguel Angel Rojas]

Hi Wesley,

>This problem isn't because of apt, the problem is that gdb-minimal/gdb
>  dependencies cannot be satified. A full-upgrade is the equivalent of a
>  dist-upgrade which will remove packages to resolve the dependencies. The
> problem you are facing is the t64 transition[1][2] where not all packages
are
>  transitioned.

I haven't detected any "gdb | gdb-minimal dependencies that can't be
satisfied at this point. Everything seems to be OK with those packages.

>  My advice to you is: don't expect full-upgrade to work until the
transitioning
>   is done.

You nail it here! I have managed to upgrade package by package but it is a
tedious process until the whole transition is completed. But "apt upgrade"
should not remove any packages according to its documentation (man apt)

*"upgrade is used to install available upgrades of all packages currently
installed on the system from the sources configured via sources.list(5).
New packages will be installed if required to satisfy dependencies, but
existing packages will never be removed. If an upgrade for apackage
requires the remove of an installed package the upgrade for thispackage
isn't performed."*

Why is this t64 upgrade working then as it is removing deprecated packages
for *t64 packages?

>  This seems to be an more of an actual issue where dependencies are
declared but
>apt doing something weird. But that is an issue on bookworm where we
aren't
>getting poluted results because of a transitioning.

I'm glad you were able to replicate in bookworm (stable) it but I don't
think (at least in this case) it is related to the t64 transition. Same
errors on both distributions and I checked that gdb dependencies were
satisfied in unstable (I don't have a system running stable).

> I don't know either and that question should be redirected to the
> plasma-workspace maintainer.

good advice! I will.

Appreciate your support.

Thanks!


On Sun, Mar 10, 2024 at 8:20 PM Wesley Schwengle 
wrote:

> On Sun, Mar 10, 2024 at 02:13:34PM +0100, Miguel Angel wrote:
>
> > # apt full-upgrade
> > Reading package lists... Done
> > Building dependency tree... Done
> > Reading state information... Done
> > Calculating upgrade... Error!
> > Some packages could not be installed. This may mean that you have
> > requested an impossible situation or if you are using the unstable
> > distribution that some required packages have not yet been created
> > or been moved out of Incoming.
> > The following information may help to resolve the situation:
> >
> > The following packages have unmet dependencies:
> >  plasma-workspace : Depends: gdb-minimal but it is not going to be
> installed or
> >  gdb
> > E: Error, pkgProblemResolver::Resolve generated breaks, this may be
> caused by held packages.
> >
>
> This problem isn't because of apt, the problem is that gdb-minimal/gdb
> dependencies cannot be satified. A full-upgrade is the equivalent of a
> dist-upgrade which will remove packages to resolve the dependencies. The
> problem you are facing is the t64 transition[1][2] where not all packages
> are
> transitioned.
>
> My advice to you is: don't expect full-upgrade to work until the
> transitioning
> is done. You can do `apt upgrade' without too much hassle. If you feel
> like it
> you can inspect individual upgrades possibilities  via `apt list
> --upgradable'
> and upgrade each package individually. That has worked well for me in the
> past
> week with aptitude, but it requires going through many offered solutions.
>
> > I've seen other users are experimenting the same issue:
> > https://groups.google.com/g/linux.debian.user/c/7gpQImSH-Cs
>
> This seems to be an more of an actual issue where dependencies are
> declared but
> apt doing something weird. But that is an issue on bookworm where we aren't
> getting poluted results because of a transitioning. It differs from yours
> because your apt output says "gdb-minimal but it is not going to be
> installed
> or gdb" so apt sees the alternative, but cannot install it either. IMHO,
> that should
> be filed as a seperate bug against apt on bookworm. And if possible
> checked on
> testing as well. FWIW, I can reproduce it on bookwork with apt, apt-get and
> aptitude, where the latter offers a solution to install gdb and not
> deinstall
> plasma-workspace.
>
> > I don't know why plasma-workspace depends on gdb
>
> I don't know either and that question should be redirected to the
> plasma-workspace maintainer.
>
> Cheers,
> Wesley
>
> [1] https://lists.debian.org/debian-devel-announce/2024/02/msg0.html
> [2]
> https://www.reddit.com/r/debian/comments/1b2ncdn/64bit_time_t_transition_in_progress_in_unstable/
>
>

Bug#1065831: apt tries to uninstall kde & plasma (full-upgrade)

[Miguel Angel]

Package: apt
Version: 2.7.13+b1
Severity: normal
X-Debbugs-Cc: mianro...@gmail.com

# apt full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Error!
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 plasma-workspace : Depends: gdb-minimal but it is not going to be installed or
 gdb
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

I don't know why plasma-workspace depends on gdb, but nevertheless,
full-upgrade doesn't work.

I've seen other users are experimenting the same issue: 
https://groups.google.com/g/linux.debian.user/c/7gpQImSH-Cs

If you mark plasma-workspace as hold, apt is still trying to remove
other kde & plasma package (its reverse dependencies).


-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "1";
APT::Install-Suggests "0";
APT::Key "";
APT::Key::Assert-Pubkey-Algo ">=rsa2048,ed25519,ed448";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*-[a-z0-9]*$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-.*";
APT::VersionedKernelPackages:: "kfreebsd-.*";
APT::VersionedKernelPackages:: "gnumach-.*";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "tasks";
APT::Move-Autobit-Sections "";
APT::Move-Autobit-Sections:: "oldlibs";
APT::Update "";
APT::Update::Post-Invoke-Success "";
APT::Update::Post-Invoke-Success:: "/usr/bin/test -e 
/usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && 
/usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call 
--system --dest org.freedesktop.PackageKit --object-path 
/org/freedesktop/PackageKit --timeout 4 --method 
org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo 
> /dev/null";
APT::Update::Post-Invoke-Success:: "if /usr/bin/test -w /var/cache/swcatalog -a 
-e /usr/bin/appstreamcli; then appstreamcli refresh --source=os > /dev/null || 
true; fi";
APT::Architectures "";
APT::Architectures:: "amd64";
APT::Compressor "";
APT::Compressor::. "";
APT::Compressor::.::Name ".";
APT::Compressor::.::Extension "";
APT::Compressor::.::Binary "";
APT::Compressor::.::Cost "0";
APT::Compressor::zstd "";
APT::Compressor::zstd::Name "zstd";
APT::Compressor::zstd::Extension ".zst";
APT::Compressor::zstd::Binary "zstd";
APT::Compressor::zstd::Cost "60";
APT::Compressor::zstd::CompressArg "";
APT::Compressor::zstd::CompressArg:: "-19";
APT::Compressor::zstd::UncompressArg "";
APT::Compressor::zstd::UncompressArg:: "-d";
APT::Compressor::lz4 "";
APT::Compressor::lz4::Name "lz4";
APT::Compressor::lz4::Extension ".lz4";
APT::Compressor::lz4::Binary "false";
APT::Compressor::lz4::Cost "50";
APT::Compressor::gzip "";
APT::Compressor::gzip::Name "gzip";
APT::Compressor::gzip::Extension ".gz";
APT::Compressor::gzip::Binary "gzip";
APT::Compressor::gzip::Cost "100";
APT::Compressor::gzip::CompressArg "";
APT::Compressor::gzip::CompressArg:: "-6n";
APT::Compressor::gzip::UncompressArg "";
APT::Compressor::gzip::UncompressArg:: "-d";
APT::Compressor::xz "";
APT::Compressor::xz::Name "xz";
APT::Compressor::xz::Extension ".xz";
APT::Compressor::xz::Binary "xz";
APT::Compressor::xz::Cost "200";
APT::Compressor::xz::CompressArg "";
APT::Compressor::xz::CompressArg:: "-6";
APT::Compressor::xz::UncompressArg "";
APT::Compressor::xz::UncompressArg:: "-d";
APT::Compressor::bzip2 "";
APT::Compressor::bzip2::Name "bzip2";
APT::Compressor::bzip2::Extension ".bz2";
APT::Compressor::bzip2::Binary "bzip2";
APT::Compressor::bzip2::Cost "300";
APT::Compressor::bzip2::CompressArg "";
APT::Compressor::bzip2::CompressArg:: "-6";
APT::Compressor::bzip2::UncompressArg "";
APT::Compressor::bzip2::UncompressArg:: "-d";
APT::Compressor::lzma "";
APT::Compressor::lzma::Name "lzma";
APT::Compressor::lzma::Extension ".lzma";
APT::Compressor::lzma::Binary "xz";
APT::Compressor::lzma::Cost "400";
APT::Compressor::lzma::CompressArg "";
APT::Compressor::lzma::CompressArg:: "--format=lzma";
APT::Compressor::lzma::CompressArg:: "-6";
APT::Compressor::lzma::UncompressArg "";
APT::Compressor::lzma::UncompressArg:: "--format=lzma";

Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2

[Miguel Angel Rojas]

Hi Diederik,

> While 'annoying', this is expected behavior. It tries to load the newest
(-83)
Yes, this is the expected behavior from our Linux kernel. However, I agree
with you and these messages are very annoying and should be removed.

> It could be it wouldn't be shown if it had already found one of the
earlier logged firmware files.
Interesting theory! When the new version of the firmware packages is
uploaded, we can check again if the "'iwl-debug-yoyo.bin" message disappears

Why are you confused with the numbers?
>Bit confused about that version number, but looks like success.

And yes, wifi is working fine although I haven't properly done any
performance test yet.

Regards


On Sun, Feb 11, 2024 at 4:15 PM Diederik de Haas 
wrote:

> Hi Miguel,
>
> On Sunday, 11 February 2024 16:03:20 CET Miguel A. Rojas wrote:
> > I forgot to include you the dmesg as promised:
> >
> > [2.235947] iwlwifi :00:14.3: enabling device ( -> 0002)
> > [2.237778] iwlwifi :00:14.3: Detected crf-id 0x1300504, cnv-id
> > 0x80401 wfpm id 0x8030
> > [2.237805] iwlwifi :00:14.3: PCI dev 7a70/0074, rev=0x430,
> > rfid=0x10a100
> > [2.237845] iwlwifi :00:14.3: firmware: failed to load
> > iwlwifi-so-a0-hr-b0-83.ucode (-2)
> > [2.237867] iwlwifi :00:14.3: firmware: failed to load
> > iwlwifi-so-a0-hr-b0-83.ucode (-2)
> > ... more firmware load failures
> > [2.238098] iwlwifi :00:14.3: Direct firmware load for
> > iwlwifi-so-a0-hr-b0-73.ucode failed with error -2
> > [2.241012] iwlwifi :00:14.3: firmware: direct-loading firmware
> > iwlwifi-so-a0-hr-b0-72.ucode
>
> While 'annoying', this is expected behavior. It tries to load the newest
> (-83)
> and when it can't find that, it tries an older one and ends up with '-72'.
>
> > [2.247819] iwlwifi :00:14.3: api flags index 2 larger than
> > supported by driver
> > [2.247832] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version:
> > 0.0.2.36
> > [2.248049] iwlwifi :00:14.3: firmware: failed to load
> > iwl-debug-yoyo.bin (-2)
> <-
> > [2.248067] iwlwifi :00:14.3: firmware: failed to load
> > iwl-debug-yoyo.bin (-2)
> <-
>
> This 'iwl-debug-yoyo.bin' is a familiar one, but this file is NOT
> available in
> the upstream linux-firmware repo.
> It could be it wouldn't be shown if it had already found one of the
> earlier
> logged firmware files.
> I might look into this particular issue at some later date.
>
> > [2.248078] iwlwifi :00:14.3: loaded firmware version
> > 72.daa05125.0 so-a0-hr-b0-72.ucode op_mode iwlmvm
>
> Bit confused about that version number, but looks like success ...
>
> > [2.653952] iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6 AX201
> > 160MHz, REV=0x430
> > [2.769070] iwlwifi :00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x3f
> > [2.769102] iwlwifi :00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
> > [2.769110] iwlwifi :00:14.3: WFPM_AUTH_KEY_0: 0x90
> > [2.769118] iwlwifi :00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
> > [2.769154] iwlwifi :00:14.3: Detected RF HR B3, rfid=0x10a100
> > [2.834751] iwlwifi :00:14.3: base HW address: bc:09:1b:d3:e2:ee
> > [2.849492] iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0
> > [6.570171] iwlwifi :00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x3f
> > [6.570263] iwlwifi :00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
> > [6.570275] iwlwifi :00:14.3: WFPM_AUTH_KEY_0: 0x90
> > [6.570307] iwlwifi :00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
> > [6.644756] iwlwifi :00:14.3: Registered PHC clock: iwlwifi-PTP,
> > with index: 0
> > [6.809353] iwlwifi :00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x3f
> > [6.809386] iwlwifi :00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
> > [6.809397] iwlwifi :00:14.3: WFPM_AUTH_KEY_0: 0x90
> > [6.809408] iwlwifi :00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
>
> ... and from this it seems the device appears to be working properly?
>
> If that's indeed the case then this bug would essentially be a request for
> a
> new upstream version.
>
> Cheers,
>   Diederik

Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2

[Miguel Angel Rojas]

Hi Diederik,

My bad. Let me explain again. Taking into account the firmware errors:

   - Realtek messages are fixed now. There are no actions to be done here.
   - iwlwifi: If you are still working on a new version containing the -83
   file, that should fix some warning messages but not all of them. There is
   another message (*firmware: failed to load iwl-debug-yoyo.bin (-2)*)
   that I think is related to bug #966218. This bug has been there for a
   while, so I don't know what's happening here. Nobody explains what's going
   on or why this file is not included in the firmware package.

Thanks!


On Fri, Feb 9, 2024 at 7:48 PM Diederik de Haas 
wrote:

> Control: tag -1 moreinfo
>
> Hi,
>
> On Friday, 9 February 2024 19:35:01 CET Miguel A. Rojas wrote:
> > A few days ago, I went to
> >
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
> > and update the missing loaded modules.
> >
> > Indeed, I noticed that I have another messages related to the iwlwifi
> > module: "kernel: iwlwifi :00:14.3: firmware: failed to load
> > iwlwifi-so-a0-hr-b0-83.ucode (-2)".
>
> The reason I asked for more dmesg lines is that it likely then tried
> (f.e.)
> -81, then -79 and then probably succeeded at some point.
> The Debian kernel (unfortunately imo) 'promoted' warning/info messages to
> errors, which make it appear more severe then they actually are.
>
> > I think the the root cause is that the current Debian packages firmware
> > packages are 6 months old and they need to be updated accordingly. New
> > Debian Linux kernel expects a specific version of the firmware or the
> > name of the firmware has changed.
>
> I do think that the old package versions are a problem, so I have been
> working
> on Merge Requests for updating them.
> Version 20230804 would make the -83 file available.
> But the device using and older version should still work. If it doesn't
> work
> with an older version, but it does work with a newer, that's important
> info.
>
> But I'm still a bit confused as this bug is about *realtek* firmware, not
> iwlwifi? Can you answer the question I asked previously?

Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2

[Miguel Angel]

Package: firmware-realtek
Version: 20230625-2
Severity: important
X-Debbugs-Cc: mianro...@gmail.com

At system boot, the following message is shown: 
"Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2".

It seesm that the firmware is not properly loaded by kernel at boot. 


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

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

firmware-realtek depends on no packages.

firmware-realtek recommends no packages.

Versions of packages firmware-realtek suggests:
ii  initramfs-tools  0.142

-- no debconf information

Bug#1041331: Note on the example configuration

[Angel Ortega]

I think the configuration file, as shown in the bug report, has a bug; the last 
location should probably be


ProxyPass http://127.0.0.1:8001/snac
ProxyPreserveHost On
RequestHeaderset X-Forwarded-Proto 'https' env=HTTPS


Note the leading /snac at the end of ProxyPass; with the proposed 
configuration, the data reaches the snac server correctly, but the path is 
truncated to /USER/inbox (instead of the expected /snac/USER/inbox), and as the 
path is used in the HTTP Signature, the validation fails.

Hope it helps (I'm by no means an Apache2 expert and use nginx myself with 
snac).

Best regards,
Ángel Ortega

Bug#1053886: apt autoremove removes old kernel (ignoring default configuration)

[Miguel Angel]

Package: apt
Version: 2.7.3
Severity: normal
X-Debbugs-Cc: mianro...@gmail.com

Beside the fact that kernel packages should not removed by default
(according to /etc/apt/apt.conf.d/01autoremove), older kernel packages are 
removed
after executing 'apt autoremove'.

Regards

-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "1";
APT::Install-Suggests "0";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*-[a-z0-9]*$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-.*";
APT::VersionedKernelPackages:: "kfreebsd-.*";
APT::VersionedKernelPackages:: "gnumach-.*";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "tasks";
APT::Move-Autobit-Sections "";
APT::Move-Autobit-Sections:: "oldlibs";
APT::Update "";
APT::Update::Post-Invoke-Success "";
APT::Update::Post-Invoke-Success:: "/usr/bin/test -e 
/usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && 
/usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call 
--system --dest org.freedesktop.PackageKit --object-path 
/org/freedesktop/PackageKit --timeout 4 --method 
org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo 
> /dev/null";
APT::Update::Post-Invoke-Success:: "if /usr/bin/test -w /var/cache/swcatalog -a 
-e /usr/bin/appstreamcli; then appstreamcli refresh --source=os > /dev/null || 
true; fi";
APT::Architectures "";
APT::Architectures:: "amd64";
APT::Compressor "";
APT::Compressor::. "";
APT::Compressor::.::Name ".";
APT::Compressor::.::Extension "";
APT::Compressor::.::Binary "";
APT::Compressor::.::Cost "0";
APT::Compressor::zstd "";
APT::Compressor::zstd::Name "zstd";
APT::Compressor::zstd::Extension ".zst";
APT::Compressor::zstd::Binary "zstd";
APT::Compressor::zstd::Cost "60";
APT::Compressor::zstd::CompressArg "";
APT::Compressor::zstd::CompressArg:: "-19";
APT::Compressor::zstd::UncompressArg "";
APT::Compressor::zstd::UncompressArg:: "-d";
APT::Compressor::lz4 "";
APT::Compressor::lz4::Name "lz4";
APT::Compressor::lz4::Extension ".lz4";
APT::Compressor::lz4::Binary "false";
APT::Compressor::lz4::Cost "50";
APT::Compressor::gzip "";
APT::Compressor::gzip::Name "gzip";
APT::Compressor::gzip::Extension ".gz";
APT::Compressor::gzip::Binary "gzip";
APT::Compressor::gzip::Cost "100";
APT::Compressor::gzip::CompressArg "";
APT::Compressor::gzip::CompressArg:: "-6n";
APT::Compressor::gzip::UncompressArg "";
APT::Compressor::gzip::UncompressArg:: "-d";
APT::Compressor::xz "";
APT::Compressor::xz::Name "xz";
APT::Compressor::xz::Extension ".xz";
APT::Compressor::xz::Binary "xz";
APT::Compressor::xz::Cost "200";
APT::Compressor::xz::CompressArg "";
APT::Compressor::xz::CompressArg:: "-6";
APT::Compressor::xz::UncompressArg "";
APT::Compressor::xz::UncompressArg:: "-d";
APT::Compressor::bzip2 "";
APT::Compressor::bzip2::Name "bzip2";
APT::Compressor::bzip2::Extension ".bz2";
APT::Compressor::bzip2::Binary "bzip2";
APT::Compressor::bzip2::Cost "300";
APT::Compressor::bzip2::CompressArg "";
APT::Compressor::bzip2::CompressArg:: "-6";
APT::Compressor::bzip2::UncompressArg "";
APT::Compressor::bzip2::UncompressArg:: "-d";
APT::Compressor::lzma "";
APT::Compressor::lzma::Name "lzma";
APT::Compressor::lzma::Extension ".lzma";
APT::Compressor::lzma::Binary "xz";
APT::Compressor::lzma::Cost "400";
APT::Compressor::lzma::CompressArg "";
APT::Compressor::lzma::CompressArg:: "--format=lzma";
APT::Compressor::lzma::CompressArg:: "-6";
APT::Compressor::lzma::UncompressArg "";
APT::Compressor::lzma::UncompressArg:: "--format=lzma";
APT::Compressor::lzma::UncompressArg:: "-d";
Dir "/";
Dir::State "var/lib/apt";
Dir::State::lists "lists/";
Dir::State::cdroms "cdroms.list";
Dir::State::extended_states "extended_states";
Dir::State::status "/var/lib/dpkg/status";
Dir::Cache "var/cache/apt";
Dir::Cache::archives "archives/";
Dir::Cache::srcpkgcache "srcpkgcache.bin";
Dir::Cache::pkgcache "pkgcache.bin";
Dir::Etc "etc/apt";
Dir::Etc::sourcelist "sources.list";
Dir::Etc::sourceparts "sources.list.d";
Dir::Etc::main "apt.conf";
Dir::Etc::netrc "auth.conf";
Dir::Etc::netrcparts "auth.conf.d";
Dir::Etc::parts "apt.conf.d";
Dir::Etc::preferences "preferences";
Dir::Etc::preferencesparts "preferences.d";
Dir::Etc::trusted "trusted.gpg";
Dir::Etc::trustedparts "trusted.gpg.d";
Dir::Etc::apt-file-main "apt-file.conf";
Dir::Bin "";
Dir::Bin::methods "/usr/lib/apt/methods";
Dir::Bin::solvers "";
Dir::Bin::solvers:: "/usr/lib/apt/solvers";
Dir::Bin::planners "";

Bug#1052012: plasma-workspace: sddm presents a white screen with no background nor buttons

[Miguel Angel Rojas]

Hi there,

Downgrading the following packages:

   - sddm-themes-breeze
   - sddm-theme-debian-breeze

to version 4:5.27.7-2 makes sddm fully usable again with no issues.

It seems some changes have been made on version 4:5.27.8-1 that have broken
sddm.

I hope this helps.

Regards

Bug#1052012: plasma-workspace: sddm presents a white screen with no background nor buttons

[Miguel Angel]

Package: plasma-workspace
Version: 4:5.27.8-1
Severity: important
X-Debbugs-Cc: mianro...@gmail.com

After upgrading from 4:5.27-7-1, sddm because unusuable. Background is
ignored (white), there are no button on the screen and the only thing you can
see on the screen is the icon showing the user and password field below
it (with very tiny asterisks) in a horrible format.


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

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

Versions of packages plasma-workspace depends on:
ii  dbus-user-session [default-dbus-session-bus] 1.14.10-1
ii  drkonqi  5.27.8-1
ii  frameworkintegration 5.107.0-1
ii  gdb-minimal [gdb]13.2-1
ii  init-system-helpers  1.65.2
ii  iso-codes4.15.0-1
ii  kactivitymanagerd5.27.8-1
ii  kded55.107.0-1
ii  kinit5.107.0-1
ii  kio  5.107.0-1
ii  kpackagetool55.107.0-1
ii  kwin-common  4:5.27.8-1
ii  libappstreamqt2  0.16.3-1
ii  libc62.37-9
ii  libcolorcorrect5 4:5.27.8-1
ii  libcrypt11:4.4.36-2
ii  libfontconfig1   2.14.2-6
ii  libfreetype6 2.13.2+dfsg-1
ii  libgcc-s113.2.0-4
ii  libgps30 3.25-2
ii  libice6  2:1.0.10-1
ii  libicu72 72.1-3
ii  libkf5activities55.107.0-1
ii  libkf5activitiesstats1   5.107.0-1
ii  libkf5archive5   5.107.0-1
ii  libkf5authcore5  5.107.0-1
ii  libkf5baloo5 5.107.0-1
ii  libkf5bookmarks5 5.107.0-1
ii  libkf5calendarevents55.107.0-1
ii  libkf5completion55.107.0-1
ii  libkf5config-bin 5.107.0-1
ii  libkf5configcore55.107.0-1
ii  libkf5configgui5 5.107.0-1
ii  libkf5configwidgets5 5.107.0-2
ii  libkf5coreaddons55.107.0-1
ii  libkf5crash5 5.107.0-1
ii  libkf5dbusaddons55.107.0-1
ii  libkf5declarative5   5.107.0-1
ii  libkf5globalaccel-bin5.107.0-2
ii  libkf5globalaccel5   5.107.0-2
ii  libkf5guiaddons5 5.107.0-1
ii  libkf5holidays5  1:5.107.0-1
ii  libkf5i18n5  5.107.0-1+b1
ii  libkf5iconthemes55.107.0-1+b1
ii  libkf5idletime5  5.107.0-1
ii  libkf5jobwidgets55.107.0-1
ii  libkf5kcmutils5  5.107.0-2
ii  libkf5kexiv2-15.0.0  23.04.2-2
ii  libkf5kiocore5   5.107.0-1
ii  libkf5kiofilewidgets55.107.0-1
ii  libkf5kiogui55.107.0-1
ii  libkf5kiowidgets55.107.0-1
ii  libkf5networkmanagerqt6  5.107.0-1
ii  libkf5newstuff5  5.107.0-1
ii  libkf5newstuffcore5  5.107.0-1
ii  libkf5newstuffwidgets5   5.107.0-1
ii  libkf5notifications5 5.107.0-1
ii  libkf5notifyconfig5  5.107.0-1
ii  libkf5package5   5.107.0-1
ii  libkf5parts5 5.107.0-1
ii  libkf5people55.107.0-1
ii  

Bug#1037422: spamprobe crashing with emails containing an image attached

[Miguel Angel Varo Giner]

Package: spamprobe
Version: 1.4d-16
Followup-For: Bug #1037422

After upgrading from bullseye to bookworm I've found spamprobe is not
working with some emails. I've found that the emails spamprobe is having
problems with is the ones with images attached (jpg or png). Whenever it
processes one of those emails it fails with:

"caught signal 11: quitting
Aborted"


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

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

Versions of packages spamprobe depends on:
ii  debconf [debconf-2.0]  1.5.82
ii  libc6  2.36-9+deb12u1
ii  libdb5.3   5.3.28+dfsg2-1
ii  libgcc-s1  12.2.0-14
ii  libgif75.2.1-2.5
ii  libjpeg62-turbo1:2.1.5-2
ii  libpng16-161.6.39-2
ii  libstdc++6 12.2.0-14

Versions of packages spamprobe recommends:
ii  procmail  3.22-27

spamprobe suggests no packages.

-- debconf information:
* spamprobe/db53_upgrade:
  spamprobe/db51_upgrade:

Bug#1040174: nvidia-driver: Can't upgrade to nvidia-driver-525.116.04-1 on debian unstable: build fails

[Miguel Angel Rojas]

Hi there,

I can confirm the bug is there. Libraries are not found and NVIDIA driver
fails to build.

Regards

Bug#1036937: yaru-theme-gnome-shell: notifications do not disturb slider missing except in default Yaru variant

[Angel Segarra]

Package: yaru-theme-gnome-shell
Version: 22.10.3-1
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?
 Changing gnome-shell theme to a variant other than 'Yaru', e.g. 'Yaru-dark'

   * What was the outcome of this action?
 The notifications do not disturbed slider is missing, the following is 
logged to the journal:
 Failed to load resource:///org/gnome/shell/theme/toggle-off-dark.svg: The 
resource at “/org/gnome/shell/theme/toggle-off-dark.svg” does not exist

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


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

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

-- no debconf information

Bug#1036626: giara: Crashes on startup

[Angel Ortega]

Package: giara
Version: 1.0.1-2
Severity: important

Dear Maintainer,

giara crashes on startup with the following output:

Traceback (most recent call last):
  File "/bin/giara", line 46, in 
gi.require_version('Gtk', '4.0')
  File "/usr/lib/python3/dist-packages/gi/__init__.py", line 129, in 
require_version
raise ValueError('Namespace %s not available for version %s' %
ValueError: Namespace Gtk not available for version 4.0

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

Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.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 giara depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  gir1.2-gtksource-4   4.8.4-4
ii  gir1.2-webkit2-4.0   2.40.1-1
ii  libhandy-1-0 1.8.1-1
ii  python3  3.11.2-1+b1
ii  python3-bs4  4.11.2-2
ii  python3-dateutil 2.8.2-2
ii  python3-mistune  2.0.4-1
ii  python3-praw 7.6.0-1
ii  python3-requests 2.28.1+dfsg-1

giara recommends no packages.

giara suggests no packages.

-- no debconf information

Bug#1001991: parole: Parole 4.16.0 does not save playlist

[Miguel Angel Marcos]

Package: parole
Version: 4.16.0-1
Severity: normal
Tags: upstream
X-Debbugs-Cc: newbadho...@gmail.com

Dear Maintainer,

parole media player does not save playlist.

Steps to reproduce:
Add vieos/streams/songs to playlist
choose Media>save playlist
Nothing is saved

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

Kernel: Linux 5.10.0-10-amd64 (SMP w/4 CPU threads)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.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 parole depends on:
ii  gstreamer1.0-alsa [gstreamer1.0-audiosink]  1.18.4-2
ii  gstreamer1.0-libav  1.18.4-3
ii  gstreamer1.0-plugins-bad [gstreamer1.0-audiosink]   1.18.4-3
ii  gstreamer1.0-plugins-base   1.18.4-2
ii  gstreamer1.0-plugins-good [gstreamer1.0-audiosink]  1.18.4-2
ii  gstreamer1.0-x  1.18.4-2
ii  libc6   2.31-13+deb11u2
ii  libcairo2   1.16.0-5
ii  libdbus-1-3 1.12.20-2
ii  libdbus-glib-1-20.110-6
ii  libgdk-pixbuf-2.0-0 2.42.2+dfsg-1
ii  libglib2.0-02.66.8-1
ii  libgstreamer-plugins-base1.0-0  1.18.4-2
ii  libgstreamer1.0-0   1.18.4-2.1
ii  libgtk-3-0  3.24.24-4
ii  libnotify4  0.7.9-3
ii  libtagc01.11.1+dfsg.1-3
ii  libx11-62:1.7.2-1
ii  libxfce4ui-2-0  4.16.0-1
ii  libxfce4util7   4.16.0-1
ii  libxfconf-0-3   4.16.0-2

parole recommends no packages.

Versions of packages parole suggests:
ii  gstreamer1.0-plugins-bad   1.18.4-3
ii  gstreamer1.0-plugins-ugly  1.18.4-2

-- no debconf information

Bug#998402: Error launching onionshare-gui

[Angel Abad]

Package: onionshare
Version: 2.2-3
Severity: important
File: /usr/bin/onionshare-gui

Dear Maintainer,

When I try to launch onionshare it doesnt launch, so when we try to launch it
from bash console, I get this error, and the program fails:

$ onionshare-gui
OnionShare 2.2 | https://onionshare.org/
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use
QT_QPA_PLATFORM=wayland to run on Wayland anyway.
QSocketNotifier: Can only be used with threads started with QThread
QObject::connect: No such signal
QPlatformNativeInterface::systemTrayWindowChanged(QScreen*)
Traceback (most recent call last):
  File "/usr/bin/onionshare-gui", line 22, in 
onionshare_gui.main()
  File "/usr/lib/python3/dist-packages/onionshare_gui/__init__.py", line 142,
in main
gui = OnionShareGui(common, onion, qtapp, app, filenames, config,
local_only)
  File "/usr/lib/python3/dist-packages/onionshare_gui/onionshare_gui.py", line
172, in __init__
self.share_mode.init()
  File "/usr/lib/python3/dist-
packages/onionshare_gui/mode/share_mode/__init__.py", line 48, in init
self.web = Web(self.common, True, "share")
  File "/usr/lib/python3/dist-packages/onionshare/web/web.py", line 77, in
__init__
self.generate_static_url_path()
  File "/usr/lib/python3/dist-packages/onionshare/web/web.py", line 166, in
generate_static_url_path
self.app.add_url_rule(
  File "/usr/lib/python3/dist-packages/flask/scaffold.py", line 56, in
wrapper_func
return f(self, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/flask/app.py", line 1092, in
add_url_rule
raise AssertionError(
AssertionError: View function mapping is overwriting an existing endpoint
function: static

Thanks in advance!


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

Kernel: Linux 5.14.0-3-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.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 onionshare depends on:
ii  obfs4proxy  0.0.8-1+b6
ii  python3 3.9.7-1
ii  python3-flask   2.0.1-2
ii  python3-flask-httpauth  3.2.4-3.1
ii  python3-pycryptodome3.9.7+dfsg1-1+b2
ii  python3-pyqt5   5.15.6+dfsg-1
ii  python3-socks   1.7.1+dfsg-1
ii  python3-stem1.8.0-3
ii  tor 0.4.6.8-1

onionshare recommends no packages.

onionshare suggests no packages.

-- no debconf information

Bug#792580: Veri

[ANGEL GEOVANNY ALMEIDA OLVERA]

Good morning, it was unfair to keep me waiting indefinitely without any 
response.

Bug#992657: kio: Invalid escape sequence in /usr/share/kservices5/searchproviders/rae.desktop

[Angel Aguilera]

It seems it has been fixed upstream:
https://bugs.kde.org/show_bug.cgi?id=438632

Bug#989503: xdg-desktop-portal-wlr: Please upgrade version 0.4.0

[Angel Abad]

Package: xdg-desktop-portal-wlr
Version: 0.1.0-3
Severity: important

Dear Maintainer,

Please upgrade package, with current debian version firefox screen sharing
doesn't work.

I tested 0.4.0 upstream version and it works fine on debian unstable with sway
and firefox out of the box.

Thanks a lot!


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

Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.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 xdg-desktop-portal-wlr depends on:
ii  libc6   2.31-12
ii  libpipewire-0.3-0   0.3.19-4
ii  libsystemd0 247.3-5
ii  libwayland-client0  1.19.0-2
ii  xdg-desktop-portal  1.8.1-1

xdg-desktop-portal-wlr recommends no packages.

xdg-desktop-portal-wlr suggests no packages.

Bug#970524: (no subject)

[Angel Abad]

Hi! I have the same problem with wokkel package.

Thanks!

Bug#966107: Sorry for the bug description

[angel]

Hi! Sorry for the bug description, reportbugs failed.

So, please uprade kitty terminal, if you need help i could try
to help you.

Thanks!


signature.asc
Description: PGP signature

Bug#966107: kitty: Please upgrade to 0.18.1

[Angel Abad]

Package: kitty
Version: 0.17.4-1
Severity: normal

Dear Maintainer,

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

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

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



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

Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.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 kitty depends on:
ii  kitty-terminfo  0.17.4-1
ii  libc6   2.31-1
ii  libdbus-1-3 1.12.20-1
ii  libfontconfig1  2.13.1-4.2
ii  libfreetype62.10.2+dfsg-3
ii  libharfbuzz0b   2.6.7-1
ii  libpng16-16 1.6.37-2
ii  libpython3.83.8.5-1
ii  libwayland-client0  1.18.0-1
ii  libx11-62:1.6.9-2+b1
ii  libx11-xcb1 2:1.6.9-2+b1
ii  libxkbcommon-x11-0  0.10.0-1
ii  libxkbcommon0   0.10.0-1
ii  python3 3.8.2-3
ii  python3.8   3.8.5-1
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages kitty recommends:
ii  kitty-doc 0.17.4-1
ii  libcanberra0  0.30-7

Versions of packages kitty suggests:
ii  imagemagick  8:6.9.10.23+dfsg-2.1+b2
ii  imagemagick-6.q16 [imagemagick]  8:6.9.10.23+dfsg-2.1+b2

-- no debconf information

Bug#963174: plasma-desktop: Missing desktop-file-utils dependency causes x-scheme-handler be ignored

[Jose Angel Pastrana]

Package: plasma-desktop
Version: 4:5.17.5-3
Severity: minor

Dear Maintainer,

desktop-file-utils is needed for handling MimeType attribute in desktop files. 
This package generates /usr/share/applications/mimeinfo.cache file which is 
used by other applications as Firefox [1].

Steps to reproduce this bug:
Prerequisites: firefox and remmina installed, desktop-file-utils not installed

1. Open Firefox
2. Write vnc://192.168.1.1 in tab bar and press enter
3. Url is incomprehensible for Firefox
4. Install desktop-file-utils package and repeat the preceding steps
5. Remmina opens

Explanation:
Remmina desktop file (/usr/share/applications/remmina-file.desktop) contains 
MimeType=x-scheme-handler/vnc and desktop-file-utils has written 
x-scheme-handler/vnc=org.remmina.Remmina.desktop;remmina-file.desktop; entry in 
/usr/share/applications/mimeinfo.cache

Other desktops:
If you execute apt-cache rdepends desktop-file-utils, you may find that 
desktop-file-utils is a dependency for LXQT (pcmanfm-qt package), GNOME 
(gnome-control-center), MATE (mate-control-center) and CINNAMON 
(cinnamon-control-center)

Request:
Add desktop-file-utils as dependecy for plasma-desktop (/ or for a secondary 
package which fits better)

Thanks in advance

[1]: https://bugzilla.mozilla.org/show_bug.cgi?id=727422


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

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

Versions of packages plasma-desktop depends on:
ii  breeze   4:5.17.5-2
ii  kactivitymanagerd5.17.5-2
ii  kde-cli-tools4:5.17.5-2
ii  kded55.70.0-1
ii  kio  5.70.1-1
ii  kpackagetool55.70.0-1
ii  libc62.30-8
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.1-2
ii  libgcc-s110.1.0-3
ii  libglib2.0-0 2.64.3-1
ii  libibus-1.0-51.5.22-5
ii  libkf5activities55.70.0-1
ii  libkf5activitiesstats1   5.70.0-1
ii  libkf5archive5   5.70.0-1
ii  libkf5authcore5  5.70.0-1
ii  libkf5baloo5 5.70.0-2
ii  libkf5codecs55.70.0-1
ii  libkf5completion55.70.0-1
ii  libkf5configcore55.70.0-1
ii  libkf5configgui5 5.70.0-1
ii  libkf5configwidgets5 5.70.0-1
ii  libkf5coreaddons55.70.0-1
ii  libkf5dbusaddons55.70.0-1
ii  libkf5declarative5   5.70.0-1
ii  libkf5emoticons-bin  5.70.0-1
ii  libkf5emoticons5 5.70.0-1
ii  libkf5globalaccel-bin5.70.0-1
ii  libkf5globalaccel5   5.70.0-1
ii  libkf5guiaddons5 5.70.0-2
ii  libkf5i18n5  5.70.0-1
ii  libkf5iconthemes55.70.0-1
ii  libkf5itemmodels55.70.0-1.1
ii  libkf5itemviews5 5.70.0-1
ii  libkf5jobwidgets55.70.0-1
ii  libkf5kcmutils5  5.70.0-1
ii  libkf5kdelibs4support5   5.70.0-2
ii  libkf5kiocore5   5.70.1-1
ii  libkf5kiofilewidgets55.70.1-1
ii  libkf5kiowidgets55.70.1-1
ii  libkf5newstuff5  5.70.0-1
ii  libkf5notifications5 5.70.0-1
ii  libkf5notifyconfig5  5.70.0-1
ii  libkf5package5   5.70.0-1
ii  libkf5parts5 5.70.0-1
ii  libkf5plasma55.70.1-1
ii  libkf5plasmaquick5   5.70.1-1
ii  libkf5quickaddons5   5.70.0-1
ii  libkf5runner55.70.0-1
ii  libkf5service-bin5.70.0-1
ii  libkf5service5   5.70.0-1
ii  libkf5solid5 5.70.0-1
ii  libkf5sonnetui5  5.70.0-1
ii  libkf5wallet-bin 5.70.0-1
ii  libkf5wallet55.70.0-1
ii  libkf5widgetsaddons5 5.70.0-1
ii  libkf5windowsystem5  5.70.0-1
ii  libkf5xmlgui55.70.0-1
ii  libkfontinst5 

Bug#948316: News pushed

[Angel Abad]

Hi Russ, I pushed a NEWS file, so I think you could do release
new package.

What tool do you use for packaging? git-debrebase? I used to use 
gbp, so I will take a look at git-debrebase and learn it.

Thanks!


signature.asc
Description: PGP signature

Bug#948316: MIA?

[Angel Abad]

On Mon, Feb 03, 2020 at 11:48:45PM -0800, Russ Allbery wrote:
> Angel Abad  writes:
> > On Tue, Jan 28, 2020 at 09:35:15PM +0800, Yao-Po Wang wrote:
> 
> >> Sorry for the late reply and I did not use the package a long time. How
> >> can I transfer the owner to you?
> 
> > Hi, Russ, you have a functional package, do you want to maintain yadm on
> > Debian?
> 
> > If dont I can take care of yadm.
> 
> I can maintain it and have a functional package, although I'd love some
> help.  Happy to have someone else update it when I'm busy!
> 
> I've pushed my branch to debian/master in the Salsa repository.  It's
> based on the current master branch, although I usually use the DEP-14
> branch naming, so normally I'd delete the master branch if that also works
> for you.
> 
> I think the one thing that needs to be done before uploading to Debian
> unstable is to write a NEWS.Debian file telling people they need to run
> yadm upgrade (and upgrade Maintainer and Uploaders).  I will be able to
> get to that in the next couple of days, or happy for someone else to do
> it.

Cool, we can co-maintain the package. I will try to write a NEWS.Debian file
this week.

Cheers!

> -- 
> Russ Allbery (r...@debian.org)  <https://www.eyrie.org/~eagle/>


signature.asc
Description: PGP signature

Bug#948316: MIA?

[Angel Abad]

On Tue, Jan 28, 2020 at 09:35:15PM +0800, Yao-Po Wang wrote:
> Hi Angel,
> 
> Sorry for the late reply and I did not use the package a long time. How can
> I transfer the owner to you?

Hi, Russ, you have a functional package, do you want to maintain yadm on Debian?

If dont I can take care of yadm.

Cheers!

> br,
> yp
> 
> On Tue, Jan 28, 2020, 01:00 Angel Abad  wrote:
> 
> > It seems that Yao-Po Wang is mia, so, could we adopt this package?
> >
> > Thanks!
> >


signature.asc
Description: PGP signature

Bug#948316: MIA?

[Angel Abad]

It seems that Yao-Po Wang is mia, so, could we adopt this package?

Thanks!


signature.asc
Description: PGP signature

Bug#912865: News?

[Angel Abad]

Ok, thanks for the update.

El jue., 23 ene. 2020 a las 9:24, Birger Schacht ()
escribió:

> Hi Angel,
>
> mako is in NEW, waiting for review from ftp masters.
>
> cheers,
> Birger
>
> On 1/23/20 9:00 AM, Angel Abad wrote:
> > Hi, there are news about this ITP, I can help you to package it.
> >
> > I want to use mako on my systems.
> >
> > Thanks!
> >
>


-- 
Angel Abad
an...@debian.org | angela...@ubuntu.com | angela...@gmail.com
http://www.pastelero.net
FPR: 4A08 9719 1621 CCF7 FBEE  F752 A6D5 8816 010A 1096

Bug#912865: News?

[Angel Abad]

Hi, there are news about this ITP, I can help you to package it.

I want to use mako on my systems.

Thanks!


signature.asc
Description: PGP signature

Bug#948316: Please upgrade package

[Angel Abad]

I use yadm too, please upgrade it, I could help you too.

Thanks in advance!


signature.asc
Description: PGP signature

Bug#946775: any news about this itp?

[Angel Abad]

On Sun, Dec 29, 2019 at 07:03:02PM +0100, Jonas Meurer wrote:
> Hey Angel,
> Angel Abad:
> > Hi, any news about this itp?
> > 
> > Are you working on it?
> 
> the wofi package is almost ready for upload, will do so shortly ;)
> 
> You find the packaging repo at https://salsa.debian.org/swaywm-team/wofi

Great, thanks for the info!

If I can help you with packaging or uploading, please tell me.

Cheers,

> Cheers
>  jonas
> 
> 





signature.asc
Description: PGP signature

Bug#946775: any news about this itp?

[Angel Abad]

Hi, any news about this itp?

Are you working on it?

Cheers,


signature.asc
Description: PGP signature

Bug#946087: Please move the VCS to the DPMT Salsa group

[Angel Abad]

Hi, repo move has been requested, you can track here:

https://salsa.debian.org/salsa/support/issues/182

Cheers

On Tue, Dec 03, 2019 at 03:26:37PM -0500, Louis-Philippe Véronneau wrote:
> Package: src:polib
> Severity: wishlist
> 
> Dear maintainers,
> 
> The current VCS for this package is under the /debian group in Salsa,
> although this package is maintained by the DPMT.
> 
> DPMT policy state that:
> 
> Git repositories live on Salsa under the url
> g...@salsa.debian.org:python-team/modules/.git
> 
> Would it be possible to move it over there? I'd have done it myself
> since I technically have the permissions to do so, but I thought I'd ask
> first :)
> 
> If you don't have time, I'll be happy to do this for you.
> 
> Cheers,
> 
> -- 
>   ⢀⣴⠾⠻⢶⣦⠀
>   ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
>   ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
>   ⠈⠳⣄
> 





signature.asc
Description: PGP signature

Bug#934922: clevis: Reference to non-existant clevis-decrypt-http

[Jesus Angel]

Package: clevis-dracut
Version: 11-2
Followup-For: Bug #934922

Dear Maintainer,

This bug hasn't been fixed yet. As a workarround you can edit 
/usr/lib/dracut/modules.d/60clevis/module-setup.sh and change line 39 this way:

39c39
< clevis-decrypt-http \
---
> cryptsetup \

You have to replace clevis-decrypt-http with cryptsetup as shown above. Maybe 
you can just delete the clevis-decrypt-http line as I think cryptsetup is not 
used to open the Luks device, but systemd-cryptsetup is used instead.

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

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

Versions of packages clevis-dracut depends on:
ii  clevis-systemd  11-2
ii  dracut-network  048+80-2

clevis-dracut recommends no packages.

clevis-dracut suggests no packages.

-- no debconf information

Bug#207434: Kuule arviointisi.

[Recas Lopez, Miguel Angel]

From: Recas Lopez, Miguel Angel
Sent: Sunday, November 3, 2019 11:20 PM
Subject: Kuule arviointisi.

Työntekijöiden arvio sinulle.
 Työntekijän arviointi on jätetty sinulle. Suorita seuraavat vaiheet 
tarkistaaksesi ja vahvistaaksesi arvio:

  1. Avaa selain osoitteeseen: https://appriasialforstaff.qwkcheckout.com/
  2. Syötä sivulle käyttäjänimesi, sähköpostiosoitteesi ja salasanasi.
  3. lisätietoja lähetetään postilaatikkoosi kohtaan Valitse viimeisin 
päivämäärä avattavasta luetteloruudusta.
  4. Etsi "Työntekijöiden kuittaus" -osa.
  5. Vahvista arviointi valitsemalla yksi kolmesta (3) vaihtoehdosta 
työntekijän kuittauksen osassa.
  6. Valitse Tallenna-painike.



























































































































































































































This e-mail (including attachments) is confidential and may be privileged. 
Please delete if obtained in error and email confirmation to the sender. Thank 
you for your cooperation.

Bug#833879: (no subject)

[Angel Abad]

Hi, I want to package qsyncthingtray.

Any advance on this?

Do yo want to maintain the package?

Thanks!


signature.asc
Description: PGP signature

Bug#934648: Acknowledgement (nvidia-kernel-dkms: Nvidia 418.74 does not build with kernel 5.2.0 (put_user_pages))

[Miguel Angel Rojas]

Hi all,

It seems the problem is fixed with the new release (418.88)

Thanks


On Tue, Aug 13, 2019 at 12:42 AM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 934648:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934648.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> As you requested using X-Debbugs-CC, your message was also forwarded to
>   mianro...@gmail.com
> (after having been given a Bug report number, if it did not have one).
>
> Your message has been sent to the package maintainer(s):
>  Debian NVIDIA Maintainers 
>
> If you wish to submit further information on this problem, please
> send it to 934...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 934648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934648
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#933668: Doesn't build against libecal-2.0

[Angel Abad]

Hi, thanks a lot for the patch, Im on holidays, so I will try to take a
look next week.

Cheers,

El jue., 1 ago. 2019 a las 18:30, Iain Lane ()
escribió:

> Package: src:almanah
> Version: 0.11.1-2
> Severity: wishlist
> Tags: patch upstream
>
> Control: block 933577 by -1
>
> Hi,
>
> This is in experimental-NEW at the minute, but you can grab the packages
> out of evolution-data-server Vcs-Git to test this. tl;dr is that ecal
> broke API with this release. There are patches upstream which I grabbed
> and applied to the Debian package (untested though). Diff attached for
> you to review. If you wanted to upload to experimental now that would be
> OK, or you can wait until we're ready to go to unstable - at which point
> I'll raise the severity of this bug.
>
> Cheers,
>
> --
> Iain Lane  [ i...@orangesquash.org.uk ]
> Debian Developer   [ la...@debian.org ]
> Ubuntu Developer   [ la...@ubuntu.com ]
>


-- 
Angel Abad
an...@debian.org | angela...@ubuntu.com | angela...@gmail.com
https://angelabad.me
FPR: 4A08 9719 1621 CCF7 FBEE  F752 A6D5 8816 010A 1096

Bug#934648: nvidia-kernel-dkms: Nvidia 418.74 does not build with kernel 5.2.0 (put_user_pages)

[Miguel Angel]

Package: nvidia-kernel-dkms
Version: 418.74-1
Severity: normal
Tags: a11y

Dear Maintainer,


Nvidia 418.74 fails to compile with kernel 5.2.0 after kernel upgrade,
therefore nvidia modules cannot be loaded and X system is not working.

It seems it may be related to put_user_pages() according to DKMS
compilation log (/var/lib/dkms/nvidia-current/418.74/build/make.log

-- Package-specific info:
uname -a:
Linux drizzt 5.2.0-2-amd64 #1 SMP Debian 5.2.7-1 (2019-08-07) x86_64 GNU/Linux

/proc/version:
Linux version 5.2.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 8.3.0 
(Debian 8.3.0-19)) #1 SMP Debian 5.2.7-1 (2019-08-07)

lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104 [GeForce GTX 
760] [10de:1187] (rev a1) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. GK104 [GeForce GTX 760] [1043:847a]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel modules: nvidia

dmesg:

Device node permissions:
video:x:44:sddm,miguel

OpenGL and NVIDIA library files installed:
-rw-r--r-- 1 root root 1337 Jul  2  2018 /etc/X11/xorg.conf
lrwxrwxrwx 1 root root   15 Feb 13 23:31 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   51 Feb 13 23:31 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so.1
lrwxrwxrwx 1 root root   50 Feb 13 23:31 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   50 Feb 13 23:31 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   54 Feb 13 23:31 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   54 Feb 13 23:31 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   44 Feb 13 23:31 
/etc/alternatives/glx--libGLX_indirect.so.0-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0
lrwxrwxrwx 1 root root   44 Feb 13 23:31 
/etc/alternatives/glx--libGLX_indirect.so.0-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0
lrwxrwxrwx 1 root root   38 Feb 13 23:31 
/etc/alternatives/glx--libglxserver_nvidia.so -> 
/usr/lib/nvidia/libglxserver_nvidia.so
lrwxrwxrwx 1 root root   51 Feb 13 23:31 
/etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1
lrwxrwxrwx 1 root root   42 Feb 13 23:31 
/etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> 
/etc/nvidia/nvidia-blacklists-nouveau.conf
lrwxrwxrwx 1 root root   36 Feb 13 23:31 
/etc/alternatives/glx--nvidia-bug-report.sh -> 
/usr/lib/nvidia/nvidia-bug-report.sh
lrwxrwxrwx 1 root root   39 Feb 13 23:31 
/etc/alternatives/glx--nvidia-drm-outputclass.conf -> 
/etc/nvidia/nvidia-drm-outputclass.conf
lrwxrwxrwx 1 root root   28 Feb 13 23:31 
/etc/alternatives/glx--nvidia-load.conf -> /etc/nvidia/nvidia-load.conf
lrwxrwxrwx 1 root root   32 Feb 13 23:31 
/etc/alternatives/glx--nvidia-modprobe.conf -> /etc/nvidia/nvidia-modprobe.conf
lrwxrwxrwx 1 root root   29 Feb 13 23:31 
/etc/alternatives/glx--nvidia_drv.so -> /usr/lib/nvidia/nvidia_drv.so
lrwxrwxrwx 1 root root   23 May 15 11:21 /etc/alternatives/nvidia -> 
/usr/lib/nvidia/current
lrwxrwxrwx 1 root root   59 May 15 11:21 
/etc/alternatives/nvidia--libEGL_nvidia.so.0-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/current/libEGL_nvidia.so.0
lrwxrwxrwx 1 root root   62 May 15 11:21 
/etc/alternatives/nvidia--libGLESv2_nvidia.so.2-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/current/libGLESv2_nvidia.so.2
lrwxrwxrwx 1 root root   62 May 15 11:21 
/etc/alternatives/nvidia--libGLESv2_nvidia.so.2-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/current/libGLESv2_nvidia.so.2
lrwxrwxrwx 1 root root   59 May 15 11:21 
/etc/alternatives/nvidia--libGLX_nvidia.so.0-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/current/libGLX_nvidia.so.0
lrwxrwxrwx 1 root root   59 May 15 11:21 
/etc/alternatives/nvidia--libGLX_nvidia.so.0-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/current/libGLX_nvidia.so.0
lrwxrwxrwx 1 root root   46 May 15 11:21 
/etc/alternatives/nvidia--libglxserver_nvidia.so -> 
/usr/lib/nvidia/current/libglxserver_nvidia.so
lrwxrwxrwx 1 root root   59 May 15 11:21 
/etc/alternatives/nvidia--libnvidia-cfg.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/current/libnvidia-cfg.so.1
lrwxrwxrwx 1 root root   58 May 15 11:21 
/etc/alternatives/nvidia--libnvidia-ml.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/current/libnvidia-ml.so.1
lrwxrwxrwx 1 

Bug#909218: nvidia-xconfig: Files section missing ModulePath entries break GLX upon installing libgl1-nvidia-glx (required by Steam)

[Miguel Angel Vilela]

Please find logs attached.

It appears only an empty or missing xorg.conf will cause the issue with
xflock4.
I tried before a file with only the Files section, and today I tried also
with both sections (with-files) as well as without Files, and again and
empty xorg.conf

Thanks to you!
Miguel


On Sun, Sep 30, 2018 at 3:14 PM Andreas Beckmann  wrote:

> PS: can you repeat the xflock4 test with the working minimal xorg.conf,
> too? Including the sleep+stop trick, to produce a well matching logfile?
>
> Thanks,
>
> Andreas
>


-- 
There are 10 types of geeks: 1s and 0s.

X.Org X Server 1.20.1
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.9.0-7-amd64 x86_64 Debian
Current Operating System: Linux rapture 4.18.0-1-amd64 #1 SMP Debian 4.18.6-1 
(2018-09-06) x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-1-amd64 
root=UUID=7e47da94-60c7-43de-aa1b-8f2e4bf73be8 ro nomodeset net.ifnames=0 
biosdevname=0
Build Date: 17 August 2018  08:05:00PM
xorg-server 2:1.20.1-1 (https://www.debian.org/support) 
Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct  1 22:54:18 2018
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(==) No Layout section.  Using the first Screen section.
(==) No screen section available. Using defaults.
(**) |-->Screen "Default Screen Section" (0)
(**) |   |-->Monitor ""
(==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
(==) Automatically adding devices
(==) Automatically enabling devices
(==) Automatically adding GPU devices
(==) Max clients allowed: 256, resource mask: 0x1f
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
Entry deleted from font path.
(==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
(**) ModulePath set to "/usr/lib/xorg/modules/linux,/usr/lib/xorg/modules"
(II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
(II) Loader magic: 0x557345da3de0
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 24.0
X.Org XInput driver : 24.1
X.Org Server Extension : 10.0
(++) using VT number 7

(II) systemd-logind: logind integration requires -keeptty and -keeptty was not 
provided, disabling logind integration
(II) xfree86: Adding drm device (/dev/dri/card0)
(--) PCI:*(9@0:0:0) 10de:1b81:1043:8598 rev 161, Mem @ 0xf600/16777216, 
0xe000/268435456, 0xf000/33554432, I/O @ 0xd000/128, BIOS @ 
0x/131072
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/linux/libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Server Extension
(II) NVIDIA GLX Module  390.87  Tue Aug 21 16:10:56 PDT 2018
(II) Applying OutputClass "nvidia" to /dev/dri/card0
loading driver: nvidia
(==) Matched nvidia as autoconfigured driver 0
(==) Matched nouveau as autoconfigured driver 1
(==) Matched nv as autoconfigured driver 2
(==) Matched modesetting as autoconfigured driver 3
(==) Matched fbdev as autoconfigured driver 4
(==) Matched vesa as autoconfigured driver 5
(==) Assigned the driver to the xf86ConfigLayout
(II) LoadModule: "nvidia"
(II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Video Driver
(II) LoadModule: "nouveau"
(II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
(II) Module nouveau: vendor="X.Org Foundation"
compiled for 1.20.0, module version = 1.0.15
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 24.0
(II) LoadModule: "nv"
(WW) Warning, couldn't open module nv
(EE) Failed to load module "nv" (module does not exist, 0)
(II) LoadModule: "modesetting"
(II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
(II) Module modesetting: vendor="X.Org Foundation"
compiled for 1.20.1, module version = 1.20.1
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 24.0
(II) LoadModule: "fbdev"
(II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
(II) Module fbdev: vendor="X.Org Foundation"
compiled for 1.20.0, module version = 0.5.0
Module class: X.Org Video 

Bug#892546: Debian Bug report logs - #892546 gosa: fails to decrypt openssl encrypted password

[Angel Ana María Matute]

*Hi, I have done:1. cp /etc/gosa/gosa.conf.orig /etc/gosa/gosa.conf**2. sh
-c “cat /dev/null > /etc/gosa/gosa.secrets” - and also try rm
 /etc/gosa/gosa.secrets -3. create /bin/gosa-encrypt-passwords -as the
correct encryption method said in link-4. service apache2 reloadbut i get
the same problem: "Error while connecting to LDAP: Could not bind to
cn=gosa-admin,ou=ldap-access,dc=skole,dc=skolelinux,dc=no (unauthenticated
bind (DN with no password) disallowed, while operating on using LDAP server
ldap://ldap.intern)"something is still not working, what is it??The problem
should be in:a. How i do the step: use plan passsord in gosa.conf?b. Must
/bin/gosa-encrypt-passwords** have special permissions? I set it even
777.c. How i set web-server configuration**?i need gosa just tu creat user
with CSVThanks.*

Bug#879712: (no subject)

[Angel Abad]

After this release if you want we can co-maintain the package
ir xmpp or dpmt team.

Cheers!


signature.asc
Description: PGP signature

Bug#879712: (no subject)

[Angel Abad]

Hi, sorry for my delay!

This week I hope to prepare a release for experimental, with
python 2 and 3 support, before the upload I will send you
package and source if you want to test it.

Thanks a log!


signature.asc
Description: PGP signature

Bug#879712: Update wokkel?

[Angel Abad]

Hi, at the moment I have no response from the upstream developer.

Cheers

2018-01-02 11:40 GMT+01:00 W. Martin Borgert <deba...@debian.org>:

> On 2017-10-27 17:26, Angel Abad wrote:
> > Because there is no official release with these changes, I will
> > write upstream developer and I will tell you.
>
> Was there any outcome? TIA!
>



-- 
Angel Abad
an...@debian.org | angela...@ubuntu.com | angela...@gmail.com
http://www.pastelero.net
FPR: 4A08 9719 1621 CCF7 FBEE  F752 A6D5 8816 010A 1096

Bug#885819: almanah: Depends on gconf

[Angel Abad]

Thanks for the info, I will talk to upstream developer.

Cheers

On Fri, Dec 29, 2017 at 10:05:11PM -0500, Jeremy Bicha wrote:
> Source: almanah
> Version: 0.11.1-1
> Severity: important
> User: pkg-gnome-maintain...@lists.alioth.debian.org
> Usertags: oldlibs gconf
> Tags: sid buster
> 
> Your package depends or build-depends on gconf, but gconf will be
> removed from Debian soon.
> 
> gconf's last release was about 5 years ago. It has been replaced by
> gsettings (provided in Debian by source glib2.0 )
> 
> Someone should look into packaging a git snapshot since it looks like
> this app has been ported from gconf to gsettings in git master.
> 
> References
> --
> https://developer.gnome.org/gio/stable/ch34.html
> https://developer.gnome.org/gio/stable/GSettings.html
> 
> On behalf of the Debian GNOME team,
> Jeremy Bicha


signature.asc
Description: PGP signature

Bug#823373: audio leveller stuck

[Chalilodimun Angel]

Hello,

It's the same here.
The audio leveller is stuck, I can't move it at all. I can't work on my
karaoke, it's really annoying. (I'm on Mac, Aegisub 3.2.2)

Chalilo

Bug#882249: Welcome to Amazon - congrats Michel uiTF

[Michel Angel]

Thank you.! What did i win

> On Nov 20, 2017, at 12:14 PM, thank you  wrote:
> 
> A Special Thankyou!
> 
> claim your amazonShopperReward
> 
> Thankyou for participating in our amazonquestionnaire. your feedback
> 
> about Amazon will earn you a special reward.
> 
> Thankyou for your opinion.
> 
> 
> Toberemoved fromreceivingfuturemail justgo here. 
> PO box 971, Reno NV 89504 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Package: xrdp Version: 0.9.4-1 Severity: wishlist  Hi, the attached script 
> works for me to compile the xrdp pulse modules any time needed. Please test 
> and consider to ship it. In case shipping it is considered useful, please 
> update d/README.Debian accordingly. Wolfgang
> 

Bug#882051: Welcome To Amazon..QVrMZV

[Michel Angel]

I won the 50 dollards why am i getting a final notice. Do you want me to 
returned the 50 dollars. I have a credit card. Do you want the numbers

> On Nov 18, 2017, at 1:17 AM, final notice  wrote:
> 
> important information
> 
> 
> 
>
> 
>   
> 
>   
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Package: release.debian.org Severity: normal User: 
> release.debian@packages.debian.org Usertags: binnmu debhelper 10.10.7 
> fixed a regression in debhelper 10.10.6 that prevented dbgsym packages from 
> being generated. There are probably several packages affected but I am not 
> aware of any easy mechanism to determine which packages were built against 
> debhelper 10.10.6 so I've just included a binNMU request for the two packages 
> I'm aware of that were definitely affected by this. debhelper (10.10.7) 
> unstable; urgency=3Dmedium * dh_strip: Fix a regression that caused debug 
> symbols for executables to be discarded instead of included into debug 
> packages. nmu xdg-desktop-portal_0.8-3 . amd64 arm64 i386 mips64el mips 
> powerpc ppc64= el s390x . unstable . -m "Rebuild to include dbgsym packages 
> after debhelpe= r 10.10.7 fix" nmu xdg-desktop-portal-gtk_0.7-3 . amd64 arm64 
> i386 mips64el mips powerpc p= pc64el s390x . unstable . -m "Rebuild to 
> include dbgsym packages after debh= elper 10.10.7 fix" --=20 bye, pabs 
> https://wiki.debian.org/PaulWise

Bug#882020: Welcome To Amazon. BQPg5p

[Michel Angel]

thank you..!! i won 50 dollards..

On Nov 19, 2017 11:15 AM, "important notice"  wrote:

> important information
>
>
> 
>
>
> 
>
>
> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Your message dated Sun, 19 Nov 2017 15:06:44 + with message-id and
> subject line Bug#882020: fixed in socat 1.7.3.2-2 has caused the Debian Bug
> report #882020, regarding socat: Fails to build on Hurd to be marked as
> done. This means that you claim that the problem has been dealt with. If
> this is not the case it is now your responsibility to reopen the Bug report
> if necessary, and/or fix the problem forthwith. (NB: If you are a system
> administrator and have no idea what this message is talking about, this may
> indicate a serious mail system misconfiguration somewhere. Please contact
> ow...@bugs.debian.org immediately.) -- 882020:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882020 Debian Bug
> Tracking System Contact ow...@bugs.debian.org with problems
>
> -- Mensaje reenviado --
> From: Andreas Henriksson 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Fri, 17 Nov 2017 18:59:28 +0100
> Subject: socat: Fails to build on Hurd
> Package: socat
> Version: 1.7.3.2-1
> Severity: normal
> Tags: patch
>
> Dear Maintainer,
>
> It seems socat fails to build on hurd. This in turn affects util-linux
> which has a build-dependency on socat for tests. Rather than excluding
> socat specifically on hurd, I think it would be better to have socat
> building.
>
> Not a hurd expert myself so took the simplest possible way forward
> in the attached patch which I've confirmed to build on the hurd
> porterbox. Hopefully an actual hurd porter can improve on it if needed
> (and actually runtime test the results).  See also comments in patch
> header.
>
> Regards,
> Andreas Henriksson
>
>
>
> -- Mensaje reenviado --
> From: Laszlo Boszormenyi 
> To: 882020-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Sun, 19 Nov 2017 15:06:44 +
> Subject: Bug#882020: fixed in socat 1.7.3.2-2
> Source: socat
> Source-Version: 1.7.3.2-2
>
> We believe that the bug you reported is fixed in the latest version of
> socat, which is due to be installed in the Debian FTP archive.
>
> A summary of the changes between this version and the previous one is
> attached.
>
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 882...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Laszlo Boszormenyi (GCS)  (supplier of updated socat
> package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Format: 1.8
> Date: Sun, 19 Nov 2017 13:56:10 +
> Source: socat
> Binary: socat
> Architecture: source amd64
> Version: 1.7.3.2-2
> Distribution: unstable
> Urgency: medium
> Maintainer: Laszlo Boszormenyi (GCS) 
> Changed-By: Laszlo Boszormenyi (GCS) 
> Description:
>  socat  - multipurpose relay for bidirectional data transfer
> Closes: 882020
> Changes:
>  socat (1.7.3.2-2) unstable; urgency=medium
>  .
>* Update Standards-Version to 4.1.1:
>  - change package priority to optional.
>* Remove dh-autoreconf build dependency.
>  .
>[ Andreas Henriksson  ]
>* Have compat.h define PATH_MAX if undefined (closes: #882020).
> Checksums-Sha1:
>  d986951fb520e3e522e86e2d9fce455312085447 1730 socat_1.7.3.2-2.dsc
>  a8e9b9b3bb47d7997a98bb1dbfa194c03bf2c6d3 9796
> socat_1.7.3.2-2.debian.tar.xz
>  237084697dd4347cccbb31e4709ae685130b5472 552672
> socat-dbgsym_1.7.3.2-2_amd64.deb
>  5f22645ee17761b90c71fb6407f2fdba59a1b565 6558 socat_1.7.3.2-2_amd64.
> buildinfo
>  aa30cac1e1145e57e18495da32670a36cb8c028c 357680 socat_1.7.3.2-2_amd64.deb
> Checksums-Sha256:
>  1872142f251e2bddc750fd033398554625111ab74273fcbad66885367c2d553b 1730
> socat_1.7.3.2-2.dsc
>  f0b62497913019a026deedf6727b9dc54aa4f5ad0ec1a4a298715da9b6456397 9796
> socat_1.7.3.2-2.debian.tar.xz
>  8abdf907256faa11d58a31b0c2256df8e7998c5f49a08cbb2fa4bfaaa8a383bb 552672
> socat-dbgsym_1.7.3.2-2_amd64.deb
>  c34a74e37b5a3de0b84d71b66c7032d2b09aa6cdab553122f35650e96893df6b 6558
> socat_1.7.3.2-2_amd64.buildinfo
>  43075db7598277bdfeca9adf6b43bc6592f2017fdfa3c7d61f923563d7e90853 357680
> 

Bug#879712: Update wokkel?

[Angel Abad]

On Thu, Oct 26, 2017 at 10:49:44AM +0200, W. Martin Borgert wrote:
> Hi Angel and team,

Hi,

> would you mind, if I update wokkel and close #735304 (teams git
> repo) and #879712 (Python 3 support)? I would add myself to
> uploaders, too.

Because there is no official release with these changes, I will
write upstream developer and I will tell you.

I you want to co-maintain wokkel package we could talk about it.

Cheers,

> TIA & Cheers




signature.asc
Description: PGP signature

Bug#862672:

[Angel Abad]

Sorry, in unstable there is 2.9

Cheers

-- 
Angel Abad
an...@debian.org | angela...@ubuntu.com | angela...@gmail.com
http://www.pastelero.net
FPR: 4A08 9719 1621 CCF7 FBEE  F752 A6D5 8816 010A 1096

Bug#862672: unblock: glue/0.13-1

[Angel Abad]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package glue

Hi, the package is unusable beacuse it depends on Jinga2 >=2.7,<2.8,
in testing there is 2.9 and in unstable there is 2.10.

The upstream maintainer changed this dependency to >=2.7,<2.10, and
I updated depends in debian pacakge so, now its usable in testing and
in unstable.

Please see #860169

I attach debdiff

Cheers,

unblock glue/0.13-1

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

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru glue-0.11.1/debian/changelog glue-0.13/debian/changelog
--- glue-0.11.1/debian/changelog2015-05-02 12:37:07.0 +0200
+++ glue-0.13/debian/changelog  2017-05-15 13:39:14.0 +0200
@@ -1,3 +1,10 @@
+glue (0.13-1) unstable; urgency=medium
+
+  * New upstream version 0.13 (Closes: #860169)
+  * debian/py3dist-overrides: Add override for Jinja2
+
+ -- Angel Abad <an...@debian.org>  Mon, 15 May 2017 13:39:14 +0200
+
 glue (0.11.1-2) unstable; urgency=medium
 
   * Now package uses python 3 (Closes: #782921)
diff -Nru glue-0.11.1/debian/py3dist-overrides 
glue-0.13/debian/py3dist-overrides
--- glue-0.11.1/debian/py3dist-overrides1970-01-01 01:00:00.0 
+0100
+++ glue-0.13/debian/py3dist-overrides  2017-05-15 13:33:02.0 +0200
@@ -0,0 +1 @@
+Jinja2 python3-jinja2 (>= 2.7), python3-jinja2 (<< 2.10)
diff -Nru glue-0.11.1/docs/changelog.rst glue-0.13/docs/changelog.rst
--- glue-0.11.1/docs/changelog.rst  2015-03-29 23:05:00.0 +0200
+++ glue-0.13/docs/changelog.rst2017-05-15 13:05:55.0 +0200
@@ -1,6 +1,14 @@
 Changelog
 =
 
+0.13
+^^
+* Update Jinja version
+
+0.12
+^^
+* Update Jinja version
+
 0.11.1
 ^^
 * Fix packaging issue. #192
diff -Nru glue-0.11.1/glue/__init__.py glue-0.13/glue/__init__.py
--- glue-0.11.1/glue/__init__.py2015-03-29 23:06:03.0 +0200
+++ glue-0.13/glue/__init__.py  2017-05-15 13:06:00.0 +0200
@@ -1 +1 @@
-__version__ = '0.11.1'
+__version__ = '0.13'
diff -Nru glue-0.11.1/glue.egg-info/PKG-INFO glue-0.13/glue.egg-info/PKG-INFO
--- glue-0.11.1/glue.egg-info/PKG-INFO  2015-03-29 23:23:13.0 +0200
+++ glue-0.13/glue.egg-info/PKG-INFO2017-05-15 13:06:43.0 +0200
@@ -1,6 +1,6 @@
 Metadata-Version: 1.1
 Name: glue
-Version: 0.11.1
+Version: 0.13
 Summary: Glue is a simple command line tool to generate sprites.
 Home-page: http://github.com/jorgebastida/glue
 Author: Jorge Bastida
diff -Nru glue-0.11.1/glue.egg-info/requires.txt 
glue-0.13/glue.egg-info/requires.txt
--- glue-0.11.1/glue.egg-info/requires.txt  2015-03-29 23:23:13.0 
+0200
+++ glue-0.13/glue.egg-info/requires.txt2017-05-15 13:06:43.0 
+0200
@@ -1,2 +1,2 @@
 Pillow>=2.2.2
-Jinja2>=2.7,<2.8
\ No hay ningún carácter de nueva línea al final del fichero
+Jinja2>=2.7,<2.10
diff -Nru glue-0.11.1/PKG-INFO glue-0.13/PKG-INFO
--- glue-0.11.1/PKG-INFO2015-03-29 23:23:13.0 +0200
+++ glue-0.13/PKG-INFO  2017-05-15 13:06:43.0 +0200
@@ -1,6 +1,6 @@
 Metadata-Version: 1.1
 Name: glue
-Version: 0.11.1
+Version: 0.13
 Summary: Glue is a simple command line tool to generate sprites.
 Home-page: http://github.com/jorgebastida/glue
 Author: Jorge Bastida
diff -Nru glue-0.11.1/setup.cfg glue-0.13/setup.cfg
--- glue-0.11.1/setup.cfg   2015-03-29 23:23:13.0 +0200
+++ glue-0.13/setup.cfg 2017-05-15 13:06:43.0 +0200
@@ -1,5 +1,4 @@
 [egg_info]
 tag_build = 
 tag_date = 0
-tag_svn_revision = 0
 
diff -Nru glue-0.11.1/setup.py glue-0.13/setup.py
--- glue-0.11.1/setup.py2015-03-29 23:13:51.0 +0200
+++ glue-0.13/setup.py  2017-05-15 13:06:05.0 +0200
@@ -4,7 +4,7 @@
 
 install_requires=[
 'Pillow>=2.2.2',
-'Jinja2>=2.7,<2.8',
+'Jinja2>=2.7,<2.10',
 ]
 
 tests_require=[
@@ -24,7 +24,7 @@
 
 setup(
 name='glue',
-version='0.11.1',
+version='0.13',
 url='http://github.com/jorgebastida/glue',
 license='BSD',
 author='Jorge Bastida',

Bug#860169:

[Angel Abad]

If you execute glue-sprite on terminal:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
655, in _build_master
ws.require(__requires__)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
963, in require
needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
854, in resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (Jinja2 2.9.5
(/usr/lib/python3/dist-packages), Requirement.parse('Jinja2<2.8,>=2.7'),
{'glue'})

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/glue-sprite", line 5, in 
from pkg_resources import load_entry_point
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
3019, in 
@_call_aside
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
3003, in _call_aside
f(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
3032, in _initialize_master_working_set
working_set = WorkingSet._build_master()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
657, in _build_master
return cls._build_from_requirements(__requires__)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
670, in _build_from_requirements
dists = ws.resolve(reqs, Environment())
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
849, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'Jinja2<2.8,>=2.7' distribution was
not found and is required by glue

-- 
Angel Abad
an...@debian.org | angela...@ubuntu.com | angela...@gmail.com
http://www.pastelero.net
FPR: 4A08 9719 1621 CCF7 FBEE  F752 A6D5 8816 010A 1096

Bug#856887: sddm default configuration is not properly taken

[Miguel Angel]

Package: sddm
Version: 0.13.0-1
Severity: important
Tags: upstream

Dear Maintainer,

sddm default "blue configuration" is not taking properly when the
packages is upgraded to version 0.14 or above (bad theme and wrong
configuration)

Downgrading to version 0.13 makes sddm usable again with the
default theme properly setup. Curious thing is when you lock your screen
with 0.14, the right blue default theme is displayed (?), but not in the logout.

If you need screenshots, just let me know, but it is very easy to
reproduce.

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

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

Versions of packages sddm depends on:
ii  adduser 3.115
ii  debconf [debconf-2.0]   1.5.60
ii  libc6   2.24-9
ii  libgcc1 1:6.3.0-8
ii  libpam0g1.1.8-3.5
ii  libqt5core5a5.7.1+dfsg-3+b1
ii  libqt5dbus5 5.7.1+dfsg-3+b1
ii  libqt5gui5  5.7.1+dfsg-3+b1
ii  libqt5network5  5.7.1+dfsg-3+b1
ii  libqt5qml5  5.7.1-2
ii  libqt5quick55.7.1-2
ii  libstdc++6  6.3.0-8
ii  libsystemd0 232-19
ii  libxcb-xkb1 1.12-1
ii  libxcb1 1.12-1
ii  qml-module-qtquick2 5.7.1-2
ii  sddm-theme-breeze [sddm-theme]  4:5.8.4-1

Versions of packages sddm recommends:
ii  libpam-systemd  232-19

Versions of packages sddm suggests:
ii  libpam-kwallet5  5.8.4-1

-- debconf information:
* shared/default-x-display-manager: sddm
  sddm/daemon_name: /usr/bin/sddm

Bug#826462: RFA: screenruler

[Siegfried-Angel Gevatter Pujals]

Package: wnpp
Severity: normal

This package is up to adoption, feel free to take over if you are interested in 
maintaining it.

Bug#826464: RFA: vilistextum

[Siegfried-Angel Gevatter Pujals]

Package: wnpp
Severity: normal

This package is up for adoption, feel free to take it over.

Bug#826461: RFA: open-invaders

[Siegfried-Angel Gevatter Pujals]

Package: wnpp
Severity: normal

Hi,

If someone is interested in this package feel free to take it over, I don't 
anticipate doing any more work on it. Note that upstream is no longer actively 
developing this game, so it shouldn't require much work.

Bug#816478: RM: dajaxice -- ROM; unmaintained by upstream

[Angel Abad]

Package: ftp.debian.org
Severity: normal

This package is a python library for django, at this moment
upstream developer only supports django 1.7 (1.9 in unstable)
and the pacakge is unmaintained.

This package only has one reverse depends and this package is now
removed from unstable too.

python-django-dajaxice
Reverse Depends:
  python-django-dajax (removed from unstable)

Cheers,

Bug#816364: RM: django-dajax -- ROM; unmaintained by upstream

[Angel Abad]

Package: ftp.debian.org
Severity: normal

This package is a python library for django, at this moment
upstream developer only supports django 1.7 (1.9 in unstable)
and the pacakge is unmaintainer.

from https://github.com/jorgebastida/django-dajax:
"From v0.9.2 this project is not going to accept new features.
In order to not break existing projects using this library,
django-dajax and django-dajaxice will be maintained until django
1.8 is released."

The package has no reverse depends.

Cheers,

Bug#802930: ITP: libtest-tempdir-tiny-perl -- Temporary directories that stick around when tests fail

[Angel Abad]

Package: wnpp
Owner: Angel Abad <an...@debian.org>
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libtest-tempdir-tiny-perl
  Version : 0.004
  Upstream Author : David Golden <dagol...@cpan.org>
* URL : https://metacpan.org/release/Test-TempDir-Tiny
* License : Apache-2.0
  Programming Lang: Perl
  Description : Temporary directories that stick around when tests fail

Test::TempDir::Tiny works with Test::More to create temporary directories
that stick around if tests fail.

It is loosely based on Test::TempDir, but with less complexity, greater
portability and zero non-core dependencies.

Bug#802927: ITP: awslogs -- AWS CloudWatch logs for Humans

[Angel Abad]

Package: wnpp
Owner: Angel Abad <an...@debian.org>
Severity: wishlist
X-Debbugs-CC: neo2...@gmail.com

* Package name: awslogs
  Version : 0.1.0-1
  Upstream Author : Jorge Bastida <m...@jorgebastida.com>
* URL : https://github.com/jorgebastida/awslogs
* License : BSD-3-clause
  Programming Lang: python
  Description : AWS CloudWatch logs for Humans

awslogs is a simple command line tool for querying groups, streams and
events from Amazon CloudWatch logs. One of the most powerful features
is to query events from several streams and consume them (ordered) in
pseudo-realtime using your favourite tools such as grep.

Bug#799948: Plasma desktop is unable to start (black screen - panic)

[Miguel Angel Rojas]

>
>
> I must first say that I am absolutely not familiar with KDE, the QT
> environment and how it works. But the thread that raises the abort
> doesn't look like it's in the GL libraries code:
>
> Maybe there's some context I'm missing. Forgive me for asking, but are
> you sure this is due to the Nvidia driver packages or glx-alternatives?
>
>
Hi Luca,

But indeed, it is! I conducted the same experiments as Vladimir did with
the same result. Something is wrong with the glx beyond 0.6.x (bad
packaging, new API, new behavior? I don't know). I would recommend to
reproduce as it is very easy to do it and you will see what we are talking
about.

Talking about Bug #799948, is there a reason why sddm user should be
included in video? (because it seems to be the workaround) If so, someone
should notify sddm guys that is somehow required due to new upstream
requirement in nvidia glx packages. We don't have a clear explanation about
it.

Regards

Bug#799948: Plasma desktop is unable to start (black screen - panic)

[Miguel Angel Rojas]

Hi Luca,​

Here you have the report you asked about the plasmashell. I do not know if
it could be related to a configuration issue, but again very easy to
reproduce. Here you have 2 reports (same error in 2 consecutive log on
sessions).

These crashes are related to the plasmashell (I manually fixed the
workaround by adding the sddm user to the video group) but if you remove
it, sddm is the one who crashes.

Hope it helps.
Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f972f7dc940 (LWP 1799))]

Thread 7 (Thread 0x7f9718aeb700 (LWP 1801)):
#0  0x7f9729f6252d in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7f972dfb2252 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f972dfb3ddf in xcb_wait_for_event () from 
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f971ac4c2f9 in ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
#4  0x7f972a64b25e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f972976b0a4 in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#6  0x7f9729f6b06d in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 6 (Thread 0x7f971220c700 (LWP 1806)):
#0  0x7f972a881391 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7f9726d2176d in g_main_context_prepare () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9726d2210b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f9726d222ec in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f972a881e4b in 
QEventDispatcherGlib::processEvents(QFlags) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f972a8282ca in 
QEventLoop::exec(QFlags) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f972a646374 in QThread::exec() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f972ce7b055 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f972a64b25e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f972976b0a4 in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#10 0x7f9729f6b06d in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 5 (Thread 0x7f9709f46700 (LWP 1810)):
#0  0x7f97297717fc in __lll_lock_wait () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#1  0x7f972976d4d4 in _L_lock_986 () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#2  0x7f972976d336 in pthread_mutex_lock () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#3  0x7f972614de90 in ?? () from /usr/lib/x86_64-linux-gnu/libGL.so.1
#4  0x7f972615141e in ?? () from /usr/lib/x86_64-linux-gnu/libGL.so.1
#5  0x7f972615181b in ?? () from /usr/lib/x86_64-linux-gnu/libGL.so.1
#6  0x7f97226fafc0 in ?? () from 
/usr/lib/x86_64-linux-gnu/tls/libnvidia-tls.so.340.93
#7  0x7f9726d654d0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f9726d21cc4 in g_main_context_check () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f9726d22180 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7f9726d222ec in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7f972a881e4b in 
QEventDispatcherGlib::processEvents(QFlags) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f972a8282ca in 
QEventLoop::exec(QFlags) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f972a646374 in QThread::exec() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f972ce7b055 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#15 0x7f972a64b25e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7f972976b0a4 in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#17 0x7f9729f6b06d in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 4 (Thread 0x7f97035c8700 (LWP 1814)):
#0  0x7f9726d221c2 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f9726d222ec in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f972a881e4b in 
QEventDispatcherGlib::processEvents(QFlags) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f972a8282ca in 
QEventLoop::exec(QFlags) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f972a646374 in QThread::exec() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f972ce7b055 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x7f972a64b25e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f972976b0a4 in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#8  0x7f9729f6b06d in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 3 (Thread 0x7f9701d32700 (LWP 1815)):
#0  0x7f972976f08f in pthread_cond_wait@@GLIBC_2.3.2 () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#1  0x7f972f222144 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f972f222189 in ?? () from 

Bug#800938: Bug#799948: Plasma desktop is unable to start (black screen - panic)

[Miguel Angel Rojas]

Hi Luca,

Thanks for the quick answer!

Here you have both report you asked for. Hopefully it will help us to know
where the issue is.

Regards

On Sun, Oct 18, 2015 at 9:43 PM, Luca Boccassi <luca.bocca...@gmail.com>
wrote:

> On Sun, 2015-10-18 at 20:16 +0200, Miguel Angel Rojas wrote:
> > Hi all,
> >
> >
> > Vladimir is right, same issue here. Indeed, It is weird to me not so
> > many people is currently reporting on it, but it is affecting a lot of
> > programs. Something happens when upgrading to version 0.6.x (I agree
> > at this point)
> >
> >
> > plasma-desktop is also unable to start and panic (black screen).If you
> > update-alternative glx fall back to mesa, the desktop runs just fine
> > (of course, without the nvidia drivers)
> >
> >
> > I though it was solved by bug 799948 (ssdm panic too), but again, it
> > is not. At least you can "adduser sddm video" and make ssdm-greater
> > works as a workaround, but plasma-desktop panics still panics after
> > you try to log on.
> >
> >
> >
> > It is very easy to check it. Just install a fresh installation of KDE
> > and nvidia drivers and you will see a beautiful black screen. Let me
> > know if you need additional information but it is quite easy to
> > reproduce
>
> Hi,
>
> Could you please attach the output of:
>
> reportbug --template glx-alternative-nvidia
> reportbug --template nvidia-driver
>
> Kind regards,
> Luca Boccassi
>
>

-- Package-specific info:
Diversions:
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.0.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.0.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2.0.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2.0.0 by glx-diversions
diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by 
glx-diversions
diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by 
glx-diversions
diversion of /usr/lib/libGL.so.1.2 to /usr/lib/mesa-diverted/libGL.so.1.2 by 
glx-diversions
diversion of /usr/lib/libGL.so.1.2.0 to /usr/lib/mesa-diverted/libGL.so.1.2.0 
by glx-diversions
diversion of /usr/lib/libGLESv1_CM.so to /usr/lib/mesa-diverted/libGLESv1_CM.so 
by glx-diversions
diversion of /usr/lib/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/l

Bug#799948: Plasma desktop is unable to start (black screen - panic)

[Miguel Angel Rojas]

Hi all,

Vladimir is right, same issue here. Indeed, It is weird to me not so many
people is currently reporting on it, but it is affecting a lot of programs.
Something happens when upgrading to version 0.6.x (I agree at this point)

plasma-desktop is also unable to start and panic (black screen).If you
update-alternative glx fall back to mesa, the desktop runs just fine (of
course, without the nvidia drivers)

I though it was solved by bug 799948 (ssdm panic too), but again, it is
not. At least you can "adduser sddm video" and make ssdm-greater works as a
workaround, but plasma-desktop panics still panics after you try to log on.

It is very easy to check it. Just install a fresh installation of KDE and
nvidia drivers and you will see a beautiful black screen. Let me know if
you need additional information but it is quite easy to reproduce

Regards

Bug#779551: devtodo: FTBFS, should Build-Depends on libtool-bin

[Angel Abad]

Package: devtodo
Severity: serious

Dear Maintainer,

This package FTBFS, it uses /usr/bin/libtool which is in libtool-bin
package, so, the package should Build-Depends on libtool-bin.

make[1]: Leaving directory '/build/buildd/devtodo-0.1.20'
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/buildd/devtodo-0.1.20'
cp /usr/bin/libtool ./
cp: cannot stat '/usr/bin/libtool': No such file or directory
debian/rules:23: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1

Cheers,

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

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


-- 
Angel Abad
an...@debian.org | angela...@ubuntu.com | angela...@gmail.com
http://www.pastelero.net
FPR: EBF6 080D 59D4 008A DF47  00D4 098D AE47 EE3B C279

Bug#774138: grub-efi-amd64: Update freeze with kernel oops for EFI (2.02~beta2-{18 - 19})

[Axel Angel]

 Was this in the state where things crashed or the working state (but
 with the second issue you mentioned occurring)?

This is the diff between -18 and -19 when nothing crash in both case.
This shows there is a visible change for efibootmgr.

 I think there is a pretty good chance that this is therefore a firmware
 issue. I'd recommend the first thing to try would be to see if an
 updated firmware is available for your system and if so then install it.

You mean the motherboard firmware right? There seem to be only minor
changes according to the changelog of Gigabyte on their website. I'm
always worried about upgrading firmwares, I could give a try though as
a last resort.

 Your kernel stack trace shows that the CPU has tried to execute code
 from a region of RAM which has been marked non-executable when calling
 into the firmware. I'm not familiar enough with EFI to know if
 responsibility for this lies with the firmware or the kernel and have a
 feeling it might be the two in concert.
 
 You might find that adding noexec=off to your kernel command line
 worksaround this issue.

I can give it a try. Question: isn't it dangerous to enable this flag in
normal use? I guess so.

 Sounds like a firmware issue to me, if an upgrade doesn't help I'd
 recommend to start by reporting against efibootmgr.

I thought the issue may be related so I hope I didn't confuse you more
with this information.

 Once you've updated the firmware I think I'd suggest starting by
 reassigning this crash issue to the Linux package (I can help with the
 mechanics of that if you need). The thing about the delete boot entries
 probably ought to start with efibootmgr (I could clone this report, but
 I think a fresh one dedicated to that issue would be better).

Thanks for the help. Let's report it to efibootmgr after I tried the two
things you mentionned above.

Thanks!


signature.asc
Description: Digital signature

Bug#773677: unblock: lightyears/1.4-2

[Siegfried-Angel Gevatter Pujals]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package lightyears

Revision 1.4-2 fixes a patch in 1.4-1 which unconditionally disabled sound
for all users (bug #742473). Several users consider this bug important.

unblock lightyears/1.4-2

-- DEBDIFF

diff -Nru lightyears-1.4/debian/changelog lightyears-1.4/debian/changelog
--- lightyears-1.4/debian/changelog 2011-07-22 01:49:49.0 +0200
+++ lightyears-1.4/debian/changelog 2014-12-21 22:29:04.0 +0100
@@ -1,3 +1,12 @@
+lightyears (1.4-2) unstable; urgency=medium
+
+  * debian/patches/snd_disabled_typo.patch:
+ - Move pygame.mixer to a place where pygame has already started up;
+   it was unconditionally disabling sound. Thanks to Allan Wirth
+   for diagnosing this (Closes: #742473).
+
+ -- Siegfried-Angel Gevatter Pujals rai...@ubuntu.com  Sun, 21 Dec 2014 
22:26:54 +0100
+
 lightyears (1.4-1) unstable; urgency=low
 
   * New upstream version. Some of the changes are:
diff -Nru lightyears-1.4/debian/patches/snd_disabled_typo.patch 
lightyears-1.4/debian/patches/snd_disabled_typo.patch
--- lightyears-1.4/debian/patches/snd_disabled_typo.patch 2011-07-22 
00:34:03.0 +0200
+++ lightyears-1.4/debian/patches/snd_disabled_typo.patch 2014-12-21 
22:26:23.0 +0100
@@ -1,14 +1,29 @@
 Description: Fix typo in variable name
 Author: Siegfried-Angel Gevatter Pujals rai...@ubuntu.com
 
+Index: lightyears-1.4/code/resource.py
+===
 --- lightyears-1.4.orig/code/resource.py
 +++ lightyears-1.4/code/resource.py
-@@ -15,7 +15,7 @@ __snd_cache = dict()
+@@ -14,9 +14,6 @@ __img_cache = dict()
+ __snd_cache = dict()
  __snd_disabled = False
  
- if not pygame.mixer or not pygame.mixer.get_init():
+-if not pygame.mixer or not pygame.mixer.get_init():
 -  __snd__disabled = True
-+  __snd_disabled = True
- 
+-
  DATA_DIR = os.path.abspath(os.path.join(
  os.path.dirname(sys.argv[ 0 ]), data))
+ 
+@@ -88,7 +85,10 @@ def Load_Font(size):
+ 
+ def Load_Sound(name):
+ global __snd_cache, __snd_disabled
+-   
++
++if not pygame.mixer or not pygame.mixer.get_init():
++__snd_disabled = True
++
+ if ( __snd_disabled ):
+ return None
+ 


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

Bug#771468: RFP: libgetopt-argparse -- Perl module for parsing command line arguments inspired from python's argparse

[Axel Angel]

Package: wnpp
Severity: wishlist

* Package name: libgetopt-argparse
  Version : 1.0.4
  Upstream Author : Mytram mytr...@gmail.com
* URL : http://search.cpan.org/dist/Getopt-ArgParse/
* License : same as Perl itself (Artistic)
  Programming Lang: Perl
  Description : Perl module for parsing command line arguments inspired 
from python's argparse

Getopt::ArgParse is a Perl 5 module for parsing command line arguments
with a richer and more user-friendly API interface, similar to python's
argparse but with perlish extra. (CPAN author's description)

Some nice features are:
 * More succint and powerful because it manages arguments for you.
 * Automatically generate usage messages when the help is requested or
   when some arguments are missing/incorrects.
 * Stores the arguments in an object based on the arguments names.
 * Supports extended options such as multi-value arguments, argument
   values split, specify which arguments are required, the types, etc.
 * Supports subcommand parsing such as: git fetch, git pull, etc.
 * Supports both optional and positional arguments.
 * Based on the design of Python argparse, which is one of the two most
   used modules in Python for this purpose.

Depends on already packaged modules: libmoo-perl, libtext-wrapper-perl.
Other dependencies seems integrated into perl.

This package is stable and doesn't change often. Its maintenance
should be easy and I can offer my help, although I'm not experienced, I
can try as I think this package is worth the effort.


signature.asc
Description: Digital signature

Bug#766858: circuslinux: FTBFS in Debian Sid

[Angel Abad]

Source: circuslinux
Severity: grave

This package fails to build from source in debian Sid, the
package should build-depends on autoconf and automake to run
autoreconf. Please consider add them to debian/control file.

make[1]: autoreconf: Command not found
debian/rules:22: recipe for target 'override_dh_auto_configure' failed
make[1]: [override_dh_auto_configure] Error 127 (ignored)
./configure --prefix=/usr \
--mandir=\${prefix}/share/man \
--infodir=\${prefix}/share/info \
--datadir=\${prefix}/share/games \
--enable-scorefile
/bin/sh: 1: ./configure: not found
debian/rules:22: recipe for target 'override_dh_auto_configure' failed

Cheers,

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

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


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

Bug#763737: red5-server init script is frozen in system reboot or shutdown

[Miguel Angel Campos]

Package: red5-server
Version: 0.9.1-4squeeze1
Severity: normal

When you execute a reboot or shutdown, the system is frozen because the
stop process in red5-server init script doesn't working. It's frozen when
is executing the getent command, in the next line of init script:

DAEMONUID=`getent passwd |grep ^$DAEMONUSER: | awk -F : '{print $3}'`
DAEMONGID=`getent passwd |grep ^$DAEMONUSER: | awk -F : '{print $4}'

However, if you execute this command in the system prompt, you have a
correct result:

# getent passwd |grep ^_red5: | awk -F : '{print $3}'
118

This line in the init script for check that red5 user exist is executed
always but it could be execute only in the start process. I have checked
that when I put this lines only in the start process, and it isn't in a
generic part of init script, the reboot or shutdown system is working
correctly and stop process of red5-server doesn't freeze.

Thank you

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

Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) (ignored:
LC_ALL set to es_ES.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages red5-server depends on:
ii  adduser 3.112+nmu2   add and remove users and groups
ii  default-jre-headles 1:1.6-40 Standard Java or Java
compatible R
ii  libred5-java0.9.1-4squeeze1  remote API for Red5 flash
streamin
ii  openjdk-6-jre-headl 6b31-1.13.3-1~deb6u1 OpenJDK Java runtime, using
Hotspo
ii  sun-java6-jre [java 6.26-0squeeze1   Sun Java(TM) Runtime
Environment (

red5-server recommends no packages.

red5-server suggests no packages.

-- no debconf information

Bug#755587:

[Angel Abad]

I'm working with upstream developer to fix compat with 1.7 as soon as
possible.

Cheers.

-- 
Angel Abad
an...@debian.org | angela...@ubuntu.com | angela...@gmail.com
http://www.pastelero.net
FPR: EBF6 080D 59D4 008A DF47  00D4 098D AE47 EE3B C279

Bug#760639: mplayer2: PGS subtitle format won't appear

[Axel Angel]

Package: mplayer2
Version: 2.0-728-g2c378c7-2+b2
Severity: normal

Dear Maintainer,

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

* What led up to the situation?
Upgrading mplayer2 2.0-728-g2c378c7-2+{b1 - b2}
Note: {before - after}:


* What exactly did you do (or not do) that was effective (or
 ineffective)?
Playing videos (eg: mkv) containing correctly recognized S_HDMV/PGS
subtitles with mplayer2 but they are not displayed at all in this new
build. When downgrading t in this new build. When downgrading t in this
new build. Downgrading to 2.0-728-g2c378c7-2+b1 works fine.

It may be possible the ABI of one of the libav changed (according to
ldd):

libavutil.so.{53 - 54}
libavcodec.so.{55 - 56}
libavformat.so.{55 - 56}
libavresample.so.{1 - 2}

I tried to compile mplayer2 from the debian git but no change. Moreover
I tried mpv which works fine on the same file, although it's using the
same versions of libav.


* What was the outcome of this action?
No subtitle is visible.


* What outcome did you expect instead?
They should be rendered, as before the update.

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


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable-updates'), (150, 'unstable'), 
(100, 'experimental'), (95, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14.12-kvm.1 (SMP w/8 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 mplayer2 depends on:
ii  liba52-0.7.4  0.7.4-17
ii  libasound21.0.28-1
ii  libass5   0.10.2-3
ii  libavcodec56  6:11~beta1-2
ii  libavformat56 6:11~beta1-2
ii  libavresample26:11~beta1-2
ii  libavutil54   6:11~beta1-2
ii  libbluray11:0.6.1-2
ii  libbs2b0  3.1.0+dfsg-2
ii  libc6 2.19-10
ii  libcaca0  0.99.beta19-2
ii  libcdio-cdda1 0.83-4.1
ii  libcdio-paranoia1 0.83-4.1
ii  libcdio13 0.83-4.1
ii  libdca0   0.0.5-7
ii  libdirectfb-1.2-9 1.2.10.0-5
ii  libdv41.0.0-6
ii  libdvdread4   5.0.0-1
ii  libenca0  1.15-2
ii  libfaad2  2.7-8
ii  libgif4   4.1.6-11
ii  libgl1-mesa-glx [libgl1]  10.2.6-1
ii  libjack0 [libjack-0.116]  1:0.124.1+20140122git5013bed0-3
ii  libjpeg8  8d1-1
ii  liblcms2-22.6-3
ii  liblircclient00.9.0~pre1-1
ii  libmad0   0.15.1b-8
ii  libmpg123-0   1.20.1-2
ii  libncurses5   5.9+20140712-2
ii  libogg0   1.3.2-1
ii  libpng12-01.2.50-2
ii  libpostproc52 6:0.git20120821-4
ii  libpulse0 5.0-6
ii  libquvi7  0.4.1-2.1
ii  libsdl1.2debian   1.2.15-10
ii  libsmbclient  2:4.1.11+dfsg-1
ii  libspeex1 1.2~rc1.2-1
ii  libswscale3   6:11~beta1-2
ii  libtheora01.1.1+dfsg.1-3.2
ii  libtinfo5 5.9+20140712-2
ii  libvdpau1 0.7-2
ii  libvorbis0a   1.3.2-1.4
ii  libx11-6  2:1.6.2-3
ii  libxext6  2:1.3.2-1
ii  libxinerama1  2:1.1.3-1
ii  libxss1   1:1.2.2-1
ii  libxv12:1.0.10-1
ii  libxvidcore4  2:1.3.3-1
ii  libxxf86vm1   1:1.1.3-1
ii  zlib1g1:1.2.8.dfsg-1

mplayer2 recommends no packages.

mplayer2 suggests no packages.

-- no debconf information


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

Bug#760639: mplayer2: PGS subtitle format won't appear

[Axel Angel]

 Please provide unshortened debug logs, i.e., mplayer -v «filename»

You can find the output of mplayer -v in the attached file.

Thank you for review my report so fast. Let me know if I can add more
details to ease the resolution of this problem.

Axel Angel.
Reading config file /etc/mplayer/mplayer.conf
: No such file or directory
get_path('') - '/home/d3lxa/.mplayer/'
get_path('config') - '/home/d3lxa/.mplayer/config'
Reading config file /home/d3lxa/.mplayer/config
MPlayer2 2.0-728-g2c378c7-2+b2 (C) 2000-2012 MPlayer Team
CPU vendor name: GenuineIntel  max cpuid level: 13
CPU: Intel(R) Core(TM) i7-4770S CPU @ 3.10GHz (Family: 6, Model: 60, Stepping: 
3)
extended cpuid-level: 8
extended cache-info: 16801856
Detected cache-line size is 64 bytes
CPUflags:  MMX: 1 MMX2: 1 3DNow: 0 3DNowExt: 0 SSE: 1 SSE2: 1 SSSE3: 1
Compiled with runtime CPU detection.
Compiled against libavutil version 54.3.0
Compiled against libavcodec version 56.0.0
Compiled against libavformat version 56.1.0
Compiled against libswscale version 3.0.0
get_path('codecs.conf') - '/home/d3lxa/.mplayer/codecs.conf'
No optional codecs config file: /home/d3lxa/.mplayer/codecs.conf
No optional codecs config file: /etc/mplayer/codecs.conf
163 audio  363 video codecs
Using built-in default codecs.conf.
Configuration: --prefix=/usr --confdir=/etc/mplayer --enable-translation 
--enable-debug=3 --enable-runtime-cpudetection
CommandLine: '-v' 
'Space.Battleship.Yamato.2199.-.17.-.[SUB].1080p.BluRay.x264.DHD.mkv'
get_path('fonts') - '/home/d3lxa/.mplayer/fonts'
Using MMX (with tiny bit MMX2) Optimized OnScreenDisplay
get_path('fonts') - '/home/d3lxa/.mplayer/fonts'
[ass] Raster: FreeType 2.5.2
[ass] Shaper: FriBidi 0.19.6 (SIMPLE) HarfBuzz-ng 0.9.35 (COMPLEX)
[ass] Initialized
get_path('fonts') - '/home/d3lxa/.mplayer/fonts'
get_path('subfont.ttf') - '/home/d3lxa/.mplayer/subfont.ttf'
[ass] Updating font cache
Using nanosleep() timing
get_path('input.conf') - '/home/d3lxa/.mplayer/input.conf'
[file] File size is 21 bytes
STREAM: [file] /home/d3lxa/.mplayer/input.conf
STREAM: Description: File
STREAM: Author: Albeu
STREAM: Comment: based on the code from ??? (probably Arpi)
Parsing input config file /home/d3lxa/.mplayer/input.conf
Input config file /home/d3lxa/.mplayer/input.conf parsed: 2 binds
Setting up LIRC support...
Failed to open LIRC support. You will not be able to use your remote control.
get_path('Space.Battleship.Yamato.2199.-.17.-.[SUB].1080p.BluRay.x264.DHD.mkv.conf')
 - 
'/home/d3lxa/.mplayer/Space.Battleship.Yamato.2199.-.17.-.[SUB].1080p.BluRay.x264.DHD.mkv.conf'

Playing Space.Battleship.Yamato.2199.-.17.-.[SUB].1080p.BluRay.x264.DHD.mkv.
get_path('sub/') - '/home/d3lxa/.mplayer/sub/'
[file] File size is 974383978 bytes
STREAM: [file] 
Space.Battleship.Yamato.2199.-.17.-.[SUB].1080p.BluRay.x264.DHD.mkv
STREAM: Description: File
STREAM: Author: Albeu
STREAM: Comment: based on the code from ??? (probably Arpi)
Cache size set to 1024 KiB
CACHE_PRE_INIT: 0 [0] 0  pre:1  eof:0  
Cache fill:  0.00% (0 bytes)   
LAVF_check: Matroska / WebM
Checking for YUV4MPEG2
ASF_check: not ASF guid!
Checking for REAL
Checking for SMJPEG
[mkv] Found the head...
[mkv] + a segment...
[mkv] / [ parsing seek head ] -
[mkv] |+ segment information...
[mkv] | + timecode scale: 100
[mkv] | + duration: 1486.250s
[mkv] | + segment uid 98 96 da 77 50 23 9c 0e af 1d 6a 8d 2f b3 57 b8
[mkv] |+ segment tracks...
[mkv] | + a track...
[mkv] |  + Track number: 1
[mkv] |  + Track type: Video
[mkv] |  + Video track
[mkv] |   + Display width: 1920
[mkv] |   + Display height: 1080
[mkv] |   + Pixel width: 1920
[mkv] |   + Pixel height: 1080
[mkv] |  + Codec ID: V_MPEG4/ISO/AVC
[mkv] |  + CodecPrivate, length 41
[mkv] |  + Language: und
[mkv] |  + Default duration: 41.708ms ( = 23.976 fps)
[mkv] | + a track...
[mkv] |  + Track number: 2
[mkv] |  + Track type: Audio
[mkv] |  + Audio track
[mkv] |   + Sampling frequency: 48000.00
[mkv] |   + Channels: 2
[mkv] |  + Codec ID: A_AAC
[mkv] |  + CodecPrivate, length 5
[mkv] |  + Language: jpn
[mkv] |  + Default duration: 21.333ms ( = 46.875 fps)
[mkv] | + a track...
[mkv] |  + Track number: 3
[mkv] |  + Track type: Subtitle
[mkv] |  + Codec ID: S_HDMV/PGS
[mkv] / [ parsing cues ] ---
[mkv] \ [ parsing cues ] ---
[mkv] \ [ parsing seek head ] -
[mkv] |+ found cluster, headers are parsed completely :)
== Found video stream: 0
[mkv] Aspect: 1.78
[mkv] Track ID 1: video (V_MPEG4/ISO/AVC), -vid 0
== Found audio stream: 0
[mkv] Track ID 2: audio (A_AAC), -aid 0, -alang jpn
[mkv] Track ID 3: subtitles (S_HDMV/PGS), -sid 0, -slang eng
[mkv] Will play video track 1.
Detected file format: Matroska
[ass] Raster: FreeType 2.5.2
[ass] Shaper: FriBidi 0.19.6 (SIMPLE) HarfBuzz-ng 0.9.35 (COMPLEX)
[ass] Initialized
get_path('fonts') - '/home/d3lxa/.mplayer/fonts'
get_path('subfont.ttf') - '/home/d3lxa/.mplayer/subfont.ttf'
[ass] Updating font cache
[V] filefmt:28  fourcc:0x31637661  size

Bug#752378: FTBFS: Missing python libraries in B-D-I

[Angel Abad]

Package: awscli
Severity: serious
Tags: patch

Hi, the pacakge FTBFS in a Debian Sid clean chroot, please take
a look to the patch. There is a missing python libraries in package
build depends.

==
ERROR: awscli.testutils (unittest.loader.ModuleImportFailure)
--
Traceback (most recent call last):
  File /usr/lib/python3.4/unittest/case.py, line 58, in testPartExecutor
yield
  File /usr/lib/python3.4/unittest/case.py, line 577, in run
testMethod()
  File /usr/lib/python3.4/unittest/loader.py, line 32, in testFailure
raise exception
ImportError: Failed to import test module: awscli.testutils
Traceback (most recent call last):
  File /usr/lib/python3.4/unittest/loader.py, line 312, in _find_tests
module = self._get_module_from_name(name)
  File /usr/lib/python3.4/unittest/loader.py, line 290, in 
_get_module_from_name
__import__(name)
  File 
/build/buildd/awscli-1.3.18/.pybuild/pythonX.Y_3.4/build/awscli/testutils.py, 
line 44, in module
import six
ImportError: No module named 'six'

Cheers,

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

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru awscli-1.3.18/debian/changelog awscli-1.3.18/debian/changelog
--- awscli-1.3.18/debian/changelog	2014-06-22 16:53:48.0 +0200
+++ awscli-1.3.18/debian/changelog	2014-06-23 09:51:16.0 +0200
@@ -1,3 +1,15 @@
+awscli (1.3.18-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add missing Build-Depends-Indep, fix FTBFS:
+- python3-six
+- python3-botocore
+- python3-colorama
+- python3-docutils
+- python3-bcdoc
+
+ -- Angel Abad an...@debian.org  Mon, 23 Jun 2014 09:50:18 +0200
+
 awscli (1.3.18-1) unstable; urgency=medium
 
   * New upstream release (Closes: #744890)
diff -Nru awscli-1.3.18/debian/control awscli-1.3.18/debian/control
--- awscli-1.3.18/debian/control	2014-01-04 09:19:47.0 +0100
+++ awscli-1.3.18/debian/control	2014-06-23 09:52:01.0 +0200
@@ -6,6 +6,11 @@
 Build-Depends: debhelper (= 9)
 	, python3
 	, python3-setuptools
+Build-Depends-Indep: python3-six
+, python3-botocore
+, python3-colorama
+, python3-docutils
+, python3-bcdoc
 Standards-Version: 3.9.5
 Homepage: http://aws.amazon.com/cli/
 Vcs-Svn: svn://anonscm.debian.org/python-apps/packages/awscli/trunk/

Bug#749665: alien-arena: diff for NMU version 7.66+dfsg-1.1

[Angel Abad]

tags 749665 + patch
tags 749665 + pending
thanks

Dear maintainer,

I've prepared an NMU for alien-arena (versioned as 7.66+dfsg-1.1) and
uploaded it to DELAYED/15. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru alien-arena-7.66+dfsg/debian/changelog 
alien-arena-7.66+dfsg/debian/changelog
--- alien-arena-7.66+dfsg/debian/changelog  2014-03-29 08:03:55.0 
+0100
+++ alien-arena-7.66+dfsg/debian/changelog  2014-06-22 18:29:03.0 
+0200
@@ -1,3 +1,10 @@
+alien-arena (7.66+dfsg-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build-Depends on pkg-config, fix FTBFS (Closes: #749665)
+
+ -- Angel Abad an...@debian.org  Sun, 22 Jun 2014 18:28:14 +0200
+
 alien-arena (7.66+dfsg-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru alien-arena-7.66+dfsg/debian/control 
alien-arena-7.66+dfsg/debian/control
--- alien-arena-7.66+dfsg/debian/control2014-03-29 06:24:09.0 
+0100
+++ alien-arena-7.66+dfsg/debian/control2014-06-22 18:28:01.0 
+0200
@@ -19,6 +19,7 @@
  libopenal-dev,
  libvorbis-dev,
  libfreetype6-dev,
+ pkg-config
 Standards-Version: 3.9.5
 Homepage: http://red.planetarena.org
 Vcs-Svn: svn://anonscm.debian.org/pkg-games/packages/trunk/alien-arena


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

Bug#733405: lasi: diff for NMU version 1.1.0-1.1

[Angel Abad]

tags 733405 + pending
thanks

Dear maintainer,

I've prepared an NMU for lasi (versioned as 1.1.0-1.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru lasi-1.1.0/debian/changelog lasi-1.1.0/debian/changelog
--- lasi-1.1.0/debian/changelog 2014-06-19 14:01:01.0 +0200
+++ lasi-1.1.0/debian/changelog 2014-06-19 13:49:25.0 +0200
@@ -1,3 +1,12 @@
+lasi (1.1.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use 3.0 (quilt) format
+  * debian/patches/fix-freetype-ftbfs (Closes: #733405):
+- Include Freetype headers in recommended way, fix FTBFS
+
+ -- Angel Abad an...@debian.org  Thu, 19 Jun 2014 13:36:38 +0200
+
 lasi (1.1.0-1) unstable; urgency=low
 
   [ Andrew Ross ]
diff -Nru lasi-1.1.0/debian/patches/fix-freetype-ftbfs 
lasi-1.1.0/debian/patches/fix-freetype-ftbfs
--- lasi-1.1.0/debian/patches/fix-freetype-ftbfs1970-01-01 
01:00:00.0 +0100
+++ lasi-1.1.0/debian/patches/fix-freetype-ftbfs2014-06-19 
13:45:54.0 +0200
@@ -0,0 +1,99 @@
+Description: Include Freetype headers in recommended way.
+ This change should fix https://sourceforge.net/p/lasi/bugs/2/. The
+ change goes a bit beyond the macports patch for the problem linked in
+ that bug report which was incomplete. (I searched for all occurrences
+ of #include and freetype in the code base and changed to the standard
+ form.)
+ .
+ Tested on Linux with Freetype version 2.4.9 which implies this change
+ does not disrupt anything for that Freetype version. A further test
+ for Freetype version 2.5.1 (which previously could not be used with
+ libLASi because of the non-standard #includes in the old version
+ of that code) has been requested.
+Author: Alan W. Irwin
+Origin: http://sourceforge.net/p/lasi/code/182/
+Bug: http://sourceforge.net/p/lasi/bugs/2/
+Bug-Debian: http://bugs.debian.org/733405
+Reviewed-By: Juhani Numminen juhaninummin...@gmail.com 
+
+--- lasi-1.1.0.orig/include/LASi.h
 lasi-1.1.0/include/LASi.h
+@@ -11,7 +11,8 @@
+ #include sstream
+ #include map
+ #include pango/pango.h
+-#include freetype/ftglyph.h
++#include ft2build.h
++#include FT_GLYPH_H
+ 
+ class FreetypeGlyphMgr;
+ class ContextMgr;
+--- lasi-1.1.0.orig/src/drawGlyph.cpp
 lasi-1.1.0/src/drawGlyph.cpp
+@@ -6,7 +6,8 @@
+  */
+ 
+ #include ostream
+-#include freetype/ftoutln.h
++#include ft2build.h
++#include FT_OUTLINE_H
+ #include algorithm
+ #include LASi.h
+ #include config.h
+--- lasi-1.1.0.orig/src/drawGlyph.h
 lasi-1.1.0/src/drawGlyph.h
+@@ -10,7 +10,8 @@
+ 
+ #include iostream
+ #include pango/pango.h
+-#include freetype/freetype.h
++#include ft2build.h
++#include FT_FREETYPE_H
+ 
+ /** Generate the Postscript commands to draw the glyph
+   * using the font in pPangoCtx.
+--- lasi-1.1.0.orig/src/glyphMgr.cpp
 lasi-1.1.0/src/glyphMgr.cpp
+@@ -10,8 +10,7 @@
+ 
+ #include ft2build.h
+ #include FT_FREETYPE_H
+-
+-#include freetype/ftglyph.h
++#include FT_GLYPH_H
+ 
+ #include cassert
+ #include util.h
+--- lasi-1.1.0.orig/src/glyphMgr.h
 lasi-1.1.0/src/glyphMgr.h
+@@ -15,8 +15,7 @@
+ 
+ #include ft2build.h
+ #include FT_FREETYPE_H
+-
+-#include freetype/ftglyph.h
++#include FT_GLYPH_H
+ 
+ /** Manage FT_Glyph by insuring that FT_Glyph is handled correctly.
+  */
+--- lasi-1.1.0.orig/src/util.cpp
 lasi-1.1.0/src/util.cpp
+@@ -11,7 +11,6 @@
+ 
+ #include ft2build.h
+ #include FT_FREETYPE_H
+-//#include freetype/freetype.h
+ 
+ using namespace std;
+ 
+--- lasi-1.1.0.orig/src/util.h
 lasi-1.1.0/src/util.h
+@@ -18,7 +18,7 @@
+ 
+ #include ft2build.h
+ #include FT_FREETYPE_H
+-#include freetype/ftglyph.h
++#include FT_GLYPH_H
+ 
+ std::ostream operator(std::ostream, const FT_Library);
+ std::ostream operator(std::ostream, const FT_Face);
diff -Nru lasi-1.1.0/debian/patches/series lasi-1.1.0/debian/patches/series
--- lasi-1.1.0/debian/patches/series1970-01-01 01:00:00.0 +0100
+++ lasi-1.1.0/debian/patches/series2014-06-19 13:47:21.0 +0200
@@ -0,0 +1 @@
+fix-freetype-ftbfs
diff -Nru lasi-1.1.0/debian/source/format lasi-1.1.0/debian/source/format
--- lasi-1.1.0/debian/source/format 1970-01-01 01:00:00.0 +0100
+++ lasi-1.1.0/debian/source/format 2014-06-19 13:37:41.0 +0200
@@ -0,0 +1 @@
+3.0 (quilt)


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

Bug#733405:

[Angel Abad]

Hello, I'm preparing a NMU for solving this bug.

Cheers

-- 
Angel Abad
an...@debian.org | angela...@ubuntu.com | angela...@gmail.com
http://www.pastelero.net
FPR: EBF6 080D 59D4 008A DF47  00D4 098D AE47 EE3B C279

Bug#751571: ftbfs with --as-needed

[Angel Abad]

Package: brightd
Severity: normal
Tags: patch
User: debian-...@lists.debian.org
Usertags: ld-as-needed

This package fails to build with binutils-gols, see the buildlog at:

https://launchpadlibrarian.net/173940324/buildlog_ubuntu-utopic-i386.brightd_0.4.1-1_FAILEDTOBUILD.txt.gz

Cheers,

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

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- brightd-0.4.1.orig/Makefile
+++ brightd-0.4.1/Makefile
@@ -14,7 +14,7 @@ endif
 all: brightd brightd.1
 
 brightd: brightd.c
-	gcc $(CFLAGS) $(A_CFLAGS) -o $@ $@.c
+	gcc $@.c $(CFLAGS) $(A_CFLAGS) -o $@
 
 brightd.1:
 	sed -re 's/^\.nr no_x11 [01]/.nr no_x11 $(MAN_NO_X11)/' brightd.1.tpl  brightd.1

Bug#750549: ipvsadm: unable to load more than one rule

[Miguel Angel Martin]

Package: ipvsadm
Version: 1:1.26-1
Severity: important

Dear Maintainer,

I was working in a cluster with pacemker and corosync and lvs to do load 
balancing.
The cluster has two nodes, and lvs needs two virtual servers (IPv4,IPv6) and 
four real servers (2 IPv4,2 IPv6). 

I tried inserting rules both using ldirectord and ipvsadm directly. 
They were unable to add more than one real server per AF.

The expectation was that 2 real servers were included per AF.

Please, see raw ipvsadm commands below:

root@debian:~# ipvsadm -L -n
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
  - RemoteAddress:Port   Forward Weight ActiveConn InActConn
TCP  192.168.1.10:389 rr
  - 192.168.1.11:389Route   1  0  0 
TCP  [fc00:1::1]:389 rr
  - [fc00:1::2]:389 Route   1  0  0 

root@debian:~# ipvsadm -A -t 192.168.1.10:389 -s rr
Service already exists

root@debian:~# ipvsadm --add-server --tcp-service 192.168.1.10:389 
--real-server 192.168.1.11
Destination already exists

root@debian:~# ipvsadm --add-server --tcp-service 192.168.1.10:389 
--real-server 192.168.1.12
Destination already exists

root@debian:~# ipvsadm -A -t [fc00:1::1]:389 -s rr
Service already exists

root@debian:~# ipvsadm --add-server --tcp-service [fc00:1::1]:389 --real-server 
[fc00:1::2]:80
Destination already exists

root@debian:~# ipvsadm --add-server --tcp-service [fc00:1::1]:389 --real-server 
[fc00:1::3]:80
Destination already exists

root@debian:~# ipvsadm -L -n
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
  - RemoteAddress:Port   Forward Weight ActiveConn InActConn
TCP  192.168.1.10:389 rr
  - 192.168.1.11:389Route   1  0  0 
TCP  [fc00:1::1]:389 rr
  - [fc00:1::2]:389 Route   1  0  0 

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

Kernel: Linux 3.2.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages ipvsadm depends on:
ii  debconf [debconf-2.0]  1.5.49
ii  libc6  2.13-38+deb7u1
ii  libnl1 1.1-7
ii  libpopt0   1.16-7
ii  lsb-base   4.1+Debian8+deb7u1

ipvsadm recommends no packages.

Versions of packages ipvsadm suggests:
pn  heartbeat   none
pn  keepalived  none
ii  ldirectord  1:3.9.2-5+deb7u2

-- Configuration Files:
/etc/default/ipvsadm changed:
AUTO=false
DAEMON=none


-- debconf information:
  ipvsadm/kernel_does_not_support_ipvs:
  ipvsadm/daemon_multicast_interface: eth0
  ipvsadm/auto_load_rules: false
  ipvsadm/daemon_method: none


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

Bug#743935: base: Once SD card safely removed, sometimes it is no more recognized until restart

[Miguel Angel]

Package: base
Severity: normal

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation? Formatting a SD card for different purposes 
and when I remove it safely from the computer, SOMETIMES it is no more 
recognized again, and when I didn't remove it safely, I don't remember to have 
this problem...
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action? Debian does not recognize again the 
SD card hardware
   * What outcome did you expect instead? 

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


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

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


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

Bug#740282:

[Angel Abad]

Hi, the upstream maintainer is evaluating the situation and patch.

Cheers,

-- 
Angel Abad
an...@debian.org | angela...@ubuntu.com | angela...@gmail.com
http://www.pastelero.net
FPR: EBF6 080D 59D4 008A DF47  00D4 098D AE47 EE3B C279

Bug#707856:

[Siegfried-Angel Gevatter Pujals]

Update: I've finally got around to porting the app, but there's some weird
segmentation fault happening that I need to figure out before I can upload
the changes.

-- 
Siegfried

Bug#730262: please, reactivate debian-laespi...@lists.debian.org

[Miguel Angel Ordoñez Moya]

Hi I am very interested in the reactivation of the
debian-laespi...@lists.debian.org list.

The main purpose of this list
will be to establish a communication channel for all the things
involving the management of La Espiral magazine.

Thank you very much.

-- 
Usuario registrado de Debian GNU/Linux nº 416197
http://linuxcounter.net/user/416197.html


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

Bug#718778: RFP: doublecmd -- Dual panel file manager.

[Miguel Angel Fraile]

Package: wnpp
Severity: wishlist

* Package name: doublecmd
  Version : 0.5.6b
  Upstream Author : alexx2000
* URL : http://doublecmd.sourceforge.net
* License : GPL, LGPL
  Programming Lang: FreePascal / Lazarus
  Description : Dual panel file manager.

Double Commander is a cross platform open source file manager with two panels 
side by side. It is inspired by Total Commander and features some new ideas.

Here are some key features of Double Commander:

- Unicode support
- All operations working in background
- Multi-rename tool
- Tabbed interface
- Custom columns
- Internal text editor (F4)  with syntax hightlighting
- Built in file viewer (F3) to view files of in hex, binary or text format
- Archives are handled like subdirectories. You can easily copy files to and 
from archives. Supported archive types: ZIP, TAR GZ, TGZ, LZMA and also BZ2, 
RPM, CPIO, DEB, RAR.
- Extended  search function with full text search in any files
- Configurable button bar to start external programs or internal menu commands
- Total Commander WCX, WDX and WLX plug-ins support
- File operations logging
- And more...


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

Bug#712812: almanah: Please move Almanah 0.10 to unstable

[Angel Abad]

2013/6/20 Jordi Mallach jo...@debian.org

 Hey Ángel!

 El dc 19 de 06 de 2013 a les 22:47 +0200, en/na Angel Abad va escriure:
  Hi Jordi, I cant upload to unstable, almanah 0.10.8 is waiting for
  libecal1.2-dev (= 3.6.0) and libedataserver1.2-dev (= 3.6.0).

 Meh, I totally don't want to entangle this silly transition with all the
 evo stuff.

 I tried the upstream patch against 0.9.1, it works flawlessly. Rough,
 quick patch attached, feel free to cleanup and upload!

 Thanks!
 Jordi


Thanks Jordi, I'll review it as soon as possible.

Cheers,



  --
 Jordi Mallach Pérez  --  Debian developer http://www.debian.org/
 jo...@sindominio.net jo...@debian.org http://www.sindominio.net/
 GnuPG public key information available at http://oskuro.net/




-- 
Angel Abad
an...@debian.org | angela...@ubuntu.com | angela...@gmail.com
http://www.pastelero.net
FPR: EBF6 080D 59D4 008A DF47  00D4 098D AE47 EE3B C279

Bug#712812: almanah: Please move Almanah 0.10 to unstable

[Angel Abad]

Hi Jordi, I cant upload to unstable, almanah 0.10.8 is waiting for
libecal1.2-dev (= 3.6.0) and libedataserver1.2-dev (= 3.6.0).

Cheers,


2013/6/19 Jordi Mallach jo...@debian.org

 Package: almanah
 Version: 0.10.8-1
 Severity: normal

 As it's blocking the transition of libgtkspell to testing.

 Thanks!

 Jordi

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

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




-- 
Angel Abad
an...@debian.org | angela...@ubuntu.com | angela...@gmail.com
http://www.pastelero.net
FPR: EBF6 080D 59D4 008A DF47  00D4 098D AE47 EE3B C279

Bug#709267: File Corruption Problems

[Angel Ortega]

2013/5/23 Bob Proulx b...@proulx.com:

 Ola Lundqvist wrote:
 ... My guess is that you have some kind of bit errors on your disk.
 ...
 I'll close this bug report and I think you should check your
 disk using the badblocks command. :-)

 You might also consider running 'debsums' which will verify package
 files against the MD5 checksum lists included in the package.  A
 useful file integrity checking tool.

Given that neither badblocks nor smartctl reported aboutn any HD
failure, I'll try this approach.

Thanks!

Regards,
Angel


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

Bug#709267: cron-apt: Syntax error: in unexpected

[Angel Ortega]

2013/5/22 Ola Lundqvist o...@debian.org:

 I can not find any in in the source I have. Could you please
 send me the file so I can have a look.

Of course. Please find it attached to this message.

 And you are sure there is no chance that this file may have
 been modified by anyone on your system?

No. I'm the only user on this system.

I've replaced the in by an if, but today I had received another
error. I think the file went corrupted somehow in the wheezy
transition.

I've --reinstall'ed the package and the in is no longer an if, so
you may file this in the unexplainable folder and move on.

Thanks for your help and keep the good work,
Angel Ortega


cron-apt
Description: Binary data

Bug#709267: cron-apt: Syntax error: in unexpected

[Angel Ortega]

Package: cron-apt
Version: 0.9.1
Severity: important

Dear Maintainer,

Since a couple of days I receive an email message from Cron Daemon
with the following content:

/usr/sbin/cron-apt: 381: /usr/sbin/cron-apt: Syntax error: in unexpected

Line 381 of /usr/sbin/cron-apt contains the mentioned in instead
of if.

Please fix.

Best regards,
Angel Ortega

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

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

Versions of packages cron-apt depends on:
ii  apt  0.9.7.8

Versions of packages cron-apt recommends:
ii  cron3.0pl1-124
ii  heirloom-mailx [mailx]  12.5-2
ii  liblockfile11.09-5

cron-apt suggests no packages.

-- no debconf information


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

Bug#708253: dracut: resume doesn't work

[Axel Angel]

Package: dracut
Version: 027-1
Severity: important

Dear Maintainer,

   * Installed linux-image-3.8-1-amd64, which depends on udev-175-7.2
 which depends on dracut

   * Beforehand tried the old version (wheezy) but the resume had an
 error: /lib/dracut/hooks/mount/10resume.sh: line 17: resume:
 command not found it boots without resuming

   * With the actual version there is no error and it won't resume. In
 all these tests I had to add resume=/dev/sda2

   * I expected the system to resume from swap because I suspended to
 disk as before my kernel upgrade (pm-hibernate: pm-utils-1.4.1-9)


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

Kernel: Linux 3.8-1-amd64 (SMP w/4 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 dracut depends on:
ii  cpio   2.11+dfsg-0.1
ii  kbd1.15.3-9
ii  kpartx 0.4.9+git0.4dfdaf2b-6
ii  module-init-tools  9-3
ii  udev   175-7.2
ii  util-linux 2.20.1-5.3

Versions of packages dracut recommends:
ii  cryptsetup  2:1.4.3-4
ii  dmraid  1.0.0.rc16-4.2
ii  dmsetup 2:1.02.74-7
ii  lvm22.02.95-7
ii  mdadm   3.2.5-5

Versions of packages dracut suggests:
pn  dracut-network  none

-- no debconf information


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

Bug#702905:

[Angel Abad]

Hi, 0.9.1-1 is now in testing, thanks for your attention.

Cheers,

-- 
Angel Abad
an...@debian.org | angela...@ubuntu.com | angela...@gmail.com
http://www.pastelero.net
FPR: EBF6 080D 59D4 008A DF47  00D4 098D AE47 EE3B C279