Bug#1015242: gcc Trademark violation on the horizon

2022-07-18 Thread lkcl
Package: gcc Version: 4:9.2.1-3.1 Severity: serious Tags: upstream Justification: Policy 2.1 short version: gcc is about to become more problematic than rustc with respect to violation of a non-free Trademark License created by the Rust (Mozilla) Foundation.

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

2022-07-18 Thread lkcl
of DFSG] On Mon, Jun 27, 2022 at 3:38 PM lkcl wrote: > > the alternative is to work with the Mozilla Foundation to rewrite their > Trademark License. > > the *intent* is clear, they do not trust Licensees (distributors) to "damage" > the rust API, which is perfectly re

Bug#1013920: Info received (Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel"))

2022-06-27 Thread lkcl
https://www.debian.org/doc/debian-policy/ch-archive.html#the-debian-free-software-guidelines urrr 50% of the clauses of DFSG 2.1 are violated section 2.1 3 is violated 3. Derived Works The license must allow modifications and derived works, and must allow them to be distributed

Bug#1013920: Info received (Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel"))

2022-06-27 Thread lkcl
jeremy i didn't see your reply until i checked online. you spotted the second half: We will usually allow these uses as long as the modifications are (1) relatively small and (2) very clearly communicated to end-users. i did not include this because DFSG 8 is already violated by

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

2022-06-27 Thread lkcl
the alternative is to work with the Mozilla Foundation to rewrite their Trademark License. the *intent* is clear, they do not trust Licensees (distributors) to "damage" the rust API, which is perfectly reasonable. therefore, why don't they just say that? "if a distributor performs source

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

2022-06-27 Thread lkcl
hi Geert, sorry i have an odd mailer which can only toppost. as in the initial post, i found a link that indicates that such explicit requests are in direct violation of DFSG Section 8, namely that others (including Derivatives) may take the source that goes through Debian and continue to use

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

2022-06-27 Thread lkcl
eal but I will chat with some people on the >Rust side about this. > >Cheers, >Sylvestre (who managed the iceweasel/firefox thing) > > >Le 27/06/2022 à 13:52, lkcl a écrit : >> Package: rust-all >> Severity: serious >> Tags: upstream >> Justification: Po

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

2022-06-27 Thread lkcl
Package: rust-all Severity: serious Tags: upstream Justification: Policy 2.1 https://internals.rust-lang.org/t/rust-s-freedom-flaws/11533 https://lists.debian.org/debian-legal/2021/05/msg6.html https://foundation.rust-lang.org/policies/logo-policy-and-media-guide/ this is an extremely

Bug#929709: libgdbm6: file exists in libgdbm-dev as well as gdbm

2019-05-29 Thread lkcl
Package: libgdbm6 Version: 1.18.1-4 Severity: serious Justification: 2 Unpacking libgdbm-dev:amd64 (1.18.1-4) ... dpkg: error processing archive /var/cache/apt/archives/libgdbm-dev_1.18.1-4_amd64.deb (--unpack): trying to overwrite '/usr/share/info/gdbm.info.gz', which is also in package

Bug#919882: firefox-esr: linker options under investigation for 32-bit builds

2019-01-20 Thread lkcl
Package: firefox-esr Version: 60.4.0esr-1 Severity: serious Justification: Policy 10.1 https://lists.debian.org/debian-devel/2019/01/msg00069.html https://sourceware.org/bugzilla/show_bug.cgi?id=22831#c25 under investigation are some options to get firefox to build natively on 32-bit

Bug#824848: xchat current debian/testing is out-of-date and specifically depends on libperl5.20

2016-05-20 Thread lkcl
files there, resulting in a conflict, whoops. with dpkg --force -i xchat*.deb that problem is overcome but it's still bd :) root@bigmac:/home/lkcl/src/xchat-2.8.8# dpkg -L xchat /. /usr /usr/lib /usr/lib/xchat /usr/lib/xchat/plugins /usr/lib/xchat/plugins/perl.so /usr/lib/xchat/plugins

Bug#814331: repsnapper: nothing displayed in 3d window

2016-02-10 Thread lkcl
Package: repsnapper Version: 2.4a0-1 Severity: grave Justification: renders package unusable the entire 3D pane is completely blank. there's no grid, no object (prior to loading a model and after loading a model). settings are those that are in http://hands.com/~lkcl/repsnapper_weirdness.tgz

Bug#745038: sgml-base: dependency xml-core missing (missing update-xmlcatalog)

2014-04-17 Thread lkcl
Package: sgml-base Version: 1.26+nmu3 Severity: serious Justification: 2 the command update-xmlcatalog is used by sgml-base however the dependency xml-core is missing. this is from an upgrade of a debian/wheezy system to debian-testing (sgml-data-2.0.9-1) which is now in an unusable state and

Bug#726530: fvwm: random segfault

2013-10-16 Thread lkcl
Package: fvwm Version: 1:2.6.5.ds-2 Severity: grave Justification: causes non-serious data loss listed this as grave as it's the closest option available: data-loss is occurring because fvwm is dying taking all windows (e.g. firefox and all vi sessions) with it. this may not specifically be

Bug#657075: python-hulahop

2012-02-17 Thread lkcl luke
dear experimenter, please can you try the following: ii xulrunner-9.09.0.1-1 XUL + XPCOM application runner ii xulrunner-dev9.0.1-1 Development files for the Gecko engine library ii python-xpcom