Bug#950096: flatpak: Flatpak fails to open SSL connections with p11-kit 0.23.19

McVittie : > On Tue, 28 Jan 2020 at 22:50:31 +0100, Lennart Weller wrote: > > > Currently all SSL connections, probably mostly HTTPS, will fail with > > flatpak due to a major API change in p11-kit as discussed in the merge > > request[1] for p11-kit 0.23.19, cause obviously a pa

Bug#950096: flatpak: Flatpak fails to open SSL connections with p11-kit 0.23.19

Package: flatpak Version: 1.6.1-1 Severity: important Dear Maintainer, Currently all SSL connections, probably mostly HTTPS, will fail with flatpak due to a major API change in p11-kit as discussed in the merge request[1] for p11-kit 0.23.19, cause obviously a patch-version changes major API

Bug#944227: (no subject)

Hello Gordon, Both pgcli and mycli are managed by me and they both wiating for the prompt_toolkit update to major version 2. The updated packages are already in the vcs but cannot be uploaded yet to unstable. I might push them to experimental in case you want to test something. Kind regards,

Bug#930010: warnings with postgresql 11

Hi Daniel, currently the package upload hangs on the fact that python-prompt-toolkit is one major version behind in testing/buster. I might look into just patching the pgcli a little bit to avoid this warning. I dont think I want to go through the process to get a new major version of i think at

Bug#904765: looking-glass packaging questions

Hello everyone I do have some changes I want to make to the package to make it more comfortable to use. Before the first use the looking-glass host (this package) requires some changes to the libvirt-qemu abstract apparmor profile. Explicility changing "/{dev,run}/shm r," to read-write The

Bug#904765: closed by Bart Martens (closing RFS: looking-glass/0+a11-1 [ITP])

I recently uploaded a new version tagged 0+a12 of looking-glass. I'm still looking for sponsors. In case the use-case for this software is not clear a short description from the official website: > Looking Glass is an open source application that allows the use of a KVM > (Kernel-based Virtual

Bug#904765:

And another upstream release before I could find a sponsor. * Package name : looking-glass Packaging link : https://salsa.debian.org/lhw-guest/looking-glass Version : 0+a12 Upstream Author : Geoffrey McRae * URL : https://github.com/gnif/LookingGlass * License : GPL2+ Programming Lang:

Bug#898931: Fwd: Bug#898931: Acknowledgement (ITP: looking-glass -- An extremely low latency KVM FrameRelay implementation for guests with VGA PCI Passthrough)

And another upstream release before I could find a sponsor. * Package name : looking-glass Packaging link : https://salsa.debian.org/lhw-guest/looking-glass Version : 0+a12 Upstream Author : Geoffrey McRae * URL : https://github.com/gnif/LookingGlass * License : GPL2+ Programming Lang:

Bug#913034: (no subject)

Control: found 1.1.7-2 I had my system automatically install libasound2-plugins 1.1.7-2 coming from 1.1.6-1+b1 which was working fine. With 1.1.7-2 it is still failing on my system. Alsa shows all devices as on but Pulse in my case has no knowledge of them.

Bug#904765: RFS: looking-glass/0+a11-1

dget -x https://mentors.debian.net/debian/pool/main/l/looking-glass/looking-glass_0+a11-1.dsc Regards, Lennart Weller

Bug#903312: innoextract: bad chunk magic: iostream error on armhf

Hey, You should still report it upstream. GOG containers are probably the most common use-case for innoextract so I assume they will be able to help with this issue. Version 1.7 was supposed to fix some issues with the newer versions of GOG Installers but maybe there are some caveats left.

Bug#898931: Acknowledgement (ITP: looking-glass -- An extremely low latency KVM FrameRelay implementation for guests with VGA PCI Passthrough)

A few things have changed since the initial ITP. The package had license issues which have been resolved upstream. The packaging is already finished and available at the link below. * Package name: looking-glass Packaging link : https://salsa.debian.org/lhw-guest/looking-glass Version

Bug#898931: ITP: looking-glass -- An extremely low latency KVM FrameRelay implementation for guests with VGA PCI Passthrough

Package: wnpp Severity: wishlist Owner: Lennart Weller <l...@ring0.de> * Package name: looking-glass Version : 0+a10 Upstream Author : Geoffrey McRae <ge...@hostfission.com> * URL : https://github.com/gnif/LookingGlass/ * License : GPL2+ with OpenS

Bug#894321: new upstream (1.9.0)

