Re: I *love* goodbye-microsoft.com

[paddy]

On Thu, Feb 22, 2007 at 12:15:02PM -0800, Tyler MacDonald wrote:
> ... so I thought I'd take the liberty of registering "goodbye-apple.com" and
> "goodbye-osx.com" in order to protect the namespace. I'll gladly transfer
> them over to the first DD to code up something similar for that platform(s).
> :-)
> 

perhaps you should consider goodbye-fedora.org too ;-)

Regards,
Paddy


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Work-needing packages report for Feb 23, 2007

[Sam Hocevar]

On Fri, Feb 23, 2007, [EMAIL PROTECTED] wrote:
> The following packages have been orphaned:
> 
>s48-refman (#411423), orphaned 4 days ago
>  Description: An unofficial reference manual for Scheme48
>  Installations reported by Popcon: 18
> 
>scheme48 (#411425), orphaned 4 days ago
>  Description: A simple, modular, and lightweight Scheme
>implementation
>  Reverse Depends: cmuscheme48-el
>  Installations reported by Popcon: 64

   Anyone interested in a pkg-scheme team / alioth project? I'd hate
to see scheme48 disappear, but I have too many packages to adopt these
ones. My elk package is bugless but could use some love from such a
team, too.

Regards,
-- 
Sam.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

xs-vcs-browser and friends

[Stefano Zacchiroli]

Hi all,
  a couple of days ago Filippo Giunchedi (thanks a lot!) applied my
patch which adds support for the XS-Vcs-Browser field in the web
interface of the PTS.  Now you can happily use in your debian/control
both XS-Vcs-Browser (pointing to a web browsable interface of the
repository of a given version control system) and its XS-Vcs-* friends
(pointing to a vcs-specific access of the same repository).

For more info see the (last version of) the patch I submitted for the
Developer's Reference documenting the usage of the fields [1].

Cheers.

[1] 
http://bugs.debian.org/cgi-bin/bugreport.cgi/developers_reference-vcs_field.patch?bug=391023;msg=75;att=1

-- 
Stefano Zacchiroli -*- Computer Science PhD student @ Uny Bologna, Italy
[EMAIL PROTECTED],debian.org,bononia.it} -%- http://www.bononia.it/zack/
(15:56:48)  Zack: e la demo dema ?/\All one has to do is hit the
(15:57:15)  Bac: no, la demo scema\/right keys at the right time


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Looking for a temporary account on Alpha

[Frank B. Brokken]

Dear list members,

Falk Hueffner filed a bug (Bug#412003) against the 2.10 release of the Yodl
package. He detected that the latest version did not run correctly on the
Alpha (see, e.g.,
http://buildd.debian.org/fetch.cgi?pkg=yodl&arch=alpha&ver=2.10-1&stamp=1171904919)

The problem I'm now confronted with is that as far as I know nobody in my
environment uses the Alpha running Debian Linux. So I wonder if there is a
list member who *does* operate an Alpha and is willing and able to offer me a 
(temporary) account so I can research the problem's cause.

Thanks in advance for any help offered,

Cheers,

[cc: Falk]

-- 
Frank B. Brokken
Computing Center, University of Groningen
(+31) 50 363 9281
Public PGP key: http://pgp.surfnet.nl:11371/
Key Fingerprint: 8E36 9FC4 1DAA FCDF 1A0D  B19F DAC4 BE50 38C6 6170


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

[EMAIL PROTECTED]

[Turbo Fredriksson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

What's the code that do this? Is it packaged? If not, can
I have it? :)

I've been thinking how to do something like this myself
for some time, but I did some signing today and accidently
stumbled across http://db.debian.org/password.html so...


PS. Please keep the Cc. Debian-devel is high volume, and I
rarely have time to read it...
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 

iD8DBQFF3swRmlWzPKccHgARApXnAJ9QjEEZn3br9IQp89yOIV0kVhg/fgCcCFp1
+TGvzbqRt9nn9SgTFta+h+g=
=pith
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: [EMAIL PROTECTED]

[Raphael Hertzog]

Hello,

On Fri, 23 Feb 2007, Turbo Fredriksson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> What's the code that do this? Is it packaged? If not, can
> I have it? :)
> 
> I've been thinking how to do something like this myself
> for some time, but I did some signing today and accidently
> stumbled across http://db.debian.org/password.html so...

Check ud-mailgate in http://cvs.debian.org/userdir-ldap/?root=debian-admin

(The userdir-ldap package is on the APT repository on
http://db.debian.org/debian-admin/ but that's mainly for direct use by DSA
and not for public use)

Cheers,
-- 
Raphaël Hertzog

Premier livre français sur Debian GNU/Linux :
http://www.ouaza.com/livre/admin-debian/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Where did Bacula 1.38.11-7+b1 come from?

[Matthias Julius]

John Goerzen <[EMAIL PROTECTED]> writes:

> On Fri, Feb 23, 2007 at 12:13:07AM +0100, Wouter Verhelst wrote:
>> > binNMUs though.  Aren't buildds simply there to build the existing
>> > sources on other platforms?  Surely some human was involved here?
>> 
>> wanna-build and buildd have been modified a while back to be able to do
>> binNMU's. The only human involvement is when a given package is marked
>> in the database as 'requires a binNMU', and when the buildd admin later
>> signs the package, as usual.
>
> Would it be possible to record the name of the human that marked the
> package in debian/changelog?  That would be a big help, I think (and
> hopefully avoid a discussion on debian-devel next time it happens)

Since this is about a binNMU where the source package is not touched
and the changelog lives inside the source package how is that supposed
to be possible?

Adding to the changelog requires a new upload.

Matthias


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Where did Bacula 1.38.11-7+b1 come from?

[Wouter Verhelst]

On Fri, Feb 23, 2007 at 08:36:26AM -0500, Matthias Julius wrote:
> John Goerzen <[EMAIL PROTECTED]> writes:
> 
> > On Fri, Feb 23, 2007 at 12:13:07AM +0100, Wouter Verhelst wrote:
> >> > binNMUs though.  Aren't buildds simply there to build the existing
> >> > sources on other platforms?  Surely some human was involved here?
> >> 
> >> wanna-build and buildd have been modified a while back to be able to do
> >> binNMU's. The only human involvement is when a given package is marked
> >> in the database as 'requires a binNMU', and when the buildd admin later
> >> signs the package, as usual.
> >
> > Would it be possible to record the name of the human that marked the
> > package in debian/changelog?  That would be a big help, I think (and
> > hopefully avoid a discussion on debian-devel next time it happens)
> 
> Since this is about a binNMU where the source package is not touched
> and the changelog lives inside the source package how is that supposed
> to be possible?
> 
> Adding to the changelog requires a new upload.

No, that's not true. Since the version of a Debian package is distilled
from the changelog, the only way to change it is by changing the
changelog. This is also one of the reasons why buildd needs support for
binNMU's: because you need to do some weird stuff with the source before
actually building.

Since you're doing a build anyway, and since that changelog entry ends
up in the .changes file, it would sound reasonable to request that the
human who does the upload is mentioned in the changelog. This is already
possible (requesting a build requires that you also specify a changelog
entry), but the tools do not enforce entering a name; and it's also
impossible to automatically add a name upon request, since
ftp-master.d.o does not necessarily have a user account for the person
doing the request.

-- 
 Home is where you have to wash the dishes.
  -- #debian-devel, Freenode, 2004-09-22


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Votre complémentaire santé à partir de 12,94 EUR/mois !

[ECA ASSURANCES]

Pour visualiser la version en ligne cliquez ici 
http://tr1.bp12.net/r5.aspx?GV1=ASP104Z0026O0002U4U4B00094ITV



http://tr1.bp12.net/r5.aspx?GV1=ASP104Z0026O0002U4U3U00094ITV 


http://tr1.bp12.net/r5.aspx?GV1=ASP104Z0026O0002U4U3V00094ITV 

http://tr1.bp12.net/r5.aspx?GV1=ASP104Z0026O0002U4U3W00094ITV 


http://tr1.bp12.net/r5.aspx?GV1=ASP104Z0026O0002U4U3X00094ITV 


http://tr1.bp12.net/r5.aspx?GV1=ASP104Z0026O0002U4U3Y00094ITV 


http://tr1.bp12.net/r5.aspx?GV1=ASP104Z0026O0002U4U3Z00094ITV 


http://tr1.bp12.net/r5.aspx?GV1=ASP104Z0026O0002U4U494ITV 


http://tr1.bp12.net/r5.aspx?GV1=ASP104Z0026O0002U4U4100094ITV 

http://tr1.bp12.net/r5.aspx?GV1=ASP104Z0026O0002U4U4200094ITV 


http://tr1.bp12.net/r5.aspx?GV1=ASP104Z0026O0002U4U4300094ITV 


http://tr1.bp12.net/r5.aspx?GV1=ASP104Z0026O0002U4U4400094ITV 


http://tr1.bp12.net/r5.aspx?GV1=ASP104Z0026O0002U4U4500094ITV 


http://tr1.bp12.net/r5.aspx?GV1=ASP104Z0026O0002U4U4600094ITV 


http://tr1.bp12.net/r5.aspx?GV1=ASP104Z0026O0002U4U4700094ITV 

http://tr1.bp12.net/r5.aspx?GV1=ASP104Z0026O0002U4U4800094ITV 

http://tr1.bp12.net/r5.aspx?GV1=ASP104Z0026O0002U4U4900094ITV 

En vertu 
  de la loi n°78-17 du 6 janvier 1978, vous disposez d'un droit d'accès 
  et de rectification des données vous concernant ainsi qu'un droit 
d'opposition 
  que vous pouvez faire valoir à tout moment. Pour cela Si 
  vous ne souhaitez plus recevoir de mails de notre part veuillez : 
http://tr1.bp12.net/r5.aspx?GV1=ASP104Z0026O0002U4U4A00094ITV&fguidv5=000190
 
Cliquez 
  ici

Re: bugs.d.o down (was: wiki.debian.org disk problems resolved)

[Ryan Murray]

On Thu, 22 Feb 2007 17:37:03 +0100
Sam Hocevar <[EMAIL PROTECTED]> wrote:

> On Wed, Feb 14, 2007, Ryan Murray wrote:
> > wiki.debian.org has been moved to a new host with lots of available
> > disk space, so updates should be fine now.  For the first 90 minutes
> > after the move exim wasn't running, so updates during this period
> > would have failed to send notifications.
> > 
> > If any problems are found with the move, please contact debian-admin
> > with details.
> 
>Hi! There must have been a problem with the move because bugs.d.o and
> wiki.d.o have been down the whole day while no maintenance was planned
> (or there's a problem with -devel-anounce, too, I don't know).

Yes, there was a problem, and it resulted in rietz being down until the
local admins were around.  This ended up being ~8 hours later; I did
not have an ETA at the time, so didn't have any details to make a post
to -devel-announce.

I now have direct access to rietz's iLO, and am working with the bugs
team to always have bugs-mirror.debian.org's web interface available,
should something ever happen to the main server in future.


signature.asc
Description: PGP signature

status/destiny of imagemagick

[Yaroslav Halchenko]

Dear All,

I am in the process of preparing umibozu package, which uses
libmagick++9c2a library. Some crashes of umibozu boiled down to problems
in imagemagick and naturally upstream author recommended to try recent
imagemagick. 

At the moment imagemagick in debian is 7:6.2.4.5.dfsg1-0.14 (with  (103
bugs: 0, 51, 40, 12) bugs). 
Upstream release is ImageMagick-6.3.2-8.tar.gz whenever 6.2.4.6 was
released on 09/17/2005 (ie 1.5 years ago).

imagemagick seems to be not listed among wnpp packages (ie not orphaned,
neither requiring some help) but has a list of 14 NMUs... 

I am wondering if there is some good cause to stay with such outdated
imagemagick or it is simply its implicit orphaned state?

-- 
  .-.
=--   /v\  =
Keep in touch// \\ (yoh@|www.)onerussian.com
Yaroslav Halchenko  /(   )\   ICQ#: 60653192
   Linux User^^-^^[17]



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: status/destiny of imagemagick

[Luciano Bello]

El vie, 23-02-2007 a las 11:45 -0500, Yaroslav Halchenko escribió:
> Dear All,
> 
> I am in the process of preparing umibozu package, which uses
> libmagick++9c2a library. Some crashes of umibozu boiled down to problems
> in imagemagick and naturally upstream author recommended to try recent
> imagemagick. 
> 
> At the moment imagemagick in debian is 7:6.2.4.5.dfsg1-0.14 (with  (103
> bugs: 0, 51, 40, 12) bugs). 
> Upstream release is ImageMagick-6.3.2-8.tar.gz whenever 6.2.4.6 was
> released on 09/17/2005 (ie 1.5 years ago).
> 
> imagemagick seems to be not listed among wnpp packages (ie not orphaned,
> neither requiring some help) but has a list of 14 NMUs... 
> 
> I am wondering if there is some good cause to stay with such outdated
> imagemagick or it is simply its implicit orphaned state?

I adopted imagemagick and I preparing a new version in theses days.

luciano


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: status/destiny of imagemagick

[Yaroslav Halchenko]

> > I am wondering if there is some good cause to stay with such outdated
> > imagemagick or it is simply its implicit orphaned state?
> I adopted imagemagick and I preparing a new version in theses days.

Wonderful! Thank you so much (there seems to be no ITA bug though...;-))

-- 
  .-.
=--   /v\  =
Keep in touch// \\ (yoh@|www.)onerussian.com
Yaroslav Halchenko  /(   )\   ICQ#: 60653192
   Linux User^^-^^[17]



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Where did Bacula 1.38.11-7+b1 come from?

[Florian Weimer]

* Guillem Jover:

> The resulting .changes will get a field like this:
>
>   Source: bacula (1.38.11-7)
>
> which can be used to track back from which source this binary
> originated.

Yeah, but this only helps if you've got a source version to compare
to.  You could derive that from a binary version if you've got the
corresponding Package entry, but this information might not be
available anymore when you need it.

Furthermore, it's not particularly useful to address the
inconsistencies added by binNMUs when there are other problems.  Some
binary packages have different version numbering schemes on different
architectures, or they are built from different source packages.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Where did Bacula 1.38.11-7+b1 come from?

[Andreas Metzler]

Mike Hommey <[EMAIL PROTECTED]> wrote:
> On Thu, Feb 22, 2007 at 07:57:07PM +0100, Andreas Metzler <[EMAIL PROTECTED]> 
> wrote:
>> Mike Hommey <[EMAIL PROTECTED]> wrote:
>>> On Thu, Feb 22, 2007 at 07:31:46PM +0100, Frans Pop <[EMAIL PROTECTED]> 
>>> wrote:
 On Thursday 22 February 2007 19:26, Andreas Metzler wrote:
> 1. Add a Build-dependency on dpkg-dev (>=1.13.19)
> 2. For all in bacula-foo packages that are arch:all replace any
> occurence of
> Depends: bacula-foo (= ${Source-Version})
> with Depends: bacula-foo (= ${source:Version})
> 3. (optional, but clarify things) For all in bacula-foo packages that
> are arch:any replace any occurence of
> Depends: bacula-foo (= ${Binary-Version})

 Something is missing here... I suspect:
 | with Depends: bacula-foo (= ${binary:Version})

>>> That would be 
>>> bacula-foo (>= ${source:Version}), bacula-foo (<< ${source:Version}.1~)

>> I do not get that, what is the benefit compared to (= ${binary:Version})

> arch: all packages are *not* rebuilt, so their dependency won't ever get
> updated, which means the dependency will be stuck to the original
> ${binary:Version}, which is... ${source:Version}.

You are thinking about an arch:all Package with a (= ${Source-Version})
dependency on an arch=any package? Hmm, yes that is a gotcha.

So we'd end up with this instead of a the 3. above:

3. For all in bacula-foo packages that are arch:any replace any occurence of
Depends: bacula-foo (= ${Source-Version}) with either

Depends: bacula-foo (= ${binary:Version})
*if* the depending package itself is arch-any (optional cosmetical
change) or

Depends: bacula-foo (>= ${source:Version}), bacula-foo (<< ${source:Version}.1~
otherwise *if* the depending package itself is arch all.

An example might help:

*Before*
Package: foo
Architecture: all
Depends: foo-binary (= ${Source-Version}), foo-doc (= ${Source-Version})

Package: foo-x
Architecture: any
Depends: foo-binary (= ${Source-Version})

Package: foo-binary
Architecture: any
Depends: foo-data (= ${Source-Version})

Package: foo-data
Architecture: all

Package: foo-doc
Architecture: all

*After*
Build-Depends: dpkg-dev (>=1.13.19)
Package: foo
Architecture: all
Depends: foo-binary  (>= ${source:Version}), foo-binary (<< 
${source:Version}.1~), foo-doc (= ${source:Version})

Package: foo-x
Architecture: any
Depends: foo-binary (= ${binary:Version})

Package: foo-binary
Architecture: any
Depends: foo-data (= ${source:Version})

Package: foo-data
Architecture: all

Package: foo-doc
Architecture: all

cu andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Where did Bacula 1.38.11-7+b1 come from?

[Charles Plessy]

Le Fri, Feb 23, 2007 at 08:36:26AM -0500, Matthias Julius a écrit :
> John Goerzen <[EMAIL PROTECTED]> writes:
> 
> > On Fri, Feb 23, 2007 at 12:13:07AM +0100, Wouter Verhelst wrote:
> >> > binNMUs though.  Aren't buildds simply there to build the existing
> >> > sources on other platforms?  Surely some human was involved here?
> >> 
> >> wanna-build and buildd have been modified a while back to be able to do
> >> binNMU's. The only human involvement is when a given package is marked
> >> in the database as 'requires a binNMU', and when the buildd admin later
> >> signs the package, as usual.
> >
> > Would it be possible to record the name of the human that marked the
> > package in debian/changelog?  That would be a big help, I think (and
> > hopefully avoid a discussion on debian-devel next time it happens)
> 
> Since this is about a binNMU where the source package is not touched
> and the changelog lives inside the source package how is that supposed
> to be possible?
> 
> Adding to the changelog requires a new upload.

Would it be that a bad idea ? There has been a lot of talk explaining
that there is no need to leave written justifications for binNMUs, but I
think that we are stil clueless about the problem it was supposed to
solve in the case of Bacula...

Have a nice day,

-- 
Charles Plessy
Wako, Saitama, Japan


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Where did Bacula 1.38.11-7+b1 come from?

[Marc 'HE' Brockschmidt]

Charles Plessy <[EMAIL PROTECTED]> writes:
> Le Fri, Feb 23, 2007 at 08:36:26AM -0500, Matthias Julius a écrit :
>> John Goerzen <[EMAIL PROTECTED]> writes:
>>> Would it be possible to record the name of the human that marked the
>>> package in debian/changelog?  That would be a big help, I think (and
>>> hopefully avoid a discussion on debian-devel next time it happens) 
>> Since this is about a binNMU where the source package is not touched
>> and the changelog lives inside the source package how is that supposed
>> to be possible?
>> 
>> Adding to the changelog requires a new upload.
> Would it be that a bad idea ? There has been a lot of talk explaining
> that there is no need to leave written justifications for binNMUs, but I
> think that we are stil clueless about the problem it was supposed to
> solve in the case of Bacula...

At least Steve notes the reason for his bin-NMUs on
http://ftp-master.debian.org/~vorlon/transition-binnmus.txt

In the case of bacula, it was indeed done to rebuild against a newer
mysql version.

Marc
-- 
BOFH #445:
Browser's cookie is corrupted -- someone's been nibbling on it.


pgpjNPqFsBqe5.pgp
Description: PGP signature

Bug#412149: general: "usb:" stopped working in both gpsbabel and jpilot

[Reid Priedhorsky]

Package: general
Severity: normal


A few days ago, jpilot stopped syncing my USB PalmPilot. I had been using
libusb (i.e. "usb:" as the port). A reboot and a different cable didn't help,
but un-blacklisting the visor module and changing the port to /dev/pilot --
i.e. using the kernel visor module instead of libusb, reversing the procedure
suggested in #399878 -- and now sycning works fine.

Similarly, gpsbabel, which also uses libusb, no longer speaks to my GPS unit:

  4 [~]$ gpsbabel -r -i garmin -f usb: -o gpx -F /tmp/foo
  usb_set_configuration failed, probably because kernel driver ''
   is blocking our access to the USB device.
  For more information see http://www.gpsbabel.org/os/Linux_Hotplug.html

dmesg output for both the pilot and the GPS are along the lines of:

  ohci_hcd :00:02.0: wakeup
  usb 1-3: new full speed USB device using ohci_hcd and address 11
  usb 1-3: configuration #1 chosen from 1 choice
  usb 1-3: USB disconnect, address 11

Also, the GPS works fine in mass storage mode -- again, no libusb.

The following are the packages I upgraded between working and non-working USB:

2007-02-20 21:36:24 status installed dhcp3-common 3.0.4-13
2007-02-20 21:36:29 status installed dhcp3-server 3.0.4-13
2007-02-20 21:36:29 status installed module-init-tools 3.3-pre4-1
2007-02-20 21:36:38 status installed linux-sound-base 1.0.13-4
2007-02-20 21:36:39 status installed alsa-base 1.0.13-4
2007-02-20 21:36:47 status installed libexpat1 1.95.8-3.4
2007-02-20 21:36:47 status installed libexpat1-dev 1.95.8-3.4
2007-02-20 21:36:47 status installed apache2-utils 2.2.3-3.3
2007-02-20 21:36:47 status installed busybox 1:1.1.3-4
2007-02-20 21:36:47 status installed libklibc 1.4.34-1
2007-02-20 21:36:47 status installed klibc-utils 1.4.34-1
2007-02-20 21:36:47 status installed libgphoto2-port0 2.2.1-16
2007-02-20 21:36:50 status installed libgphoto2-2 2.2.1-16
2007-02-20 21:36:51 status installed libpango1.0-common 1.14.8-5
2007-02-20 21:36:51 status installed libpango1.0-0 1.14.8-5
2007-02-20 21:36:51 status installed libpango1.0-dev 1.14.8-5
2007-02-20 21:36:51 status installed libscrollkeeper0 0.3.14-13
2007-02-20 21:36:52 status installed openoffice.org-common 2.0.4.dfsg.2-5
2007-02-20 21:37:04 status installed ttf-opensymbol 2.0.4.dfsg.2-5
2007-02-20 21:37:04 status installed openoffice.org-core 2.0.4.dfsg.2-5
2007-02-20 21:37:07 status installed python-uno 2.0.4.dfsg.2-5
2007-02-20 21:37:07 status installed openoffice.org-writer 2.0.4.dfsg.2-5
2007-02-20 21:37:07 status installed openoffice.org-draw 2.0.4.dfsg.2-5
2007-02-20 21:37:07 status installed openoffice.org-gtk 2.0.4.dfsg.2-5
2007-02-20 21:37:09 status installed scrollkeeper 0.3.14-13
2007-02-20 21:37:09 status installed ttf-dejavu 2.14-2
2007-02-20 21:37:10 status installed ttf-freefont 20060501cvs-10
2007-02-20 21:37:11 status installed update-inetd 4.27-0.3
2007-02-20 21:37:19 status installed x-ttcidfont-conf 25.1

I'm not sure for which package this bug report is appropriate. libusb seems a
likely candidate, but I haven't upgraded that package since October and
haven't touched the configuration in a while.

Any help would be greatly appreciated. Please let me know what further
information would be useful.

Thanks,

Reid


-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.18-3-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: I *love* goodbye-microsoft.com

[Russell Coker]

On Friday 23 February 2007 19:58, [EMAIL PROTECTED] wrote:
> perhaps you should consider goodbye-fedora.org too ;-)

Converting from Fedora to Debian is not a challenge, merely run debootstrap 
from a root shell.

Also Fedora isn't the enemy.  In fact there's a lot of code sharing between 
Fedora and Debian (more than just shared upstream) and I am not the only 
person to have been both a Fedora and Debian developer at the same time (now 
I am only a DD).

-- 
[EMAIL PROTECTED]
http://etbe.blogspot.com/  My Blog

http://www.coker.com.au/sponsorship.html Sponsoring Free Software development


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]