Bug#1010998: simh: Upstream license change conflicts with DFSG
As an alternative, Bob Supnik's "classic" version continues to release - version 2.12-2 just released 25 April 2022 - and would be an excellent replacement. http://simh.trailing-edge.com/ Unfortunately, that version still must overcome the licensing issues outlined in Debian bug #824883.
Bug#1010998: simh: Upstream license change conflicts with DFSG
Package: simh Version: 3.8.1-6.1 Severity: serious Tags: upstream Justification: Policy 2.1 Dear Maintainer, Upstream has added licensing information that is both inaccurate as well as now violates the terms of the DFSG. Specifically: https://github.com/simh/simh/commit/ce2adce632e1a22e6d76d4bf726d6b863373c550 > Additionally, the following restrictions on the use of this software apply. > > Any use of this codebase that changes the code to influence the behavior of > the disk access activities is free to do that as long as anyone doing this > is explicitly not licensed to any subsequent changes to any part of the > codebase made by Mark Pizzolato after that functionality was implemented by > Mark Pizzolato. Changes that qualify for this restriction at least include: > changing the behavior or default of SET AUTOSIZE/NOAUTOSIZE, or any code > in sim_disk.c or any simulator components that use the sim_disk routines. > > All changes to the codebase made after the inclusion of this LICENSE.txt > file in the github simh repository. Discussion: https://groups.io/g/simh/topic/new_license/91108560 If this package is to remain in debian, it will need to move to the non-free section. -- System Information: Debian Release: 11.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-14-amd64 (SMP w/2 CPU threads) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages simh depends on: ii libc6 2.31-13+deb11u3 ii libpcap0.8 1.10.0-2 simh recommends no packages. simh suggests no packages.
Bug#669304: Revisit disabling DNS caching by default
Package: nscd Version: 2.13-27 Upstream changes have resolved the problems in NEWS.Debian. Namely, since at least 2.8 (2008), nscd correctly respects TTL in DNS caching. [1] Would it be possible to remove the now-incorrect statement in NEWS and re-enable DNS caching by default? [1] http://sourceware.org/ml/libc-alpha/2008-04/msg00050.html -- Joan Touzet | jo...@atypical.net | wohali everywhere else -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#644545: Confirmed fixed, thx
Thanks for prompt action on this. Please expedite pushing this into testing if possible; for other users, if you're new to debian pinning, you can pin the package thusly to get this today in your wheezy install: http://www.atypical.net/archive/2012/03/20/how-to-fix-couchdb-in-debian-testing -- Joan Touzet | jo...@atypical.net | wohali everywhere else -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#644545: Finally, a fix...
This grave/critical issue with couchdb 1.1.1 in testing/unstable is that the version of libmozjs that you declare as a dependency is invalid. 1.1.x will NEVER work with anything newer than Spidermonkey 1.8.5 with the setting JSOPTION_ANONFUNFIX enabled. At some point in the last 4 months, libmozjs185-dev added this flag to their build. (The PTS and the changelog for libmozjs185 doesn't say when this happened.) So the easy fix for testing/unstable is to change your dependency from libmozjs-dev to libmozjs185-dev! :) https://issues.apache.org/jira/browse/COUCHDB-1302 has the gritty details. Making couchdb work with the very latest libmozjses is not going to happen in 1.2.x, it's been pushed off to 1.3/2.x. The comment about v10 working is not indicative of the curent code base, it's some patches we're working on that are too radical to slip into 1.1 or 1.2 at this time. I will also contact the libmozjs maintainer to get confirmation he will not disable JSOPTION_ANONFUNFIX on us in the future. -- Joan Touzet | jo...@atypical.net | wohali everywhere else -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#644545: Clarification
I seem to have left a couple of words out: 1.1.x will NEVER work with anything newer than Spidermonkey 1.8.5 *or 1.8.5 without* the setting JSOPTION_ANONFUNFIX enabled. Sorry about that. -- Joan Touzet | jo...@atypical.net | wohali everywhere else -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#440572: wordpress debian config overrides $file, $server in upstream php files
Package: wordpress
Version: 2.2.2-1
Severity: serious
Tags: patch
The use of the variable $file in /etc/wordpress/wp-config.php
overrides $file in many of the upstream package's base files (list
below).
This can lead to unintended security holes, as the included file
(/etc/wordpress/config-$server.php) contains the backend MySQL
access information - *including* the plaintext password. At the very
least, the use of $file breaks WP's theme editor. Similarly, the
variable $server overrides some upstream files' variables as well,
though it's unclear that this presents any immediate concern.
The fix is simple, though perhaps inelegant. Prefix debian- to all
variable names as shown below to prevent namespace collision.
Best regards,
Joan
?php
/** WordPress's Debianised default master config file
Please do NOT edit and read about how the configuration works in the
README.Debian
**/
#http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=435289
$debian-server = preg_replace('/:.*/', , $_SERVER['HTTP_HOST']);
$debian-file = '/etc/wordpress/config-'.strtolower($debian-server).'.php';
if (!file_exists($debian-file)) {
header(HTTP/1.0 404 Not Found);
echo 404 Not found;
}
require_once($debian-file);
define('ABSPATH', '/usr/share/wordpress/');
require_once(ABSPATH.'wp-settings.php');
?
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.13-vs2.0.2.1
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages wordpress depends on:
ii apache2-mpm-prefork [httpd] 2.2.4-3Traditional model for Apache HTTPD
ii libapache2-mod-php5 5.2.3-1+b1 server-side, HTML-embedded scripti
ii libphp-phpmailer 1.73-6 full featured email transfer class
ii mysql-client-5.0 [virtual-mys 5.0.45-1 MySQL database client binaries
ii php5-cgi 5.2.3-1+b1 server-side, HTML-embedded scripti
ii php5-mysql5.2.3-1+b1 MySQL module for php5
wordpress recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#440572: update
One individual has had his debian WordPress blog hacked; it may have been affected by this bug: http://www.phfactor.net/wp/2007/08/25/fnord-updates-downtime-themes/#comment-73174 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
