Bug#883731: audacious: Debian packaging has incorrect license

2017-12-12 Thread John Lindgren
Hi Nicholas et. al,

(tallica: This is re: Debian bug #883731, related to the GPL -> BSD
relicensing of Audacious a few years back.  Please take a look at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883731 for background
if you're interested, otherwise disregard.)

On 12/12/2017 04:39 PM, Nicholas D Steeves wrote:
> For Debian Legal Team: With respect to the translations, I now suspect
> they can probably be transitioned to BSD without issue, because
> copyright is also assigned to the Audacious Translators.  eg, in the
> last GPL-2+ release 3.2.4:
> Copyright (C) Audacious translators

We needed a single copyright line because of the way Transifex is set
up, but it's not meant to indicate copyright assignment.  "Audacious
translators" is not a legal entity and just refers to the individual
translators listed in each .po file, who are the copyright holders.

> John, I removed the offending patch in git for the user-visible
> license provided by the Audacious GUI.  Then I went ahead and did a
> historical relicensing review, in spite of the potential for other
> missing copyright holders due to the Transifex switch.  I am a bit
> concerned about what looks to be a politic of "silence is consent" wrt
> relicensing, and hope that I am wrong, or that I was sloppy in my
> review.  Was the discussing conducted informally off the record?

We took a bit more care with the source code relicensing than with the
translations.  I personally went through Git commit logs and replaced
copyrights of "XMMS team", "BMP team", or "Audacious team" (again, none
of which were legal entities) and replaced them with the names of the
actual contributors.

In many cases, files still credited to "the XMMS team" or "the BMP team"
had been totally rewritten and none of the original code that was under
the XMMS/BMP copyright remained.  Actually, as of today, no original
XMMS code remains in Audacious core (i.e. the "audacious" package) at
all.  The largest body of remaining XMMS code is in the "skins" plugin,
which is still GPL for that very reason.

For the core of Audacious, the remaining copyright holders all gave
consent to relicense their code as BSD, generally by email or via the
IRC channel we had back then.  I don't have any of the emails or IRC
logs saved (sorry) but the date of each of the separate Git commits you
listed reflects the point at which we received permission from the
copyright holders listed in those files.

> Would you please take a look at the following (Ian's reply) for an
> example of how to provide a record of all copyright holder's consent?
> tldr; documented confirmation (eg: via copies of emails or a download
> of a bug report/issue/forum thread) for all contributors who did not
> assign copyright to the Audacious Team in the headers of the files
> they contributed to.

Unfortunately, such documentation doesn't exist, to my knowledge.  I'll
point out any specific information I recall about the commits you mentioned.

> 42cbe57307962e65acc2db24dbe99249453c6aac
The equalizer code was a port from mplayer.  The author, Anders
Johansson, was contacted and gave consent for the relicense, and
incidentally also asked that we retain some of his coding style (see the
previous commit to equalizer.c).

> b308c892f47a55c63ef2675f9b6cf016be037f4c
The session management code was later removed from Audacious, which is
why Ivan and David aren't listed in AUTHORS any longer.

> 31ea4ad1adb84f37ce8fff5b4868df247bd6d913
Michal Lipski (tallica, CC'd) did the footwork in tracking down the
authors of those files, and "where possible" in the commit message
refers to developers who gave consent.  Most of the developers listed in
those files were still around on IRC at the time.

> df1165d2fdd8470b2fd45d2e87cac5373055b55e
"desowin ok'd it" -- desowin is the Tomasz Moń listed in those files.
The rest of us were present on IRC, I think.

> 9a979a5af95eb663435ef99d3b7b5c79b94855be
Jussi Judin was not a core developer at the time; I assume tallica
contacted him.

> 33b58d4d8ba18fcbcc36af5c650414e173e22396
>   * Do you have consent on file to move to BSD license for all
> contributors to XMMS and BMP?

I don't recall the particular IRC discussion referenced in the commit
message, but presumably it was determined that no XMMS/BMP code remained
in those files.

> bc295976816358f9512f99a78e933e6594cce121
The commit message itself lists the copyright holders who gave consent.
Most of those folks were around on IRC and so I would assume that was
how they were contacted.

> 853f96f54bbca608f0c95b5e8bf3fd2146607bdd
Similar, except that (from what I remember) Paula developed that code
under Tony Vroon (Chainsaw)'s mentorship, and he would have vouched for
her consent.

> 3d2ca792a02973fb5e2f33d6273aac825d4f3a55
Here I was reattributing some files to their actual authors based on Git
logs, as I said earlier.  You can see that in this commit, I left the
GPL notice intact on any files whose authors hadn't given consent yet at
that 

Bug#883731: audacious: Debian packaging has incorrect license

2017-12-10 Thread John Lindgren
On 12/10/2017 06:12 PM, Nicholas D Steeves wrote:
> In particular I'm concerned about lines like this from
> d/copyright:
> 
> "po/uk.po" is © 2005 Mykola Lynnyk and is distributed under the terms of the
>  GPL.
> 
> Where the new po/uk.po is GPL-incompatible 2-clause BSD:

The line "Copyright (C) 2005 Mykola Lynnyk <...>" appears to have been
lost accidentally in commit 1a013156d209b, when we switched over to
Transifex.  I'll see about restoring it.

As far as our Git history goes back (to October 2005), uk.po had no
license declaration and was assumed to be under the same license as the
source files it translated (which at the time was GPLv2+). At the time
of the BSD relicense, we took the liberty of assuming that such
translations would automatically switch to the new license along with
the source files they translated.  No one (to my knowledge) has
contacted us in the five years since to clarify that their translations
were intended to be forever GPL-only, but I suppose that to take a more
cautious approach, Debian could still distribute the package as GPL in
total.

> Oh, and if
> everything goes according to plan we'll have a qt variant again
> sometime in 2018 (one src:package will build the gtk variant, cleanup,
> build the qt variant, and then package the two variants separately).

+1 from me!

John



Bug#883731: audacious: Debian packaging has incorrect license

2017-12-08 Thread John Lindgren
Nicholas D Steeves wrote:

> Both BSD 3-clause and BSD 2-clause allow relicensing as GPL, thus so
> long as the licensing terms are complied with correctly BSD code can
> perpetually and unidirectionally flow to GPL projects.

Yes, I agree.  It's perfectly okay for the Debian package(s) to be
distributed as GPL, *as long as* the original BSD license text is still
retained.

> I'm also unsure whether the patch
> that changes the user-visible bits and the out-of-date
> debian/copyright outweigh the 2-clause license that wasn't stripped
> from the headers of various files.

Speaking for myself as upstream project lead, I'm not worried about
the legal status of already-built packages, but I would prefer that the
upstream (BSD 2-clause) license remain user-visible in future Debian
builds.  The simplest way to achieve this would be to remove
use-system-licenses.patch and let the GUI again display
/usr/share/audacious/COPYING as the upstream version does.

Alternatively, debian/copyright could be updated to include the full
text of the upstream license, plus any Debian-specific bits (packaging
copyrights, etc.), and the patch could be updated so that the GUI
displays the installed version of that file instead (I think that would
be /usr/share/doc/audacious/copyright?)

Francesco Poli wrote:

> The Audacious upstream developers may be willing to help, by clarifying
> any doubts upon request.

Yes, for sure.

> If that is deemed to be needed or useful, it could be feasible to also
> fix the debian/copyright file for audacious version 3.7.2 in a Debian
> stable update (and possibly also address the same issue for
> oldstable)... On the other hand, this extra effort could perhaps be
> considered not worth doing.

For my part, I'm not worried about the stable+oldstable packages being
fixed, only that the problem is resolved in a new unstable upload going
forward.  I think that the other upstream developers would agree.

Thank you both for the prompt reply and good discussion!

John



Bug#883731: audacious: Debian packaging has incorrect license

2017-12-07 Thread John Lindgren
Hi Nicholas,

> On this topic, would you please update contrib/audacious.appdata.xml
> to reflect the current Audacious license (GPL3)? It claims the
> project_license is BSD-2-Clause.

Sorry if my initial email was unclear.  The current Audacious license *is*
BSD 2-clause, with some exceptions:

1. The embedded copy of libguess (which is an external project) is under
   a BSD 3-clause license, with a separate copyright.  I believe this is
   not a problem so long as the libguess license is also included with
   any distribution.
2. Some of the more ancient plugins are under different licenses, including
   GPLv2+ and GPLv3.  When we relicensed the main parts of Audacious to BSD
   around 2012, we thought it impractical to contact all of the original
   plugin authors since some of them go back to XMMS days (20 years ago now).
   The plugins are compiled as separate binaries, and Debian has them in a
   separate package (audacious-plugins).

Our upstream COPYING file makes note of these exceptions, which is one
reason why it's important for it to be included verbatim, and not replaced
with generic BSD 2-clause text as it is in the current Debian package.

Regarding the plugins, I don't know the state of debian/copyright in the
audacious-plugins package, but my main concern here is that the one in
audacious is correct.

> However, shouldn't it say the following if Audacious' project license
> is GPL-3+ (drop the "any later version" clause for GPL-3 only) ?:

No, see above.

> Also, I found BSD-2-clause here: src/libaudcore/hook.cc,
> src/libaudcore/hook.h, src/libaudcore/output.cc, et al.

Those are correct.

> Conversely, what I found in debian/copyright was a project license of
> GPL-3, with notable exceptions. eg: are really translations GPL-1+?

As I said, debian/copyright is out-of-date.  We relicensed the project
from GPLv3 to BSD 2-clause back in 2012.  Possibly we didn't make an
obvious enough announcement back then for Debian to take notice.

Translations are under the same license as the rest of Audacious.

> To my eyes it looks like the upstream project license needs to be
> clarified and disambiguated, debian/copyright needs work, and finally
> that deduplication patch can be dropped.

Let me know if you think there are still clarifications needed upstream
given the information I've provided here.  I'd be happy to adjust things
as necessary.

Thank you,
John



Bug#883731: audacious: Debian packaging has incorrect license

2017-12-06 Thread John Lindgren
Package: audacious
Version: 3.9-2
Severity: serious

Per Debian policy 2.3:

"Every package must be accompanied by a verbatim copy of its copyright
information and distribution license in the file 
/usr/share/doc/package/copyright
(see Copyright information for further details)."

The file /usr/share/doc/audacious/copyright shipped in the Debian package
is out of date and does not match the current Audacious license (GPL3 vs.
BSD 2-clause).

Worse, the Debian package patches out[1] the upstream license file which
is normally installed under /usr/share/audacious/COPYING and visible in
the "About" window when running Audacious.

You are currently distributing Audacious in violation both of our license
and of Debian's own policy.  Please include the original upstream license,
verbatim, in the Debian package, or stop distributing Audacious.

Thank you,

John Lindgren
Audacious maintainer

[1] 
https://sources.debian.org/patches/audacious/3.9-2/use-system-licenses.patch/



Bug#759241: Build failures against Audacious D-Bus interface

2014-08-25 Thread John Lindgren

Hi,

These packages need to build-depend on the new libaudclient-dev package 
since the libaudclient headers are no longer included in audacious-dev.


See:
https://ftp-master.debian.org/new/libaudclient_3.5~rc2-1.html

--John


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



Bug#618295: audacious: major skipping on VIA 8235 and ALSA

2011-03-18 Thread John Lindgren
severity 618295 important
thanks

Hi Jonathan,

I am sorry to hear you are having trouble with audio output.  I am the
author of the ALSA plugin and would like to see it just work on every
system out there.  Unfortunately I have no experience with this
particular sound card.  One thing I would suggest is to try a newer
version such as 2.4.4, which fixes problems with some cards.

http://www.debian.org/Bugs/Developer#severities
important
a bug which has a major effect on the usability of a package,
without rendering it completely unusable to everyone.

-- John Lindgren



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



Bug#613953: libspectre1: Uninstallable (depends on unavailable package libgs8)

2011-02-18 Thread John Lindgren
Package: libspectre1
Version: 0.2.6-1
Justification: renders package unusable
Severity: grave


As the title says.  libgs8 is not present in sid (at least for amd64 and
i386); thus, libspectre1 cannot be installed.  (I wouldn't care except
that Evince depends on libspectre1.)

-- John

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

Kernel: Linux 2.6.37-1-amd64 (SMP w/2 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 libspectre1 depends on:
ii  libc6 2.11.2-11  Embedded GNU C Library: Shared lib
pn  libgs8none (no description available)

libspectre1 recommends no packages.

Versions of packages libspectre1 suggests:
pn  libspectre1-dbg   none (no description available)




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



Bug#613956: libxine1-ffmpeg: Uninstallable (depends on unavailable package libavutil49)

2011-02-18 Thread John Lindgren
Package: libxine1-ffmpeg
Version: 1.1.19-2
Justification: renders package unusable
Severity: grave


As the title says.  libavcodec49 is not present in sid; thus,
libxine1-ffmpeg cannot be installed.

-- John

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

Kernel: Linux 2.6.37-1-amd64 (SMP w/2 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 libxine1-ffmpeg depends on:
ii  libavcodec52 5:0.6.1+svn20101128-0.2 library to encode decode multimedi
pn  libavutil49 | li none  (no description available)
ii  libc62.11.2-11   Embedded GNU C Library: Shared lib
ii  libfaad2 2.7-6   freeware Advanced Audio Decoder - 
ii  libmad0  0.15.1b-5   MPEG audio decoder library
ii  libpostproc515:0.6.1+svn20101128-0.2 postproc shared libraries
ii  libxine1-bin 1.1.19-2the xine video/media player librar
ii  zlib1g   1:1.2.3.4.dfsg-3compression library - runtime

libxine1-ffmpeg recommends no packages.

libxine1-ffmpeg suggests no packages.




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



Bug#602399: gxine: Fails to start: Aborted

2010-11-04 Thread John Lindgren
Package: gxine
Version: 0.5.905-4
Justification: renders package unusable
Severity: grave

I recently installed gxine and it completely fails to run.  Running
gxine after erasing (~/.config/gxine) brings up a video window, a
controls window, an icon in the system tray, and a configuration
wizard.  The following output is printed:

gtkvideo: failed to get a proxy for gnome-screensaver
params.c:OpenConfFile() - Unable to open configuration file 
/home/john/.smb/smb.conf:
No such file or directory
params.c:OpenConfFile() - Unable to open configuration file 
/etc/samba/smb.conf:
No such file or directory
warning: configuration item media.audio_cd.cddb_cachedir points to a 
non-existent location /home/john/.xine/cddbcache
warning: configuration item media.capture.save_dir points to a non-existent 
location 
warning: configuration item media.dvb.channels_conf points to a non-existent 
location /home/john/.xine/channels.conf
warning: configuration item media.dvd.raw_device points to a non-existent 
location /dev/rdvd
warning: configuration item media.vcd.device points to a non-existent location 
warning: configuration item media.video4linux.radio_device points to a 
non-existent location /dev/radio0
warning: configuration item decoder.external.real_codecs_path points to a 
non-existent location 
warning: configuration item subtitles.separate.font_freetype points to a 
non-existent location 
lirc: cannot initialise - disabling remote control
lirc: maybe lircd isn't running or you can't connect to the socket?

I click forward on the configuration window; it goes to a page saying
that all checks have passed.  The following output is printed:

  sysname: Linux
  release: 2.6.32-5-amd64
  machine: x86_64
X-Video Extension version 2.2
video_out_xv: Xv image format: 0x32315659 (YV12) planar
video_out_xv: this adaptor supports the yv12 format.
video_out_xv: this adaptor supports the yuy2 format.
video_out_xv: Xv image format: 0x30323449 (I420) planar
video_out_xv: Xv image format: 0x32595559 (YUY2) packed
video_out_xv: Xv image format: 0x59565955 (UYVY) packed

I click forward again and get to a page saying setup completed.  I
click close.  gxine dies, and the following output is printed:

Aborted

-- John

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

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 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 gxine depends on:
ii  libc6  2.11.2-6+squeeze1 Embedded GNU C Library: Shared lib
ii  libdbus-glib-1-2   0.88-2simple interprocess messaging syst
ii  libglib2.0-0   2.24.2-1  The GLib library of C routines
ii  libgtk2.0-02.20.1-2  The GTK+ graphical user interface 
ii  libgudev-1.0-0 163-2 GObject-based wrapper library for 
ii  liblircclient0 0.8.3-5   infra-red remote control support -
ii  libmozjs2d 1.9.1.15-1The Mozilla SpiderMonkey JavaScrip
ii  libpango1.0-0  1.28.3-1  Layout and rendering of internatio
ii  librsvg2-common2.26.3-1  SAX-based renderer library for SVG
ii  libx11-6   2:1.3.3-3 X11 client-side library
ii  libxcb11.6-1 X C Binding
ii  libxext6   2:1.1.2-1 X11 miscellaneous extension librar
ii  libxine1   1.1.19-2  the xine video/media player librar
ii  libxine1-x 1.1.19-2  X desktop video output plugins for
ii  libxinerama1   2:1.1-3   X11 Xinerama extension library

Versions of packages gxine recommends:
ii  libxine1-ffmpeg   1.1.19-2   MPEG-related plugins for libxine1

Versions of packages gxine suggests:
pn  gxineplugin   none (no description available)
ii  libdvdcss2 [libdvdcss]1.2.10-0.3 Simple foundation for reading DVDs
ii  libgnomevfs2-01:2.24.3-1 GNOME Virtual File System (runtime
pn  realplayernone (no description available)

-- no debconf information




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



Bug#602399: gxine: Fails to start: Aborted

2010-11-04 Thread John Lindgren
Installing libxine1-gnome allows gxine to start.

-- John

On 11/04/2010 11:05 AM, Darren Salt wrote:
 This looks like bug 597289, which I've just closed. To confirm this, install
 libxine1-gnome; if it is the same problem, this will 'fix' it



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



Bug#577283: audacious: error on upgrade 2.1 - 2.3 (file conflict)

2010-05-07 Thread John Lindgren
Benjamin Drung wrote:
 audacious-plugins has to Break  Replace audacious ( 2.3), which I
 already committed to the git repository.

2.3 has been in experimental for over a month now, and there haven't
been any show-stopping problems other than this upgrade conflict.  Can
you build a package with your fix for the conflict and upload it to
unstable?

Thanks,
John Lindgren




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



Bug#577283: audacious: error on upgrade 2.1 - 2.3 (file conflict)

2010-04-12 Thread John Lindgren
notfound 577283 2.1-1+b1
found 577283 2.3-1
thanks

2.3 plugins cannot be used with a 2.1 core, and depend on audacious =
2.3 for this very reason.

Chris, can you take a look at this?

Peace,
John Lindgren


Willi Mann wrote:
 When installing audacious from experimental, I get the following error 
 message 
 (Sorry for the German messages):
 
 
 Entpacke Ersatz für audacious-plugins ...
 Ersetze die Dateien im alten Paket audacious-plugins-extra ...
 dpkg: Fehler beim Bearbeiten von 
 /var/cache/apt/archives/audacious-plugins_2.3-1_i386.deb (--unpack):
  Versuche, »/usr/share/audacious/Skins/Classic/shufrep.png« zu überschreiben, 
 welches auch in Paket audacious 0:2.1-1+b1 ist
 dpkg-deb: Unterprozess paste mit Signal (Datenübergabe unterbrochen (broken 
 pipe)) getötet
 Verarbeite Trigger für man-db ...
 Fehler traten auf beim Bearbeiten von:
  /var/cache/apt/archives/audacious-plugins_2.3-1_i386.deb
 E: Sub-process /usr/bin/dpkg returned an error code (1)Tags: experimental
 
 So /usr/share/audacious/Skins/Classic/shufrep.png moved to audacious to 
 audacious-plugins. I guess a Replaces: audacious ( 2.3-1) is missing.




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



Bug#555946: audacious: segmentation fault

2009-11-12 Thread John Lindgren
severity 555946 important
thanks

Brian,

I can't reproduce this with either version of libcdio-cdda0 you
mentioned.  Because this bug does not affect everyone, I am lowering the
severity to important.  Please install audacious-dbg and
audacious-plugins-dbg and provide a backtrace.

Also, the configuration for Audacious 2.x has moved from ~/.audacious to
~/.config/audacious.

Peace,
John Lindgren




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



Bug#530862: audacity: random hangups

2009-09-26 Thread John Lindgren
On Sat, 2009-09-26 at 21:53 +0200, Benjamin Drung wrote:
 since a while 1.3.9-3 is in the archive. Can you test, if this version
 still crashes? Please provide a back trace then. If you cannot reproduce
 it any more, I will close this bug.

Since I upgraded from 1.3.7-2 to 1.3.7-3 a month ago, I have not seen
this hangup. I'm installing 1.3.9-3 now; but unless there's been a
regression since 1.3.7-3, I think the bug can be closed.

John Lindgren




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



Bug#547463: nvidia-glx-legacy-96xx: cannot install because of conflicts with current X.org and Linux kernel

2009-09-19 Thread John Lindgren
Package: nvidia-glx-legacy-96xx
Version: 96.43.07-2
Justification: renders package unusable
Severity: grave

This about says it all:

xserver-xorg-core conflicts with xserver-xorg-video-2 [provided by 
nvidia-glx-legacy-96xx 96.43.07-2]
--\ The following actions will resolve this dependency:
  - Remove xserver-xorg-core [2:1.6.3-1+b1 (testing, now)] 
 
  - Cancel the installation of nvidia-glx-legacy-96xx

nvidia-kernel-legacy-96xx-2.6.26-2-686 depends upon 
linux-image-2.6.26-2-686
--\ The following actions will resolve this dependency:
  - Cancel the installation of nvidia-kernel-legacy-96xx-2.6.26-2-686  
  

The system in question is a Dell Latitude C840 with an NVidia GeForce4
440 Go. It was lately updated from Lenny to Squeeze, and now it is
impossible to use the accelerated NVidia drivers (nv works, but much
more slowly).

Setting severity to grave because the package cannot be installed,
period.

Regards,
John Lindgren


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-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/dash




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



Bug#530862: audacity: random hangups

2009-08-26 Thread John Lindgren
On Wed, 2009-08-26 at 01:48 +0200, Benjamin Drung wrote:
 on my system audacity 1.3.7 crashed from time to time on editing (not
 recording). Due to their recovery mode I had no data loss.
 
 Can you please test 1.3.8-1 from experimental and report if your
 problems are gone. On my system 1.3.8 is more stable than 1.3.7.

1.3.7-3 was pulled in when I ran an update today, and I've been running
it for around half an hour without a crash. Since 1.3.7-2 usually
crashed within five or ten minutes, it appears to me that the problem is
fixed in 1.3.7-3. I'll try to do more testing -- I don't actually use
Audacity that often -- and if I do see a crash, I'll compile the version
from experimental and try that instead.

John Lindgren




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



Bug#540380: grub-pc: cannot dual boot into Windows XP after upgrade.

2009-08-07 Thread John Lindgren
Package: grub-pc
Version: 1.96+20090725-1
Justification: renders package unusable
Severity: grave

In the upgrade from grub-legacy to grub-pc, my menu.lst entries to dual
boot Windows XP were lost. I would normally be fine with migrating them
manually, except that (1) there was no warning from debconf that they
would be lost and (2) I cannot find any instructions on how to migrate
them. Neither man grub nor man grub-pc brings up anything at all.

In my experience, dual booting Windows and Linux is more common than
booting Linux alone; thus, this problem renders grub-pc unusable to most
users.

Attached is my menu.lst from before the upgrade.

John Lindgren


-- Package-specific info:

*** BEGIN /proc/mounts
/dev/disk/by-uuid/70090295-6e7c-4b6a-8ee2-d27e6d0504fc / ext3 
rw,errors=continue,barrier=1,data=ordered 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/device.map
(hd0)   /dev/hda
*** END /boot/grub/device.map

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
set default=0
set timeout=5
set root=(hd0,3)
search --no-floppy --fs-uuid --set 70090295-6e7c-4b6a-8ee2-d27e6d0504fc
if loadfont /usr/share/grub/ascii.pf2 ; then
  set gfxmode=640x480
  insmod gfxterm
  insmod vbe
  if terminal_output.gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry Debian GNU/Linux, Linux 2.6.26-2-686 {
set root=(hd0,3)
search --no-floppy --fs-uuid --set 70090295-6e7c-4b6a-8ee2-d27e6d0504fc
linux   /boot/vmlinuz-2.6.26-2-686 
root=UUID=70090295-6e7c-4b6a-8ee2-d27e6d0504fc ro  quiet
initrd  /boot/initrd.img-2.6.26-2-686
}
menuentry Debian GNU/Linux, Linux 2.6.26-2-686 (recovery mode) {
set root=(hd0,3)
search --no-floppy --fs-uuid --set 70090295-6e7c-4b6a-8ee2-d27e6d0504fc
linux   /boot/vmlinuz-2.6.26-2-686 
root=UUID=70090295-6e7c-4b6a-8ee2-d27e6d0504fc ro single 
initrd  /boot/initrd.img-2.6.26-2-686
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file is an example on how to add custom entries
### END /etc/grub.d/40_custom ###
*** END /boot/grub/grub.cfg

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-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/dash

Versions of packages grub-pc depends on:
ii  debconf [debconf-2.0]1.5.27  Debian configuration management sy
ii  grub-common  1.96+20090725-1 GRand Unified Bootloader, version 
ii  libc62.9-12  GNU C Library: Shared libraries
ii  ucf  3.0018  Update Configuration File: preserv

grub-pc recommends no packages.

Versions of packages grub-pc suggests:
pn  desktop-base  none (no description available)
ii  genisoimage   9:1.1.9-1  Creates ISO-9660 CD-ROM filesystem
pn  os-prober none (no description available)

-- debconf information:
* grub-pc/linux_cmdline:
* grub-pc/chainload_from_menu.lst: true
  grub-pc/install_devices:

# menu.lst - See: grub(8), info grub, update-grub(8)
#grub-install(8), grub-floppy(8),
#grub-md5-crypt, /usr/share/doc/grub
#and /usr/share/doc/grub-legacy-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not change this entry to 'saved' or your
# array will desync and will not let you boot your system.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 3

# Pretty colours
color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line)  and entries protected by the
# command 'lock'
# e.g. password topsecret
#  password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

Bug#530862: Bug #530862 is severity grave

2009-08-02 Thread John Lindgren
On Sun, 2009-08-02 at 12:51 -0400, John Lindgren wrote:
 severity 530862 grave
 thanks
 
 http://www.debian.org/Bugs/Developer#severities
 
 grave
 makes the package in question unusable or mostly so, or
 causes data loss, or introduces a security hole allowing
 access to the accounts of users who use the package.
 
 These hangups happen often enough to make Audacity essentially unusable.

They cause data loss, too, when I have an unsaved file open.

John Lindgren




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