pgcli > 1.6 depends on their own version of cli_helpers which they use for pgcli and mycli. And I dont feel it would be ideal to vendorize the library in both packages. So I opened this https://mentors.debian.net/package/cli-helpers 5 months ago. If that was to go in at some point I will also

Bug#889653: netdata: missing python module 'pyyaml2'

Alright. I already found the issue in the package. I must have accidentally removed the python.d patch which I had created previously thinking it was obsolete. I'll re-add it and update the package. That should fix it again so that the netdata python modules use the system pyyaml. February

Bug#889653: netdata: missing python module 'pyyaml2'

It does depend on pyyaml3. Quote from your submitted bugreport: Versions of packages netdata depends on: ii python3-yaml 3.12-1+b1 On 05/02/2018 11:53, Guillaume Clercin wrote: Package: netdata Version: 1.9.0+dfsg-1 Severity: important Dear Maintainer, After upgrading netdata, no

Bug#888815: making SEND_EMAILS configurable

Hey Daniel, feel free to submit a patch. I wouldn't mind having some configuration options at install time. Also you seem to be the of the most involved person using netdata on debian. If you want we could add you as a maintainer. Lennart January 30, 2018 9:30 AM, "Daniel Baumann"

Bug#885661: ITP: cli-helpers -- Helper library for creating Python CLI applications

Package: wnpp Severity: wishlist Owner: Lennart Weller <l...@ring0.de> * Package name: cli-helpers Version : 1.0.1 Upstream Author : Amjith Ramanujam <amjit...@gmail.com> * URL : http:github.com/dbcli/cli_helpers * License : BSD-3-clause Prog

Bug#879765: netdata: fails to run on CPUs without SSE2 instruction set

Ah. Good old Soekris. I had a quick look through the source of netdata. The only part of netdata that makes use of the SSE instruction set is their implementation of the stats.d. Now, I didn't test this but you could try disabling just this part of the application. It shouldn't affect the

Bug#878890: netdata: Debian pachaged netdata fails to detect disks/partitions correctly

I assume it has something to do with our strict ReadOnly policy applied by systemd. Try changing the netdata service file (/lib/systemd/system/netdata.service) to be more lenient. e.g. Change ReadOnlyDirectories=/ to ReadWriteDirectories=/ or remove the lines completely. Don't forget to reload

Bug#869200: Adequate still reports netdata as having obsolete conffile , maybe an adequate bug ?

No it looks like i'm using the rm_conffile wrong. I'll have to check why this didn't work as expected. I haven't used it before. the adequate result should be correct. I'll try it out for the next release. We have some small warnings to remove anyway. August 30, 2017 7:45 AM, "shirish शिरीष"

Bug#838056: nvidia-texture-tools: Embedded libsquish library now available in debian)

After some time away from this hogwash of builtin and modified libraries in nvtt im back to work on it. Right now I think I have to rewrite the use of libsquish in the project before i can link it with the system library, as it uses internal and deprecated header files to do colourspace

Bug#861713: netdata: `service netdata restart` fails due to missing pidfile

What init do you use on your system? The creation of the pid file should have been done by the init. May 3, 2017 5:09 AM, "Daniel Ring" wrote: > Package: netdata > Version: 1.5.0+dfsg-4 > Severity: normal > > Dear Maintainer, > > The init scripts provided with this package

Bug#854401: AW: Bug#854401: new upstream (1.5)

It's already in our alioth git. We are currently waiting on some clarifications. But if you want to you can build it from the git already -Ursprüngliche Nachricht- Von: Daniel Baumann [mailto:daniel.baum...@progress-linux.org] Gesendet: Montag, 6. Februar 2017 18:34 An:

Bug#846750: Processed: Also add the affects

Those headers are so utterly useless. I patched the debian package for now and tested it with some examples for b64. I'll have to upstream some of these changes. The actual package as it is upstream doesn't even work. December 6, 2016 10:57 AM, ow...@bugs.debian.org wrote: > Processing

Bug#841612: libmodpbase64-dev: modp_stdint.h is missing

The modp_stdint.h is not installed on non-Windows systems. It just defines some standard storage names also available in stdint.h. Including it in the install seems nonsensical.

Bug#829021: pgcli: Crashes on launch

Apparently prompt-toolkit was updated again breaking all compatibility. I'll have a look the next few days to see what needs patching. On 29.06.2016 21:48, Sajith T S wrote: Package: pgcli Version: 0.20.1-3 Severity: important Upon providing password, pgcli dies with the Traceback copied

