Bug#775638: IPv6 database is corrupt
Okay, I sorted it out. The reason the city DB was corrupted is because we were putting so many locations into the location file that we were overflowing the addressable places to put them. The Maxmind format uses 3 bytes to store offsets, so when we exceed offset 0xFF our offsets wrap around to 0 and nothing good happens after that. I added a check for the overflow condition, so the code that creates city DBs errors out instead of silently making a corrupted database. Coincidentally, we were just barely over the size limit for Maxmind's format, which is why a fairly small number of entries were affected. That left the issue of why we were overflowing in the first place. It turns out that a large fraction of the locations in the CSV data aren't actually needed (aren't associated with any IP address). In order to fit the data into a .dat file in Maxmind's format, we have to scan for those and remove them. There are a huge number of them, as I said -- removing them shrinks the .dat file from 31 MB to 20 MB. I've attached a patch which does both of those things. I've built gdnsd successfully with this patch applied and the DBs rebuilt. I've also tested it by running geoiplookup against the database for several addresses. The patch also fixes the area code and metro code for US addresses, which I noticed were backwards (switched with one another). Hope this helps, let me know if you see any issues. -Andrew On Fri, Jan 23, 2015 at 11:52 AM, Andrew Moise andrew.mo...@gmail.com wrote: Hi Patrick. I tracked it down to a few broken entries in the city DB. It looks like the DB creation code makes almost all the entries correctly, but there are a couple of them that come out corrupted: (jessie)moise@localhost:~$ geoiplookup 1.120.146.170 GeoIP Country Edition: AU, Australia GeoIP City Edition, Rev 1: GP, ���-��-��%��%��%��%��- �- �-Ɣ-��%��%�-��-x�-v�-, N/A, N/A, N/A, -180.00, -179.993500, 0, 0 GeoIP ASNum Edition: AS30722 Vodafone Omnitel B.V. Note that's with a local build of the database -- that particular IP address may not be corrupted in the actual jessie database. In that local DB, as in the actual jessie database, almost all the entries are correct, just there are a handful that look like that one. I've been busy the last couple days, but I expect that I'll get enough time today to actually track down what's going wrong and fix it. -Andrew On Jan 23, 2015 9:43 AM, Patrick Matthäi pmatth...@debian.org wrote: Hi Andrew, do you have got any news? :) Am 20.01.2015 um 18:43 schrieb Andrew Moise: Thanks Patrick. One note - just like the v6 issue, the gdnsd test suite is detecting a genuine problem in the city DB. It is something wrong with the city DB creation tools that's causing it (i.e. not just an issue with the gdnsd tests). I just haven't finished tracking down exactly what the issue is yet. -Andrew On Jan 20, 2015 12:22 PM, Patrick Matthäi pmatth...@debian.org wrote: tag #775638 + confirmed clone #775638 -1 reassign -1 geoip-bin retitle -1 geoip-generator produces faulty v6/city database severity -1 grave found -1 1.6.2-3 thanks Hi Am 18.01.2015 um 05:21 schrieb Debian Bug Tracking System: Processing commands for cont...@bugs.debian.org: reassign 775638 geoip-database 20141027-1 Bug #775638 [src:gdnsd] gdnsd: FTBFS in jessie: dh_auto_test: make -j1 test returned exit code 2 Bug reassigned from package 'src:gdnsd' to 'geoip-database'. No longer marked as found in versions gdnsd/2.1.0-1. Ignoring request to alter fixed versions of bug #775638 to the same values previously set Bug #775638 [geoip-database] gdnsd: FTBFS in jessie: dh_auto_test: make -j1 test returned exit code 2 Marked as found in versions geoip-database/20141027-1. retitle 775638 IPv6 database is corrupt Bug #775638 [geoip-database] gdnsd: FTBFS in jessie: dh_auto_test: make -j1 test returned exit code 2 Changed Bug title to 'IPv6 database is corrupt' from 'gdnsd: FTBFS in jessie: dh_auto_test: make -j1 test returned exit code 2' severity 775638 grave Bug #775638 [geoip-database] IPv6 database is corrupt Severity set to 'grave' from 'serious' thanks thanks for spotting it. Curious that no one (also myself!) spotted it. The patch for the v6 database is just: --- geoip/branches/jessie/debian/src/geoip-csv-to-dat.cpp 2015-01-19 18:50:04 UTC (rev 5693) +++ geoip/branches/jessie/debian/src/geoip-csv-to-dat.cpp 2015-01-20 08:31:03 UTC (rev 5694) @@ -959,6 +959,7 @@ address_family = AF_INET; break; case '6': + database_type = GEOIP_COUNTRY_EDITION_V6; address_family = AF_INET6; break; case 'i': But Andrew found out that there is also an issue with the city database, which is working in general, but the gdnsd tests also fail. -- /* Mit
Bug#775638: IPv6 database is corrupt
Hi Patrick. I tracked it down to a few broken entries in the city DB. It looks like the DB creation code makes almost all the entries correctly, but there are a couple of them that come out corrupted: (jessie)moise@localhost:~$ geoiplookup 1.120.146.170 GeoIP Country Edition: AU, Australia GeoIP City Edition, Rev 1: GP, ���-��-��%��%��%��%��-�-�-Ɣ-��%��%�-��-x�-v�-, N/A, N/A, N/A, -180.00, -179.993500, 0, 0 GeoIP ASNum Edition: AS30722 Vodafone Omnitel B.V. Note that's with a local build of the database -- that particular IP address may not be corrupted in the actual jessie database. In that local DB, as in the actual jessie database, almost all the entries are correct, just there are a handful that look like that one. I've been busy the last couple days, but I expect that I'll get enough time today to actually track down what's going wrong and fix it. -Andrew On Jan 23, 2015 9:43 AM, Patrick Matthäi pmatth...@debian.org wrote: Hi Andrew, do you have got any news? :) Am 20.01.2015 um 18:43 schrieb Andrew Moise: Thanks Patrick. One note - just like the v6 issue, the gdnsd test suite is detecting a genuine problem in the city DB. It is something wrong with the city DB creation tools that's causing it (i.e. not just an issue with the gdnsd tests). I just haven't finished tracking down exactly what the issue is yet. -Andrew On Jan 20, 2015 12:22 PM, Patrick Matthäi pmatth...@debian.org wrote: tag #775638 + confirmed clone #775638 -1 reassign -1 geoip-bin retitle -1 geoip-generator produces faulty v6/city database severity -1 grave found -1 1.6.2-3 thanks Hi Am 18.01.2015 um 05:21 schrieb Debian Bug Tracking System: Processing commands for cont...@bugs.debian.org: reassign 775638 geoip-database 20141027-1 Bug #775638 [src:gdnsd] gdnsd: FTBFS in jessie: dh_auto_test: make -j1 test returned exit code 2 Bug reassigned from package 'src:gdnsd' to 'geoip-database'. No longer marked as found in versions gdnsd/2.1.0-1. Ignoring request to alter fixed versions of bug #775638 to the same values previously set Bug #775638 [geoip-database] gdnsd: FTBFS in jessie: dh_auto_test: make -j1 test returned exit code 2 Marked as found in versions geoip-database/20141027-1. retitle 775638 IPv6 database is corrupt Bug #775638 [geoip-database] gdnsd: FTBFS in jessie: dh_auto_test: make -j1 test returned exit code 2 Changed Bug title to 'IPv6 database is corrupt' from 'gdnsd: FTBFS in jessie: dh_auto_test: make -j1 test returned exit code 2' severity 775638 grave Bug #775638 [geoip-database] IPv6 database is corrupt Severity set to 'grave' from 'serious' thanks thanks for spotting it. Curious that no one (also myself!) spotted it. The patch for the v6 database is just: --- geoip/branches/jessie/debian/src/geoip-csv-to-dat.cpp 2015-01-19 18:50:04 UTC (rev 5693) +++ geoip/branches/jessie/debian/src/geoip-csv-to-dat.cpp 2015-01-20 08:31:03 UTC (rev 5694) @@ -959,6 +959,7 @@ address_family = AF_INET; break; case '6': + database_type = GEOIP_COUNTRY_EDITION_V6; address_family = AF_INET6; break; case 'i': But Andrew found out that there is also an issue with the city database, which is working in general, but the gdnsd tests also fail. -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775638: IPv6 database is corrupt
Thanks Patrick. One note - just like the v6 issue, the gdnsd test suite is detecting a genuine problem in the city DB. It is something wrong with the city DB creation tools that's causing it (i.e. not just an issue with the gdnsd tests). I just haven't finished tracking down exactly what the issue is yet. -Andrew On Jan 20, 2015 12:22 PM, Patrick Matthäi pmatth...@debian.org wrote: tag #775638 + confirmed clone #775638 -1 reassign -1 geoip-bin retitle -1 geoip-generator produces faulty v6/city database severity -1 grave found -1 1.6.2-3 thanks Hi Am 18.01.2015 um 05:21 schrieb Debian Bug Tracking System: Processing commands for cont...@bugs.debian.org: reassign 775638 geoip-database 20141027-1 Bug #775638 [src:gdnsd] gdnsd: FTBFS in jessie: dh_auto_test: make -j1 test returned exit code 2 Bug reassigned from package 'src:gdnsd' to 'geoip-database'. No longer marked as found in versions gdnsd/2.1.0-1. Ignoring request to alter fixed versions of bug #775638 to the same values previously set Bug #775638 [geoip-database] gdnsd: FTBFS in jessie: dh_auto_test: make -j1 test returned exit code 2 Marked as found in versions geoip-database/20141027-1. retitle 775638 IPv6 database is corrupt Bug #775638 [geoip-database] gdnsd: FTBFS in jessie: dh_auto_test: make -j1 test returned exit code 2 Changed Bug title to 'IPv6 database is corrupt' from 'gdnsd: FTBFS in jessie: dh_auto_test: make -j1 test returned exit code 2' severity 775638 grave Bug #775638 [geoip-database] IPv6 database is corrupt Severity set to 'grave' from 'serious' thanks thanks for spotting it. Curious that no one (also myself!) spotted it. The patch for the v6 database is just: --- geoip/branches/jessie/debian/src/geoip-csv-to-dat.cpp 2015-01-19 18:50:04 UTC (rev 5693) +++ geoip/branches/jessie/debian/src/geoip-csv-to-dat.cpp 2015-01-20 08:31:03 UTC (rev 5694) @@ -959,6 +959,7 @@ address_family = AF_INET; break; case '6': + database_type = GEOIP_COUNTRY_EDITION_V6; address_family = AF_INET6; break; case 'i': But Andrew found out that there is also an issue with the city database, which is working in general, but the gdnsd tests also fail. -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#484107: iscsitarget: Fails to remove if IET is not active
This seems to still be a problem for me: Preparing to replace iscsitarget 0.4.15+svn148-2 (using .../iscsitarget_0.4.16+svn162-3_i386.deb) ... Removing iSCSI enterprise target devices: failed with reason :Connection refused. invoke-rc.d: initscript iscsitarget, action stop failed. dpkg: warning - old pre-removal script returned error exit status 1 dpkg - trying script from the new package instead ... Removing iSCSI enterprise target devices: failed with reason :Connection refused. invoke-rc.d: initscript iscsitarget, action stop failed. dpkg: error processing /var/cache/apt/archives/iscsitarget_0.4.16+svn162-3_i386.deb (--unpack): subprocess new pre-removal script returned error exit status 1 Starting iSCSI enterprise target service: FATAL: Module iscsi_trgt not found. netlink fd: Connection refused failed. Errors were encountered while processing: /var/cache/apt/archives/iscsitarget_0.4.16+svn162-3_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Cheers. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#476583: amanda-server: File conflict with amanda-common
Package: amanda-server Version: 1:2.5.2p1-2 Severity: serious Justification: Policy 7.5.1 When I attempt to upgrade amanda from version 2.5.2pl-2 to version 2.5.2pl-3, I get: Preparing to replace amanda-server 1:2.5.2p1-2 (using .../amanda-server_1%3a2.5.2p1-3_i386.deb) ... Unpacking replacement amanda-server ... dpkg: error processing /var/cache/apt/archives/amanda-server_1%3a2.5.2p1-3_i386.deb (--unpack): trying to overwrite `/usr/sbin/ammt', which is also in package amanda-common dpkg-deb: subprocess paste killed by signal (Broken pipe) Presumably it will start working fine once I run 'apt-get -f install', since amanda-common was upgraded right after, but amanda-server should still have the appropriate Replaces: field set so that it'll work the first time. Cheers. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages amanda-server depends on: ii amanda-common 1:2.5.2p1-3 Advanced Maryland Automatic Networ ii bsd-mailx [mailx] 8.1.2-0.20071201cvs-2 A simple mail user agent ii libc6 2.7-10GNU C Library: Shared libraries ii libncurses55.6+20080405-1Shared libraries for terminal hand ii libreadline5 5.2-3 GNU readline and history libraries ii mailx 1:20071201-2 Transitional package for mailx ren amanda-server recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#390369: -o is not one option
On 3/22/07, peter green [EMAIL PROTECTED] wrote: someone familiar with getopt will be required to provide a patch for nbsmtp that provides similar functionality. Surely it can't take that much complexity to get nbsmtp to throw away any -o options that are passed in on the command line? This is a very serious bug (IMHO it's critical, since it breaks unrelated software on the system). I wasn't really paying attention, since I uninstalled nbsmtp long ago, but it seems ridiculous that (months after the bug is filed) a package is still in etch that breaks email on any system where it's installed. I'll see if I can put together a patch this weekend. Cheers. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#308200: blackbox-themes copyright file
On Sat, Jul 08, 2006 at 08:13:50AM -0400, Bruno Barrera C. wrote: On Sun, 2006-06-25 at 11:48 -0400, Andrew Moise wrote: Bruno, would you object if I NMUed a new version of this package, with the copyright file I attached earlier in this bug report? I would prefer if we can discuss the changes in IRC or through Email. What do you plan to do? I'm interested in to see that it can be done. I would plan to replace the copyright file with the one I attached at http://bugs.debian.org/cgi-bin/bugreport.cgi/copyright?bug=308200;msg=65;att=1 (replacing /usr/share/GPL-2 with /usr/share/common-licenses/GPL-2; that's a typo). I would also include real names for [EMAIL PROTECTED] and [EMAIL PROTECTED] if you happen to know their real names. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#308200: blackbox-themes copyright file
Bruno, would you object if I NMUed a new version of this package, with the copyright file I attached earlier in this bug report? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#308200: blackbox-themes copyright file
On Wed, Jun 07, 2006 at 10:24:37PM +0200, Francesco Poli wrote: Since you already got in touch with the relevant copyright holders, could you please clarify which images are currently shipped in blackbox-themes without source? Sure. I actually didn't ask about source image redistribution for most of the images that are still being distributed in blackbox-themes 0.3. Here are the statuses for the ones that are: === Igloo background * Author: Carlos Oliva G. [EMAIL PROTECTED] * MIT license is okay. I didn't ask about source. === Reaction background * Author: Youngjin Hahn [EMAIL PROTECTED] * MIT license is okay. I didn't ask about source. === Whitebox background * Author: Volkan Yazıcı [EMAIL PROTECTED] * Source distribution would be OK, but he's deleted the source (.psd or similar, I believe). I wish I can help you about this, but it's been a quite long time since I spent time on graphics. I've deleted my whole archive with DebArt [http://www.linuks.mine.nu/volkany/] sources. Sorry about this; I don't design graphics anymore. === Rootbox background * Author: [EMAIL PROTECTED] * I haven't talked to this guy. For completeness, here are the statuses for the images that were in blackbox-themes 0.2 that have been removed from 0.3 (the ones where I could find a background image creator to contact, that is). === Bombskew background * Copyright: © 2003 Marcus Larsson [EMAIL PROTECTED] * Upstream: http://themes.freshmeat.net/projects/bombskew/ * MIT license is okay. Doesn't have the source anymore. === Eon Silver * Copyright: Bandar Hassan Raffa [EMAIL PROTECTED] * Upstream: http://www.sadeem.net/tux.html * Distribution within Debian is okay, but he doesn't seem to want to allow further redistribution, or to share the source. He offered to create a separate Debian-themed background and allow source redistribution, but I haven't heard back about it yet. Also, the penguin was created by someone else. === Nijikon * Copyright: Igor Pruchanskiy [EMAIL PROTECTED] * Upstream: http://www.usinglinux.org/doc/Themes/bb/Nijikon-0.60.0.tar.gz * Distribution within Debian is okay, but he doesn't seem to want to allow further redistribution. === Nva91 * Copyright: © 2002 Kevin Stacey [EMAIL PROTECTED] and [EMAIL PROTECTED] * Upstream: http://www.deviantart.com/deviation/646793/ (sort of) * MIT license is okay. I didn't ask about source. === Void * Couldn't contact the background author. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#308200: blackbox-themes copyright file
On Fri, Jun 02, 2006 at 12:49:09PM +0200, Francesco Poli wrote: Is source available (and included in the .orig.tar.gz archive) for every part of the package? If this is the case, then the package is OK for main. The style files are really all source; they're just text configuration files. The image files don't include anything that resembles source, but I'm choosing to assume that DFSG #2 doesn't apply to images as long as they are being distributed legally and with permission. I'm not planning on complaining on that basis, IOW. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#308200: blackbox-themes copyright file
Okay, here's a copyright file which I believe to be correct for blackbox-themes 0.3. It would be a little nicer if it included real names for [EMAIL PROTECTED] and [EMAIL PROTECTED] It also carries the added bonus that, thanks to Bruno's repackaging, all the styles with images are licensed under non-GPL licenses, and everything seems legal to distribute and okay for main. == == Copyright == This package is an aggregation of styles and backgrounds from many authors. The copyright information for each style is as follows. On Debian systems, the text of the GPL v2 and BSD licenses can be found in /usr/share/GPL-2 and /usr/share/common-licenses/BSD respectively. Some of the authors below have agreed to provide their work under the MIT license (some by private arrangement over email) as well. The MIT license is included at the bottom of this file, for reference. === BlackGold style * Copyright: (C) 2005 [EMAIL PROTECTED] * Upstream: http://themes.freshmeat.net/projects/blackgold/ * License: GPL v2 === BlueVision style * Copyright (C) 2005 Alexander Polakov [EMAIL PROTECTED] * Upstream: http://themes.freshmeat.net/projects/bluevision/ * License: BSD === Daurple style * Copyright (C) 2005 [EMAIL PROTECTED] * Upstream: http://themes.freshmeat.net/projects/daurple/ * License: GPL v2 === Igloo style background * Copyright: (C) 2004 Carlos Oliva G. [EMAIL PROTECTED] * Upstream: None * License: MIT === Reaction style background * Copyright: (C) 2000 Youngjin Hahn [EMAIL PROTECTED] * Upstream: http://themes.freshmeat.net/projects/reaction/ * License: MIT === RootBox style * Copyright: (C) 2005 [EMAIL PROTECTED] * Upstream: http://themes.freshmeat.net/projects/rootbox/ * License: BSD === WhiteBox style background * Copyright: (C) 2003 Volkan Yazıcı [EMAIL PROTECTED] * Upstream: http://freshmeat.net/projects/whitebox/ * License: MIT = === The MIT license = Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the Software), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Bug#308200: closed by [EMAIL PROTECTED] (Bruno Barrera C.)
On Sun, 21 May 2006 00:43:11 +0200, Francesco Poli wrote: I don't agree. The GPL is *not* a bad license for images: forcing source distribution is a feature, not a bug. I was unclear: It's a bad license for images because it seems to be extremely rare, for some reason, for people to keep the source for images around. For most of the people I asked about licensing terms, I asked first if they were okay with providing the source and licensing the image under the GPL. Every single person either said that they didn't have the source anymore, or explicitly that I couldn't have the source. I'm not against non-copyleft licenses, but providing source has to be done anyway in order to call a work DFSG-free. Hence Debian should provide source even if the images were under a MIT license. Huh. If DFSG #2 is going to be applied to images, then I guess blackbox-themes should be moved to non-free. That would actually be a useful option, since it would allow the inclusion of themes where the author was okay with allowing use within Debian, but not redistribution (IIRC there was at least one of those in the 0.2 package). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#308200: closed by [EMAIL PROTECTED] (Bruno Barrera C.)
On Fri, May 26, 2006 at 11:47:40PM +0200, Francesco Poli wrote: There's a misconception here. The source code for a work is defined (in GPLv2, section 3) as the preferred form of the work for making modifications to it. If the author discards a form of his/her work, this form is apparently *not* the one he/she would prefer for making modifications. As a consequence, that form is, by definition, *not* source. Does that mean that I can delete the source to a program, and distribute the binary under the GPL, since I've indicated which form I prefer to make modifications to? :-) I certainly would define the source of an image created in photoshop as the .psd file, but my opinion isn't very authoritative, certainly. then I guess blackbox-themes should be moved to non-free. As I stated, it depends. Maybe source is made available for some of them. Upstream authors should be asked to clarify which form they prefer for making modifications, whenever it's not apparent. If we already have such a form, all is well. If we don't, then upstream should be persuaded to provide it. Only when the latter fails, the work must be moved out of main (and/or contrib). I've asked many upstream authors about this (I can post full details if you like). As I said, the authors I asked unanimously informed me that I couldn't have the source for one reason or another (generally because they didn't have it anymore). Having a package moved from main to non-free would not a be a win for anyone, I would say. So I hope we can obtain the missing sources (if any) and keep blackbox-themes in main. I agree that having all the themes freely licensed with source would be a nice goal. Really, though, I'd settle for getting debian/copyright correct and having the package in the correct section of Debian, whichever that might be :-). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#308200: closed by [EMAIL PROTECTED] (Bruno Barrera C.) (Bug#308200: fixed in blackbox-themes 0.3)
On Thu, May 18, 2006 at 10:34:17PM -0700, Debian Bug Tracking System wrote: Their explanation is attached below. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact [EMAIL PROTECTED] (Bruno Barrera C.) by replying to this email. I know I sound like a pain in the ass, but the new copyright file still doesn't list detailed copyright and upstream information. Also, the GPL is a bad license to apply to images, because it requires source distribution (photoshop or whatever), not just free distribution of the final product. For that reason, I'd been asking people about MIT licensing, which everyone I contacted was willing to provide. Read http://lists.debian.org/debian-devel-announce/2003/12/msg7.html for information about what you need to include in the debian/copyright file. I've attached the copyright file that I had compiled for the old Debian package based on contacting people and asking them about licensing. It looks like you've taken out all of the styles that I hadn't managed to obtain permission to redistribute, so I assume that you've also contacted people and gotten their permission to redistribute these files, so the only problem now is fixing the copyright file to include the needed information. This package is an aggregation of styles and backgrounds from many authors. The copyright information for each style is as follows. All of the authors below have agreed to provide their work under the MIT license (some by private arrangement over email). The MIT license is included at the bottom of this file, for reference. === Igloo * Copyright: © 2004 Carlos Oliva G. [EMAIL PROTECTED] * Upstream: None * License: MIT === Nva91 style * Copyright: © 2002 Jesse Farmer [EMAIL PROTECTED] * Upstream: http://themes.freshmeat.net/projects/nva91/ * License: MIT === Nva91 background * Copyright: © 2002 Kevin Stacey [EMAIL PROTECTED] and [EMAIL PROTECTED] * Upstream: http://www.deviantart.com/deviation/646793/ * License: MIT === Bombskew style * Copyright: © 2003 Marcus Larsson [EMAIL PROTECTED] * Upstream: http://themes.freshmeat.net/projects/bombskew/ * License: MIT === Bombskew background * Copyright: © 2002 Eric Carl [EMAIL PROTECTED] * Upstream: http://www.deviantart.com/deviation/170777/ * License: MIT === Reaction style background * Copyright: © 2000 Youngjin Hahn [EMAIL PROTECTED] * Upstream: http://themes.freshmeat.net/projects/reaction/ * License: MIT === WhiteBox style background * Copyright: © 2003 Volkan Yazıcı [EMAIL PROTECTED] * Upstream: http://freshmeat.net/projects/whitebox/ * License: MIT = === The MIT license = Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the Software), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Bug#347672: Could you please provide some more info on crash in evolution?
I re-upgraded to 2.4.2.1-1 recently (because 2.2.3-5 stopped working for me as well), and it did display a problem with freezing on strartup. 2.4.2.1-1.1 does not display this freezing problem, and generally seems to work. I'm moderately confident that it's the same freezing problem I mentioned earlier in this bug. In any case, I'm switching away from evolution now. Thanks for the followup. -- Andrew Moise [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#347672: evolution: Evolution 2.4.2.1 freezes on startup
On Wed, 2006-02-01 at 01:13 +0100, Ciro Mattia Gonano wrote: sadly, I had to stop using Evolution :( I'm still using evolution; I've downgraded to a still-working-for-me version. I'm willing to try any debugging steps you think would be helpful with the new version. I have also to tell that I'm not using Gnome as my DM, but I'm using Enlightenment DR17 (cvs) with gnome-settings-daemon running under it. Maybe it can help. I am also not running gnome as a DM. I run evolution under blackbox. -- Andrew Moise [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#347672: evolution: Evolution 2.4.2.1 freezes on startup
On Tue, 2006-01-31 at 20:59 +0100, Loïc Minier wrote: Since last update Evolution keeps freezing at startup Could you please try to killall evolution-data-server-1.4? For me at least, this did not help. I tried this (as well as rebooting the machine) when I first had this problem, and had no success. -- Andrew Moise [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#347672: evolution: Evolution 2.4.2.1 freezes on startup
values an ii libgtk2.0-0 2.8.10-1 The GTK+ graphical user interface ii libgtkhtml3.8 3.8.1-1HTML rendering/editing library - r ii libice6 6.9.0.dfsg.1-4 Inter-Client Exchange library ii libjpeg62 6b-11 The Independent JPEG Group's JPEG ii libkrb53 1.4.3-5MIT Kerberos runtime libraries ii libldap2 2.1.30-12 OpenLDAP libraries ii libnspr4 2:1.7.12-1 Netscape Portable Runtime Library ii libnss3 2:1.7.12-1 Network Security Service Libraries ii liborbit2 1:2.12.4-1 libraries for ORBit2 - a CORBA ORB ii libpango1.0-0 1.10.2-1 Layout and rendering of internatio ii libpisock80.11.8-17 Library for communicating with a P ii libpisync00.11.8-17 Synchronization library for PalmOS ii libpng12-01.2.8rel-5 PNG library - runtime ii libpopt0 1.7-5 lib for parsing cmdline parameters ii libsm66.9.0.dfsg.1-4 X Window System Session Management ii libsoup2.2-8 2.2.6-1an HTTP library implementation in ii libtasn1-20.2.17-1 Manage ASN.1 structures (runtime) ii libx11-6 6.9.0.dfsg.1-4 X Window System protocol client li ii libxcursor1 1.1.3-1X cursor management library ii libxext6 6.9.0.dfsg.1-4 X Window System miscellaneous exte ii libxi66.9.0.dfsg.1-4 X Window System Input extension li ii libxinerama1 6.9.0.dfsg.1-4 X Window System multi-head display ii libxml2 2.6.23.dfsg.1-0.1 GNOME XML library ii libxrandr26.9.0.dfsg.1-4 X Window System Resize, Rotate and ii libxrender1 1:0.9.0.2-1X Rendering Extension client libra ii zlib1g1:1.2.3-9 compression library - runtime Versions of packages evolution recommends: pn evolution-plugins none (no description available) ii gnome-desktop-data2.12.2-2 Common files for GNOME 2 desktop a pn gnome-pilot-conduits none (no description available) ii mozilla-psm 2:1.7.12-1 The Mozilla Internet application s ii spamassassin 3.1.0a-2 Perl-based spam filter using text -- Andrew Moise [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#308200: blackbox-themes: Copyright status still not resolved
Has there been any more progress on this? 250 days is a long time for Debian to be (apparently) distributing someone else's copyrighted works without a license. Again, if you want me to do any of the work associated with fixing this bug, say the word; I appreciate the work you've done for Debian and I don't want to make more work for you. -- Andrew Moise [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#307299: Perl taint error on TWiki diffs page after twiki/apache upgrade
Would it be possible to downgrade this bug to normal? Even if it is a real bug (I cannot reproduce it, though I didn't try very hard), it certainly should not be grave, and it is currently preventing twiki from entering testing. -- Andrew Moise [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#308200: blackbox-themes: Copyright status still not resolved
Package: blackbox-themes Version: 0.2 Severity: serious Justification: Policy 2.3 The copyright statement in debian/copyright has been fixed to declare that the whole package is copyright Bruno Barrera; that's not right. While a lot of the upstreams don't seem to take copyright and licensing issues very seriously, that doesn't mean they're not important for Debian. Here, AFAICT, are the copyright statuses of each section of this package. Some might present serious problems, usually with the copyright status of the background image. Styles that look definitely legal to distribute: Reaction, WhiteBox Styles that look okay, but seem to need an explicit indication of licensing terms (via email from the author or whatever): Bombskew, Eon Silver, Igloo, Nva91, Void Style that looks to me like it's illegal to distribute: Nijikon I'm sorry if this seems pedantic, but licensing is important (particularly in a case like Nijikon, where it's not just a we didn't get all the paperwork together thing but a the guy who made the image actively doesn't want it to be used and distributed like this thing). I apologize in advance for any mistakes or licensing arrangements I'm not aware of in the listing below. If you'd like, I can try to contact the upstream authors and artists and find out what their wishes are, and try to get them to license their works under more explicit terms when necessary. Here's the long list of copyright statuses I was able to figure out: === Bombskew style * Copyright: [EMAIL PROTECTED] * Upstream: http://themes.freshmeat.net/projects/bombskew/ * License: GPL === Bombskew background * Copyright: eric- at deviantART * Upstream: Presumably somewhere on deviantart.com; I couldn't find it. * License: No indication is given of special licensing terms, and deviantart.com definitely seems to think that redistribution of images without permission is not okay (see http://about.deviantart.com/policy/etiquette/). === Eon Silver style * Copyright: [EMAIL PROTECTED], but based on SimpleSmoothGray and Platinum. * SimpleSmoothGray is from http://fluxbox.sourceforge.net/themes.php, with no explicit licensing terms (though fluxbox is BSD-style licensed so it's probably okay). * Platinum is from http://themes.freshmeat.net/projects/platinum/ and is GPL licensed. * Upstream: http://themes.freshmeat.net/projects/eon01/ * License: GPL === Eon Silver background * Copyright: Bandar Hassan Raffa [EMAIL PROTECTED] * Upstream: http://www.sadeem.net/tux.html * License: This site is a small gift to all Linux and Mac users. No explicit licensing terms that I can see. === Igloo * Copyright: Carlos Oliva G. [EMAIL PROTECTED] * Upstream: Couldn't find * License: Couldn't find (probably okay). === Nijikon style * Copyright: [EMAIL PROTECTED] * Upstream: Couldn't find; I used http://ftp.riken.go.jp/pub/X11/themes/bb/Nijikon-0.60.0-200012050156.tar.gz * License: No explicit terms. === Nijikon background * Copyright: [EMAIL PROTECTED] * Upstream: http://www.deaddreamer.com/v10/freeze/toonz.html * License: Definitely not okay. every publication or redistribution requires my written permission if you know anyone who uses parts of my images ... contact me. === Nva91 style * Copyright: [EMAIL PROTECTED], or possibly [EMAIL PROTECTED] * Upstream: http://themes.freshmeat.net/projects/nva91/ * License: GPL === Nva91 background * Copyright: Venox and Niytros * Upstream: http://www.deviantart.com/deviation/646793/ (sort of) * License: No explicit terms. === Reaction style (presumably) background * Copyright: Youngjin Hahn [EMAIL PROTECTED] * Upstream: http://themes.freshmeat.net/projects/reaction/ * License: GPL === Void style * Copyright: [EMAIL PROTECTED] * Upstream: Couldn't find; I used http://ftp.riken.go.jp/pub/X11/themes/bb/Void-0.60.0-26131620.tar.gz * License: No explicit terms. === Void background * I think I got this from endeffect.com, or one of their affiliates. It looked purty ... I couldn't find it, but I think it's safe to say no explicit terms. * The style file does say My thanks to fli73, where I got this wonderful background. === WhiteBox style background * Copyright: Volkan YAZICI [EMAIL PROTECTED] * Upstream: http://freshmeat.net/projects/whitebox/ * License: GPL -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10-1-686-smp Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages blackbox-themes depends on: ii blackbox 0.70.0-2 Window manager for X -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
