Package: dh-make-perl
Version: 0.70-1
Severity: normal
Using credentials in your sources.list
(e.g. "http://say:fri...@my.repo.net/debian squeeze main")
breaks the repo_source_to_contents_path method
in Debian::AptContents.
Please consider this patch:
--- /usr/share/perl5/Debian/AptContents.pm
Hi,
# Which deb files built from the patched source did you install? The
-bin only.
# binary package libgtk2.0-bin is not the one that has the problem. Please
Well, yes, now that you mention it.. right.
# make sure to install the patched package libgtk2.0-0 before checking
There's a couple of d
Hi Sandro,
Your email is rude.
I bother reporting bugs.
reportbug has more than a hundred pending bugs. I'm reporting one but
won't dig in deeper for more than a couple of bugs all of which carrying
some related subject, just a matter of time.
I want to use reportbug. But if th
Hi Micha,
Thx for your msg and your work for Debian.
As you suggested I built libgtk2.0-bin and tried again. No fix. Sorry.
Besides, building libgtk was a PITA, all in caps. It was failing all over
the build in docs, tutorials and finally doing the TEST stuff that made
debuild stop (
severity 597913 wishlist
thanks
The problem was actually caused by a not responding libvirtd, which I
discovered too late. Still I think that virt-manager should give some
feedback after a reasonable time, e.g. 30s, if the connection to libvirtd
fails.
--
To UNSUBSCRIBE, email to debian-bugs-d
Hi,
# /lib/udev/modem-modeswitch
# /lib/udev/rules.d/61-option-modem-modeswitch.rules
I didn't investigate further, and here you lost me. Why do these affect this
19d2:2000
device version here? /lib/udev/rules.d/61-option-modem-modeswitch.rules has no
19d2 context here.
And (w/o having fully
Hi,
# I don't entirely get your bugreport… did it work with previous versions of
usb-
# modeswitch-data ?
It once worked. Unsure whether that was with a previous usb-modeswitch-data
version
or even before installing usb-modeswitch-data at all.
# What have you done to make your device work ?
Package: usb-modeswitch-data
Version: 20100221-1
Severity: important
Reporting this here for the draisberghof bb requires registration. It's just a
bad thing to have to get registrated with dozens of boards, wikis, trac or
whatever and keeping track of software. I seek to contribute but not
wast
Hi,
The following link points to the lkml report msg:
http://lkml.org/lkml/2010/2/18/104
Thanks,
Nils
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Salut,
# If the kernel goes down, that's the kernel bug. You should try to catch
# the problem in dmesg or so and open another bug report.
I'll posting in lkml now, too.
Catching dmesg or something hasn't been possible up to now. System hangs.
Any idea how to catch this?
#
Salve,
Sorry, your msg never made it through.
# > As for the trace, it's difficult to provide as udev doesn't regularly crash
but on occasions. I'll try
# Are there any news? Can you still reproduce this?
I think we can close this bug. Udev crashed still once in a while after my last
report.
B
11 matches
Mail list logo