Bug#810968: [debian-mysql] Bug#810968: Bug#810968: mariadb-server-10.0: Logrotate exists 1 if a non-debian mysqld is running (e.g. containerized mysqld)

March 8 2016 1:52 PM, "Sergey Vojtovich" wrote: > I adjusted your patch a bit, it seem to work well for me. Could you please > verify if you're fine with the attached version and it works for you too? Well you basically dropped all the safe guards. But in the end its a

Bug#810968: [debian-mysql] Bug#810968: Bug#810968: mariadb-server-10.0: Logrotate exists 1 if a non-debian mysqld is running (e.g. containerized mysqld)

On Mon, Mar 07, 2016 at 06:37:49PM +0400, Sergey Vojtovich wrote: > Existence of pid-file is a sure sign that there's mysqld running, the only > exception is mysqld crash. What do you think about skipping this check? > > I'd also suggest to turn things around and check for pid-file first and then

Bug#810968: [debian-mysql] Bug#810968: Bug#810968: mariadb-server-10.0: Logrotate exists 1 if a non-debian mysqld is running (e.g. containerized mysqld)

On Mon, Mar 07, 2016 at 04:15:54PM +0400, Sergey Vojtovich wrote: > > March 3 2016 9:35 PM, "Otto Kekäläinen" wrote: > I consider it lesser evil. You may use my_print_defaults to get > pid-file value. > > Worth to note that I don't see any value in executing "mysqladmin ping". I

Bug#810968: [debian-mysql] Bug#810968: Bug#810968: mariadb-server-10.0: Logrotate exists 1 if a non-debian mysqld is running (e.g. containerized mysqld)

March 3 2016 9:35 PM, "Otto Kekäläinen" wrote: > Hello Lennart! > > I asked core developers to review this and got this reply: > > It's probably alright for 10.0. But it's not completely suitable for 10.1. > As contributor mentioned himself that there's a problem with this

Bug#799776: python-pymysql: Update package to 0.6.6 or newer to satisfy the mycli dependency

I'm currently not very invested in the upgrade to the package. I fixed mycli up to work with 0.6.2. But I obviously don't mind updating it. Just need to test it with the 0.7.2 release. But updating the pymysql is not in my hands anyway. On 4 March 2016 12:39:57 CET, Sandro Tosi

Bug#810968: [debian-mysql] Bug#810968: Bug#810968: mariadb-server-10.0: Logrotate exists 1 if a non-debian mysqld is running (e.g. containerized mysqld)

Hey Otto, Sorry I totally forgot about this. Yes, I do have an updated patch. I actually found there to be some issues with containers which had embedded mysqld forked from the start script so I added an additional check to the 2) version. Following problems might exist in the future with this

Bug#813335: mdadm: Upgrade from jessie to testing breaks boot with raid on lvm2

Control: found 3.3.2-5+deb8u1 It's probably the patch which was released a few months ago in testing and a few days ago also in stable as 3.3.2-5+deb8u1 is also affected. As can be seen here: http://unix.stackexchange.com/questions/258790/ Try reversing the patch locally and see if it fixes your

Bug#810968: [debian-mysql] Bug#810968: mariadb-server-10.0: Logrotate exists 1 if a non-debian mysqld is running (e.g. containerized mysqld)

Well okay I didn't know the config files were being split up. There are two options of the top of my head: 1) As you said. Just assume the pid file location 2) Check the parent process id being 1 In this case parent of the parent because of mysqld_safe # test $(ps -o ppid= -p $(ps -o ppid=

Bug#811612: FTBFS with GCC 6: cannot convert x to y

Hey Martin, Could you also report this upstream[0]? The upstream version and the current debian version are already diverging by quite a bit and I don't want to add even more patches on top. Have you tried building the experimental branch from [1] with gcc6? It's a way more recent release but

Bug#811612: FTBFS with GCC 6: cannot convert x to y

On 20.01.2016 18:30, Martin Michlmayr wrote This builds fine. Nice. So I either just have to add the patches for 2.0.8 or get 0ad to work with 2.1.0. I'll look into that in the next few days as time permits. Can you remind me how to generate the orig tarball? There are two source branches.

Bug#810968: [debian-mysql] Bug#810968: mariadb-server-10.0: Logrotate exists 1 if a non-debian mysqld is running (e.g. containerized mysqld)

I added some comments to the patch On Fri, Jan 15, 2016 at 08:58:29AM +0200, Otto Kekäläinen wrote: > Thanks for reporting this and supplying a patch! > > Can you please make a new version where the scipt block has some > comments? There is rather complex stuff going on and somebody > reviewing

Bug#811072: regression in apt-get source to get source when binary has extra debian version

Package: apt Version: 1.1.3 Severity: normal The apt versions since stable have a bug in which apt-get source fails to find the source package when the binary package has additional version information. E.g. the current gdb version in testing 7.10-1+b1. Here are some reproducible steps for a

Bug#810968: mariadb-server-10.0: Logrotate exists 1 if a non-debian mysqld is running (e.g. containerized mysqld)

Package: mariadb-server-10.0 Version: 10.0.22-0+deb8u1 Severity: minor Tags: patch Dear Maintainer, The current logrotate script only checks if there is a mysqld process running which it can't connect to. If this is the case the postrotate script exists with 1 causing a mail to be send. I

Bug#807310: RFS: network-manager-ssh/0.9.4-1 [ITP] - ssh vpn for network manager

ssh.c:1290]: (error) Possible null pointer dereference: > local_ip > [properties/nm-ssh.c:1291]: (error) Possible null pointer dereference: netmask > [properties/nm-ssh.c:1316]: (error) Possible null pointer dereference: > preferred_authentication > $ flawfinder -Q -c . > I'll report these upstream as these check seems to be of valid concern. Not security wise but to avoid errors. Thanks again, Lennart Weller

Bug#807310: RFS: network-manager-ssh/0.9.4-1 [ITP] - ssh vpn for network manager

> Examples of what I mean: dz.po ug.po sl.po ro.po ps.po pa.po nb.po The files still contain the author information in the po header. They are just missing in the file header. I'll report it upstream anyway so he can add the information to the file header. > It isn't about scientific

Bug#807310: RFS: network-manager-ssh/0.9.4-1 [ITP] - ssh vpn for network manager

/network-manager-ssh_0.9.4-1.dsc More information about hello can be obtained from https://github.com/danfruehauf/NetworkManager-ssh Changes since the last upload: * Initial release. (Closes: #725396) Regards, Lennart Weller

Bug#725396:

This sounds like a nice plugin. I would package it if nobody else is working on it.

Bug#806400: ImportError: No module named 'pkg_resources'

Sorry. Should have been python3-pkg-resources. Haven't had my coffee yet. November 27 2015 9:41 AM, "Max Kellermann" <m...@duempel.org> wrote: > On 2015/11/27 09:34, Lennart Weller <lenn...@lennartweller.de> wrote: > >> Could you try reinstalling pkg-r

Bug#806400: ImportError: No module named 'pkg_resources'

Could you try reinstalling pkg-ressources? sudo apt-get install --reinstall python-pkg-resources The line from your stacktrace is not in the source code of pgcli. Lennart November 27 2015 8:51 AM, "Max Kellermann" wrote: > Package: pgcli > Version: 0.20.1-1 > > # pgcli

Bug#806415: mycli: No way to execute the query

This is indeed a weird bug. It completly ignores all control characters. Even though pgcli uses almost exactly the same code and works fine. I marked the bug as critical for now as it makes mycli impossible to use. November 27 2015 10:06 AM, "François Gannaz" wrote: >

Bug#806311: RFS: s3backer/1.4.2-1 [ITP]

the last upload: * Initial release. Regards, Lennart Weller

Bug#806311: RFS: s3backer/1.4.2-1 [ITP]

Hey again, > Please help to update the license file for s3backer.spec.in. I added the license information to the copyright file. As it is not part of the final binary or included in the package itself there should be no license compatibility issues between the GPLv2 source and this APL-2

Bug#794250: pgcli packaging progress

Hey, I already finished the packaging a while back when pgcli didn't need pgspecial yet. I just updated my version to 0.20.1 and added a reference to your package in my git[1] and also added the git-dpm stuff. My normal sponsor is currently really busy and I myself was too, so I hadn't looked

Bug#799776: Had a look into it

It looks like MySQL 5.6 and MariaDB 10.0 are more restrictive with LOAD LOCAL INFILE. At least for 3/4 of the failing tests that will be the issue. One option seems to be adding this to the my.cnf and loading it for the tests: [client] loose-local-infile = yes For the other failure I am not

Bug#794251: need to update python-pymysql ?

Potentially yes. I'm currently trying to get it to work with 0.6.2, if you want you can follow that progress on the github tracker[0]. Otherwise I will have no choice but to ask the PyMySQL-maintainers to update the debian version. Lennart [0] https://github.com/dbcli/mycli/issues/155

Bug#799776: python-pymysql: Update package to 0.6.6 or newer to satisfy the mycli dependency

Package: python-pymysql Version: 0.6.2-2 Severity: wishlist Dear Maintainer, I am currently working on getting mycli into debian. The current dependency is on version 0.6.6 or newer. I have tried some work arounds to get it to work with 0.6.2 but there seem to be some issues with connection

Bug#794452:

If I can help you out with that let me know. September 4 2015 9:55 AM, "Andrii Senkovych" <jolly_ro...@itblog.org.ua> wrote: > Hi, Lennart > > I'm sorry for the late reply. I'll update the packages during this > weekend. Thank you! > > 2015-09-04 10:01 GMT+0

Bug#790317: Patch applied upstream

[1] http://anonscm.debian.org/cgit/collab-maint/nvidia-texture-tools.git/ July 31 2015 3:21 PM, "Lennart Weller" <lenn...@lennartweller.de> wrote: > I upgraded my local version of the texture tools. The git Version has some > serious bugs right now. > The included test

Bug#794452:

I keep updating the packages and newer versions now require 0.1.16. If you'd like I could help out with updating the package.

Bug#797654: ITP: s3backer -- Amazon AWS S3-backed virtual hard disk device

a like that approach so I went with it. Cheers, Lennart Weller [1] https://github.com/s3fs-fuse/s3fs-fuse [2] https://fedorahosted.org/s3fs/ [3] https://github.com/russross/s3fslite

Bug#797654: ITP: s3backer -- Amazon AWS S3-backed virtual hard disk device

Package: wnpp Severity: wishlist Owner: Lennart Weller <l...@ring0.de> * Package name: s3backer Version : 1.4.1 Upstream Author : Archie L. Cobbs <arc...@dellroad.org> * URL : https://www.github.com/archiecobbs/s3backer * License : GPL, OpenSSL

Bug#760473: Further analysis and a patch

August 11 2015 7:54 PM, David Kalnischkies da...@kalnischkies.de wrote: apt does not link indirectly to libnettle nor to libcurl-gnutls. The optinal apt-transport-https does. That is a big difference for bootstrappers as it means they can ignore -https for the time being until the base system

Bug#794562: 0ad: Test 0ad with new version of nvidia-texture-tools

I went through all the added patches and removed all those which were already included in upstream. That left me with mostly debian related patches[0] which he doesn't want applied upstream. issue188 - still have that one clang-cpp11 - doesn't really apply to debian but I will probably include

Bug#794570: ITP: python-prompt-toolkit -- Python library for building interactive command lines

Package: wnpp Severity: wishlist Owner: Lennart Weller l...@ring0.de * Package name: python-prompt-toolkit Version : 0.45 Upstream Author : Jonathan Slenders * URL : https://github.com/jonathanslenders/python-prompt-toolkit * License : BSD-3-clause

Bug#794562: 0ad: Test 0ad with new version of nvidia-texture-tools

Package: 0ad Severity: wishlist Dear Maintainer, Could you test 0ad with the new nvidia-texture-tools version I uploaded to collab-maint[0]? My experience with the package tells me that it might break something. The updated package also includes the ARM64 support added by Martin Michlmayr

Bug#794452: python-sqlparse: Please update package to 0.1.14 or higher to satisfy pgcli/mycli dependency

Package: python-sqlparse Version: 0.1.13-2 Severity: wishlist Dear Maintainer, Please update the package to version 0.1.14 or the newest version 0.1.16 to satisfy the dependencies of the packages I am currently building for debian, pgcli (#794250) and mycli (#794251). Greetings, Lennart Weller

Bug#793249: innoextract: change of type in system_error might break with GCC-5

tags 793249 + confirmed This will most likely be an issue if I undertood the issue correctly. On 2015-07-22 15:33, Matthias Klose wrote: Package: src:innoextract Severity: important Tags: sid stretch User: debian-...@lists.debian.org Usertags: gcc-pr66145 GCC PR libstdc++/66145 is a

Bug#790317: Patch applied upstream

require some additional patches to get it working on even the supported platforms. I'll get back to you On 23 July 2015 16:56:12 CEST, Lennart Weller lenn...@lennartweller.de wrote: So far I only tested the building and compress/decompress functionality in a QEMU VM with arm64. But now

Bug#794250: ITP: pgcli -- CLI for PostgreSQL with syntax highlighting and completion

Package: wnpp Severity: wishlist Owner: Lennart Weller l...@ring0.de * Package name: pgcli Version : 0.18.0 Upstream Author : Amjith Ramanujam amjit...@gmail.com * URL : http://pgcli.com/ * License : BSD-3-clause Programming Lang: Python Description

Bug#794251: ITP: mycli -- CLI for MySQL/MariaDB with syntax highlighting and completion

Package: wnpp Severity: wishlist Owner: Lennart Weller l...@ring0.de * Package name: mycli Version : 1.0.1 Upstream Author : Amjith Ramanujam amjit...@gmail.com * URL : http://mycli.net * License : BSD-3-clause Programming Lang: Python Description : CLI

Bug#790317: Patch applied upstream

So far I only tested the building and compress/decompress functionality in a QEMU VM with arm64. But now that it is upstream I might as well just update the package to a newer git version. A lot of patches in the current package were included in the upstream version by now and homepage etc has

Bug#792275: debian-maintainers: Please add Lennart Weller as Debian Maintainer

Package: debian-maintainers Severity: normal Dear Maintainer, Please add me, Lennart Weller l...@ring0.de, to the Debian Maintainers keyring. You can find the jetring changeset in the attachment. Thank you for your attention, Lennart Weller Comment: Add Lennart Weller l...@ring0.de

Bug#792228: ITP: termdebug -- Tools for recording and replaying terminal I/O

Package: wnpp Severity: wishlist Owner: Lennart Weller l...@ring0.de * Package name: termdebug Version : 2.2 Upstream Author : G.P Halkes * URL : http://os.ghalkes.nl/termdebug.html * License : GPL-3 Programming Lang: C Description : Tools

Bug#790317: Please add ARM64 support

I might do some testing on the debian test boxes for arm64 over the weekend and include it as patch. From my experience with nvtt it might take a while for a patch to be added to upstream. Lennart On 2015-06-28 02:02, Martin Michlmayr wrote: forwarded 790317

Bug#763486: Acknowledgement (nvidia-texture-tools: Please change build dependency to libjpeg-dev (libjpeg-turbo transition))

this. Lennart Am 05.10.2014 19:10, schrieb Yasushi SHOJI: On Sat, 04 Oct 2014 16:54:21 +0200 Lennart Weller l...@ring0.de wrote: I quickly tested the compression/decompression and use of the library in games with the libjpeg-turbo and couldn't find any faults. The new version is now available

Bug#760473: apt method http uses 100% cpu with high transfer rate

Package: apt Version: 1.0.7 Severity: normal Dear Maintainer, The current implementation of the http method puts a much higher load on the CPU than a similar call done in wget or curl. As an example I downloaded a large file from the deb mirror (0ad-data) which is then cached by local squid.

Bug#730524: innoextract: Please update to version 1.4

Hey, The 1.4 release was made in March _2013_ and I read the changelog which didn't have any interesting new features in my opinion. I updated the collab-maint git with the 1.4 nevertheless and will have it uploaded in the next days to unstable. Cheers, Lennart On 26.11.2013 06:59, Stephen Kitt

Bug#721972: debdiff

Totally forgot about the nvtt issue. I uploaded your patch to the collab-maint repository and asked my uploader to do some testing and upload it to unstable. Sorry again, Lennart -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble?

Bug#716713: libtxc-dxtn-s2tc0: S2TC_REFINE_COLORS=ALWAYS (default) creates broken edges

Coming back to this issue as it appearantly won't be fixed upstream anytime soon, does the LOOP fix the issue? Or does it produce new issues? If it works out I could just temporarily set the default to LOOP for the debian package. Lennart Am 11.07.2013 18:36, schrieb Schrober: Package:

Bug#713966: nvidia-texture-tools: OptimalOptions.cmake assumes x86_64 implies athlon64

So the testsuite works fine when nvtt is not optimized for athlon64? On 24.06.2013 13:33, Vincent Cheng wrote: Package: src:nvidia-texture-tools Version: 2.0.8-1+dfsg-3 Severity: important Tags: patch Control: block 712956 by -1 Dear Maintainer, As reported in #712956, one of the amd64

Bug#690469: Possible fix for segfault

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just noting here that I saw the bug report and will test this issue and the patch. I'm just currently a little bit swamped. Am 17.12.2012 01:03, schrieb Laurent Carlier: The following patch fix segfault with atqw/quake4, please test. Regards

Bug#689642: nvidia-texture-tools: fails to build against libtiff5 due to clash of wills over int64/uint64

I already updated the package[1] a while back to fix this issue as br...@canonical.com alerted me to this issue with their build-servers. I haven't pressured my sponsor enough yet to get it uploaded. Will do that today. Sorry for that. [1]

Bug#668645: Acknowledgement (libgl1-mesa-dri: Add a recommendation for a libtxc-dxtn implementation)

Is this under consideration or did I just file it against the wrong package? There is actually some interest in other packages to have s2tc installed by default as games and other applications using s3tc implementations benefit greatly from this package. -- To UNSUBSCRIBE, email to

Bug#668645: libgl1-mesa-dri: Add a recommendation for a libtxc-dxtn implementation

Package: libgl1-mesa-dri Severity: wishlist I suggest adding a recommends dependency to mesa-dri for the package libtxc-dxtn0 provided by libtxc-dxtn-s2tc0. The package is currenly available in unstable S2TC is a most likely patent-free S3TC compatible texture compression. The performance

Bug#667989: ITP: s2tc -- S2TC is a patent-free S3TC compatible texture compression

Package: wnpp Severity: wishlist Owner: Lennart l...@ring0.de * Package name: s2tc Version : 0~git20110809 Upstream Author : Rudolf Polzer divver...@alientrap.org * URL : https://github.com/divVerent/s2tc * License : MIT/X11 Programming Lang: C/C++

Bug#594800: (no subject)

The nvidia-texture-tools are now in debian unstable[1]. If you need any help with creating the package for 0ad drop me a message and I will see how I can be of assistance to you. [1] http://packages.debian.org/source/sid/nvidia-texture-tools -- To UNSUBSCRIBE, email to

Bug#666252: nvidia-texture-tools: FTBFS on architectures not supported upstream

I already changed the the arch builds for my package in collab-maint. I just want to add a few patches which also allow building on kfreebsd-(amd64|i386) before I submit the package again for building Am 30.03.2012 03:21, schrieb Aaron M. Ucko: Package: nvidia-texture-tools Version:

Bug#666254: nvidia-texture-tools: FTBFS on i386 and powerpc: .symbols file mismatches

I already removed the symbols file and use dh_shlibdeps in my new version. Generating symbol files for C++ is a real pain [1] but the shlibdeps seems to work pleasently well. [1] http://lists.debian.org/debian-devel/2012/01/msg00671.html Am 30.03.2012 03:31, schrieb Aaron M. Ucko: Package:

Bug#666010: ITP: nvidia-texture-tools -- image processing and texture manipulation tools

Am 29.03.2012 14:10, schrieb Fabio: If you are packaging 2.0.8 please have a look at the README.txt and patches at: http://trac.wildfiregames.com/browser/ps/trunk/libraries/nvtt/ The issue139.patch is particularly important: it fixed image corruption I noticed on 0.A.D., see here:

Bug#666010: ITP: nvidia-texture-tools -- image processing and texture manipulation tools

Am 29.03.2012 02:17, schrieb Paul Wise: On Wed, 2012-03-28 at 22:40 +0200, Lennart Weller wrote: Because I did not plan to have it submitted to debian when I created it for my ubuntu ppa. Hmm, OK. In what way do you think it's broken? Also I did submit [1] the patch for the library

Bug#666010: ITP: nvidia-texture-tools -- image processing and texture manipulation tools

Am 28.03.2012 04:48, schrieb Paul Wise: On Wed, Mar 28, 2012 at 3:15 AM, Lennart Weller wrote: * Package name: nvidia-texture-tools Version : 2.0.8 Upstream Author : Ignacio Castano icast...@nvidia.com * URL : http://code.google.com/p/nvidia-texture-tools

Bug#666010: ITP: nvidia-texture-tools -- image processing and texture manipulation tools

Am 28.03.2012 13:51, schrieb Paul Wise: On Wed, 2012-03-28 at 12:25 +0200, Lennart Weller wrote: I already got a sponsor for the package and I already completed the packaging a few month back but thanks for offering your help. How come you didn't file an ITP *before* packaging it? That is what

Bug#666010: ITP: nvidia-texture-tools -- image processing and texture manipulation tools

Package: wnpp Severity: wishlist Owner: Lennart Weller l...@ring0.de * Package name: nvidia-texture-tools Version : 2.0.8 Upstream Author : Ignacio Castano icast...@nvidia.com * URL : http://code.google.com/p/nvidia-texture-tools/ * License : MIT/Expat, BSD-2

Bug#666010: ITP: nvidia-texture-tools -- image processing and texture manipulation tools

Am 28.03.2012 01:01, schrieb Ben Hutchings: On Tue, Mar 27, 2012 at 09:15:27PM +0200, Lennart Weller wrote: Package: wnpp Severity: wishlist Owner: Lennart Weller l...@ring0.de * Package name: nvidia-texture-tools Version : 2.0.8 Upstream Author : Ignacio Castano icast

Bug#611175: zsh: VCS_INFO wrongly detects svn repositories

On 27.01.2011 16:58, Frank Terbeck wrote: That sounds reasonable. Do you know how stable the entries file is within the .svn directories with respect to versions? Ie. Does it exist in old versions as well as in recent ones? (My knowledge of subversion's directory contents are rather limited.)

Bug#611175: zsh: VCS_INFO wrongly detects svn repositories

On 27.01.2011 17:43, Frank Terbeck wrote: I suggest, debian does the same (maybe you could update your patch for debian's convenience). One nit: you reported this against version 4.3.6-6; however vcs_info was shipped with zsh 4.3.7 for the first time. ...so unless debian's 4.3.6-6 package

Bug#611175: zsh: VCS_INFO wrongly detects svn repositories

Package: zsh Version: 4.3.6-6 Severity: normal Tags: patch Currently zshs VCS_INFO function wrongly detects svn repositories if an .svn directory exists in the current path. Which also applies to home directories containing for example a ~/.svn/authors file. Instead of checking only for the

Bug#595174: [Pkg-fglrx-devel] Bug#595174: 10.8 blocks opengl wine applications. _XReply: Assertion `!dpy-xcb-reply_data', failed)

That pretty much fixed it. Though the only other fglrx installation I had before was the 10.3-prealpha package from the ubuntu repositories when there was no debian package. This bugreport can be closed. On 27.09.2010 22:02, Michael Gilbert wrote: this specific error has come up before. the

Bug#595174: 10.8 blocks opengl wine applications. _XReply: Assertion `!dpy-xcb-reply_data', failed)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tried to use the Steam client today. Which as it turned out also fails with fglrx 10.7. See next to last line. It probably has something in common with the fact that this is a graphics card from the Evergreen series. I will probably give mesa 7.10

Bug#595174: fglrx-driver: fglrx, 10.8 blocks opengl wine applications. _XReply: Assertion `!dpy-xcb-reply_data', failed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I tested both still throwing the same error. But now the application crashes as well and therefore i have a stacktrace. Maybe this can help identifying the cause of the bug. mme\NCsoft\AionEU\bin32\aion.bin: ../../src/xcb_io.c:452: _XReply:

Bug#595174: [Pkg-fglrx-devel] Bug#595174: Bug#595174: fglrx-driver: fglrx 10.8 blocks opengl wine applications. _XReply: Assertion `!dpy-xcb-reply_data' failed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07.09.2010 20:24, Patrick Matthäi wrote: Am 01.09.2010 21:59, schrieb Lennart Weller: On 01.09.2010 20:34, Patrick Matthäi wrote: Am 01.09.2010 20:14, schrieb Lennart Weller: Package: fglrx-driver Version: 1:10-8-1 Severity: critical Tags

Bug#595174: [Pkg-fglrx-devel] Bug#595174: fglrx-driver: fglrx 10.8 blocks opengl wine applications. _XReply: Assertion `!dpy-xcb-reply_data' failed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07.09.2010 20:55, Patrick Matthäi wrote: Am 07.09.2010 20:38, schrieb Lennart Weller: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07.09.2010 20:24, Patrick Matthäi wrote: Am 01.09.2010 21:59, schrieb Lennart Weller: On 01.09.2010 20:34

Bug#595174: [Pkg-fglrx-devel] Bug#595174: fglrx-driver: fglrx 10.8 blocks opengl wine applications. _XReply: Assertion `!dpy-xcb-reply_data' failed

On 01.09.2010 20:34, Patrick Matthäi wrote: Am 01.09.2010 20:14, schrieb Lennart Weller: Package: fglrx-driver Version: 1:10-8-1 Severity: critical Tags: upstream The current upstream release of fglrx causes applications using opengl in a wine environment to crash instantly. A similar error

  1   2   >