Hi
On Friday 25 July 2014, Julian Andres Klode wrote:
> On Fri, Jul 25, 2014 at 04:29:02AM +0200, Stefan Lippers-Hollmann wrote:
[...]
> > It would be nice if gummiboot would support installing its EFI loader
> > to multiple EFI system partitions in order to gain failsafe suppor
test -a -p" fixes the problem again.
Regards
Stefan Lippers-Hollmann
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16-rc7-aptosid-amd64 (SMP w/8 CPU cores; PREEMPT)
L
pdown integration - which
should be excempt from these problems.
As these advanced aspects of systemd customisations are still rather
new to me, I would suggest to solicit assistance from the systemd
maintainers.
Regards
Stefan Lippers-Hollmann
signature.asc
Description: This is a digitally signed message part.
system paths; in all cases all fstab
devices exist and can be auto-mounted with src:lvm2 2.02.111-2.2. I have
attached the logs for "journalctl -xb" (gzipped) and the fstab.
Regards
Stefan Lippers-Hollmann
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
Hi
On 2015-07-19, Bastian Blank wrote:
> On Thu, Jul 09, 2015 at 05:16:57AM +0200, Stefan Lippers-Hollmann wrote:
> > Upgrading src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting due to
> > a new systemd unit dependency failures regarding lvmetad when mounting
> > non-r
ffective
reference implementation for APs, this is slightly less likely), I
don't think this to be the issue here.
Regards
Stefan Lippers-Hollmann
pgpHs1yTg10Rv.pgp
Description: Digitale Signatur von OpenPGP
rmdir --ignore-fail-on-non-empty /var/lib/mdadm
+ fi
fi
;;
esac
Regards
Stefan Lippers-Hollmann
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.18.0-rc7-aptosid-amd64 (SMP w/8
ys...
This piuparts mass bug filing imho would have better concentrated on
just wheezy to jessie issues, rather than murkying the waters by
including squeeze-->wheezy issues as well, that ship has sailed long
time ago.
Regards
Stefan Lippers-Hollmann
[1] there would be reason to ma
AUFS to overlayfs basically involved a 2-line
change (loading overlay.ko instead of aufs.ko and mounting it with
only slightly different mount options compared to aufs3), I assume the
situation will be equally easy for docker as well.
Therefore I'd suggest to close this bug as wontfix
directory conversion: /usr/share/doc/PACKAGE
Date: Friday 09 January 2015
From: "Stefan Lippers-Hollmann"
To: 774...@bugs.debian.org
Hi
On Thursday 08 January 2015, Andreas Beckmann wrote:
> Package: lirc-x
> Version: 0.9.0~pre1-1.1
> Severity: serious
> User: debia
he next regular /post-jessie/ lirc upload will just remove all
pre-jessie upgrade support (including this change[1]) from the package
anyways...
This piuparts mass bug filing imho would have better concentrated on
just wheezy to jessie issues, rather than murkying the waters by
including squeeze-
s://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769186#41
systemd upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=86707#c3
Signed-off-by: Stefan Lippers-Hollmann
--- a/wpa_supplicant/systemd/wpa_supplicant.service.in
+++ b/wpa_supplicant/systemd/wpa_supplicant.service.in
@@ -1,5 +1,7 @
Hi
On 2015-03-17, Michael Biebl wrote:
[...]
> Am 17.03.2015 um 03:51 schrieb Stefan Lippers-Hollmann:
[...]
> > Looking at it more thoroughly, I think "After=syslog.target" might be
> > needed as well, given that (by default) wpa_supplicant uses the syslog
> >
Hi
On 2015-03-17, Stefan Lippers-Hollmann wrote:
> On 2015-03-17, Michael Biebl wrote:
> > Am 17.03.2015 um 03:51 schrieb Stefan Lippers-Hollmann:
[...]
> There are two pending changes beyond this, but imho neither meet the unblock
> criterias at this stage.
[...]
> - fixing a s
http://snapshot.debian.org/package/wpa/
My hunch remains that this is probably a kernel regression, but
this can only be confirmed with those tests and by someone who
can reproduce the issue/ owns the affected hardware - and if this
really is a bug in wpa_supplicant, ideally b
kely) confirming this, iwlwifi covers a huge range of
quite different wlan chipset generations, some older, some very fresh.
Although Intel is working hard on providing kernel support even before
shipping the actual devices, the quality of support varies between
kernel versions.
Regards
St
y). Equivalent
configuration can be used to configure wpa_supplicant for WEP or
unencrypted networks - or even roaming, if you're looking for a
slightly more sophisticated setup.
Regards
Stefan Lippers-Hollmann
pgppW5d3Xnk2b.pgp
Description: Digitale Signatur von OpenPGP
)
changelog, I assume that this might have been an unintentional
modification. Feel free to close this bug if it was indeed an intentional
change of behaviour.
Regards
Stefan Lippers-Hollmann
-- Package-specific info:
-- System Information:
Debian Release: 8.0
APT prefers unstab
Hi
On 2015-02-25, Stefan Lippers-Hollmann wrote:
[...]
> Overriding tmp.conf back to specify
>
> d /tmp 1777 root root -
Sorry for the typo, this was of course meant to read:
$ grep -v -e ^$ -e ^\# tmp.conf
D /tmp 1777 root root -
x /tmp/systemd-private-%b-*
X /tmp/systemd-private-%
hat src:wpa 1.0-3+deb7u1 in wheezy is not affected by this
bug, as we did (intentionally) disable CONFIG_P2P for those packages.
Regards
Stefan Lippers-Hollmann
pgpPGtMHsDiIU.pgp
Description: Digitale Signatur von OpenPGP
from the UEFI
variable to /lib/firmware). On embedded devices it needs to be provided by
the manufacturer (not Broadcom, but the OEM vendor) of your wlan card
(respectively the devboard).
Regards
Stefan Lippers-Hollmann
[1] These blobs contain calibration data, regulatory dom
ticular SDIO based wlan chipset
is used on multiple architectures (including many windows 8.x based Intel
Atom tablets).
> On Wednesday 02 September 2015 19:37:13 Stefan Lippers-Hollmann wrote:
> > On 2015-09-02, Rainer Dorsch wrote:
[...]
> Are you saying that I opened the bugrepor
dor-
and product IDs.
>
> 00:0d.0 Ethernet controller: Qualcomm Atheros AR5212/5213/2414 Wireless
> Network
> Adapter (rev 01)
> Subsystem: D-Link System Inc AirPlus DWL-G520 Wireless PCI Adapter
> (rev. B)
> Kernel driver in use: ath5k
>
d logs of:
> wpa_supplicant -i wlan0 -ddd -Dnl80211 -c wpa.conf &> nl80211aa.log
> wpa_supplicant -i wlan0 -ddd -Dwext -c wpa.conf &> wextaa.log
As mentioned before, I'd suspect kernel 3.16 in jessie to interfere
here,
if that's the case, it would need closer debugg
Control: forcemerge -1 757124
Hi
On Wednesday 10 September 2014, Andreas Barth wrote:
> * Stefan Lippers-Hollmann (s@gmx.de) [140910 14:24]:
> > On Wednesday 30 April 2014, Breno Leitao wrote:
> > > Lirc is curretnly failing to build on new architectures, as ppc64el.
> &
pdate
or
Acquire::Check-Valid-Until "0";
for apt.
For these reasons I would suggest against changing the current
intervals, especially least not into the hour- or single day regions.
Regards
Stefan Lippers-Hollmann
[1] and even for security.d.o I don't believe th
ems to be a recurring problem with iwlwifi for years, I don't hold
many hopes that it will be fixed any time soon.
Regards
Stefan Lippers-Hollmann
signature.asc
Description: This is a digitally signed message part.
t know about any networks
'misconfigured' in this way and therefore can't debug it locally, I'd
appreciate if you could approach upstream under
HostAP mailing list
hos...@lists.shmoo.com
http://lists.shmoo.com/mailman/listinfo/hostap
and present your case.
twork
[Match]
Name=eth0
[Network]
Bridge=br0
$ cat /etc/systemd/network/60-br0.network
[Match]
Name=br0
[Network]
DHCP=yes
Regards
Stefan Lippers-Hollmann
signature.asc
Description: This is a digitally signed message part.
md/network/60-br0.network
[Match]
Name=br0
[Network]
DHCP=yes
Regards
Stefan Lippers-Hollmann
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.18-rc2-aptosid-amd64 (SMP w/4 CPU
in order not to
interfere with d-i beta2[6]? There are no behavioural changes, besides
many bugfixes[7]. If you want to test it for d-i, the packaging is
ready (besides the changelog entries) in the normal VCS location[8].
Regards
Stefan Lippers-Hollmann
[1]
https://git.kernel.org/cgit
Hi
On Monday 15 September 2014, Cyril Brulebois wrote:
> Stefan Lippers-Hollmann (2014-09-15):
[...]
Seeing that the actual problem are missing kernel modules for
CCMP (AES), and probably TKIP as well, I'll concentrate on your
new questions only
> Based on your answer, I'm w
erly to avoid adding those flags to netcfg before
> wpa is uploaded and possibly has migrated to testing.
[...]
Thanks, I'll try to get it uploaded as soon as possible (hopefully
within the next 1-2 days).
Regards
Stefan Lippers-Hollmann
signature.asc
Description: This is a digitally signed message part.
On Monday 15 September 2014, Ben Hutchings wrote:
> On Mon, 2014-09-15 at 23:08 +0200, Stefan Lippers-Hollmann wrote:
> > On Monday 15 September 2014, Cyril Brulebois wrote:
> > > Stefan Lippers-Hollmann (2014-09-15):
[...]
> > [...] but the udeb
> > should sup
tainer.)
Thanks for the notice, I've changed this in the packaging VCS[1], an
upload for lirc will follow soon (for other reasons).
Regards
Stefan Lippers-Hollmann
[1]
http://lists.alioth.debian.org/pipermail/pkg-lirc-changes/2014-September/000640.html
signature.asc
Description: This is a digitally signed message part.
ity (PPPoE, VPN tunnels, etc.).
If anyone were to step up to maintain this in Debian despite this known
problem, we'd be happy to accommodate Ceni and help with its (existing)
packaging as needed.
Regards
Stefan Lippers-Hollmann
[1] Ceni doesn't deal with inet6 stanzas, wh
;t/ won't take the responsibility for potential
network-manager related regressions 10 days before the freeze[3].
Regards
Stefan Lippers-Hollmann
[1] I'm very interested in networkd, but haven't completely migrated
my relatively advanced networking setup (includin
y
issue.
This is a new upstream version of wpa containing further changes and
features of wpa's stable integration branch[1], rather than a
targetted fix.
unblock wpa/2.3-1
Regards
Stefan Lippers-Hollmann
[1] wpa 2.x is a continuous integration branch for bugfixes and new
ndependent subnets (no interconnections) and typically
with 15-20 tap interfaces used for virtual (kvm) machines).
I can reproduce this with src:systemd 229-1, reverting all installed
src:systemd packages to 228-6 fixes the issue again.
Regards
Stefan Lippers-Hollmann
-- Package-sp
Hi
On 2016-02-13, Stefan Lippers-Hollmann wrote:
[...]
> $ ip -6 r
> 2001:470:1234:10::/64 dev br0 proto ra metric 1024 pref medium
> 2001:470:1234:10::/64 dev enp2s0 proto ra metric 1024 pref medium
> 2001:470:1234:10::/64 dev br1 proto ra metric 1024 pref medium
> 2001:4
Hi
On 2016-02-13, Stefan Lippers-Hollmann wrote:
> On 2016-02-13, Stefan Lippers-Hollmann wrote:
[...]
> Apparently I can work around this problem by explicitly disabling
> IPv6AcceptRouterAdvertisements for enp2s0 and enp4s0:
[...]
> $ ip -6 r
> 2001:470:1234:10::/64 dev br0 p
valent
state and results in functional IPv6 connectivity for me again, while
networkd 229-1, and current upstream git HEAD, are totally broken).
Regards
Stefan Lippers-Hollmann
From f1f54ef2f8509100483cb8dc8a9a2f9c3c823700 Mon Sep 17 00:00:00 2001
From: Stefan Lippers-Hollmann
Date: Thu, 25 Feb
ding on your schedule, I can look into the targeted backports,
but naturally I'd prefer to avoid that (as long as lirc won't be
one of the final blockers).
Regards
Stefan Lippers-Hollmann
pgpqcQgBtZwtO.pgp
Description: Digitale Signatur von OpenPGP
t naturally I'd prefer to avoid that (as long as lirc won't be
one of the final blockers).
Regards
Stefan Lippers-Hollmann
pgpQ9qg5OCG3s.pgp
Description: Digitale Signatur von OpenPGP
documenting this as volatile
and potentially unsupported (in the future) might be a way out,
but I'd still hate to eventually break previously working network
configurations in the future.
Regards
Stefan Lippers-Hollmann
[1] breaks with legacy/ staging (non-cfg80211
time I looked into it,
the build issues were trivial, but quite numerous), I'd tend towards
declining this (however, if there'd be an src:wpa co-maintainer who'd
take care of this aspect...). Have you checked buildability recently?
Regards
Stefan Lippers-Hollmann
pgpa50bOT3paK.pgp
Description: Digitale Signatur von OpenPGP
ively using sudo should also work
$ sudo /usr/sbin/wpa_gui
respectively something like xclock for testing.
Regards
Stefan Lippers-Hollmann
pgppT4PsFrWAk.pgp
Description: Digitale Signatur von OpenPGP
mesa 7.0.1-1 fixes the mentioned issues and using OpenGL becomes
stable on i386 and x86_64.
Thanks a lot for your efforts
Stefan Lippers-Hollmann
[1] http://sidux.com/slh/mesa/Xorg.0.log
[2]
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=dc7a
rned an error code (1)
An alternative download location for wl_apsta.o 3.130.20.0 would be
http://svit.epfl.ch/stuff/wl_apsta.o which seems to be the most current
v3 firmware revision.
Regards
Stefan Lippers-Hollmann
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
until this
issue is fixed in debian's grub(-legacy) packages.
Regards
Stefan Lippers-Hollmann
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.24-slh64-smp-5 (SMP w
e)
and that the patch seems to be of reasonable size, while grub2 doesn't seem
to be ready for mass deployment.
The attached patch has been tested on several amd64 and i386 systems of
varying (ext3) filesystem age and seems to work well with 128 byte and 256
byte inode sizes.
Regards
g modules_clean
exec debian/rules DEBIAN_REVISION=1 modules_clean
make[1]: Entering directory `/tmp/pkg/linux-2.6.24-slh64-smp-7'
for module in /tmp/pkg/modules/qc-usb; do\
if test -d $module; then\
(cd $module;
still leaves a lot of open issues that need to be fixed, like the
inability of using module-assistant as user due to not being able to
write as user at
dh_builddeb --destdir=$(KSRC)/..
or the whole debconf usage.
Regards
Stefan Lippers-Hollmann
Using kernel-package's "make
ility, SET_MODULE_OWNER could be removed unconditionally for
all kernels that are important for lenny (it should be obsolete since
2.5.66).
Tested (iwlist s) with kernel 2.6.23.11 and 2.6.24-rc5-git3 on i386:
06:00.0 Network controller [0280]: Texas Instruments ACX 100 22Mbps Wireless
Interface
against the
running kernel sources/ header while it claims to build against the
specified kernel version).
Proposed changelog entries:
* add kernel 2.6.23 compatibility (Closes: #445430).
* fix module build against correct kernel sources/ header (Closes: #445431).
Regards
Stefan Lippers-Hol
Removing the newly added lzma patches from squashfs alltogether fixes these
bugs (see attached debdiff "squashfs_remove-lzma-patches.diff" and [4]) and
results in valid zlib compressed squashfs images (confirmed on various
amd64 and i386 systems).
Regards
Stefan Lippers-Hollma
34).
* add kernel 2.6.24 compatibility (Closes: $THIS_BUG).
* don't ignore make clean error.
* bump standards version to 3.7.3 (no changes necessary).
Regards
Stefan Lippers-Hollmann
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (50
while the likewise attached
debdiff "virtualbox-ose-source_fix-rules.diff" rewrites
debian/virtualbox-ose-source.rules to deal with the module sources now
residing in a subdir.
Personally I tend to favour "virtualbox-ose-source_fix-installdir.diff", as
it seems to be more consis
tags 502602 + pending
thanks
Hi
On Samstag, 18. Oktober 2008, vince wrote:
> Package: lirc
> Severity: wishlist
> Tags: l10n patch
>
> Enclosed please find the Italian translation of the Debconf template.
Thanks, applied to svn.
> Best regards
> vince
Regards
St
Hi
Sorry, I've been physically away from the notebook since early august till
last weekend.
On Dienstag, 26. August 2008, Brice Goglin wrote:
> On Sun, Jun 01, 2008 at 08:49:18PM +0200, Stefan Lippers-Hollmann wrote:
> > Yes, it is completely dead, open ssh connections trying
= 0
write(0, "(II) SAVAGE(0): [dri] visual conf"..., 49) = 49
fsync(0)= 0
write(0, "(**) SAVAGE(0): DRI is enabled\n"..., 31) = 31
fsync(0) = 0
write(0, "(--) SAVAGE(0): Chose mode 118 at"..., 40) =
ting to squashfs 3.4 would
fix this as well). Severity wishlist, given that testing and l-m-e are
frozen on 2.6.26 anyways.
Regards
Stefan Lippers-Hollmann
[1]
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=51cc50685a4275c6a02653670af9f108a64e01cf
-- Sy
s
in no way an official Debian package.
> Thanks,
> Raphael
Regards
Stefan Lippers-Hollmann
[1] http://svn.debian.org/wsvn/pkg-lirc/lirc/trunk/?rev=335&sc=1
[2] http://sidux.com/debian/pool/fix.main/l/lirc/
http://sidux.com/debian/pool/fix.main/l/lirc/lirc-modules-
nny's 2.6.26-1-amd64 and
2.6.26-1-686 for me (see attached build logs).
Without further information, I strongly suspect an unclean source-/ build
directory (/usr/src/modules/lirc*) to be at fault and am tempted to close
this bugreport.
> Regards: David
Regards
Stefan Lippers
Hi
On Dienstag, 23. Dezember 2008, Guido Günther wrote:
> Hi Stefan,
> On Sun, Dec 07, 2008 at 12:40:00AM +0100, Stefan Lippers-Hollmann wrote:
> > Package: kvm
> > Version: 72+dfsg-3
> > Severity: wishlist
> > Tags: patch
> >
> > Since 1.0.17.dfsg-3
modules-sidux-main-2.6-2.6.28.rev1/debian/build/build_amd64_none_sidux-amd64_qc-usb/qc-driver.o]
Error 1
make[3]: ***
[_module_/tmp/buildd/linux-modules-sidux-main-2.6-2.6.28.rev1/debian/build/build_amd64_none_sidux-amd64_qc-usb]
Error 2
The attached, minimal and tested, patch (which depends on the
lity fix in #504187) fixes this issue, while keeping compatibility
to older kernels. Severity wishlist, given that testing and l-m-e are
frozen on 2.6.26 anyways.
Regards
Stefan Lippers-Hollmann
Post scriptum:
This is a backport of the interdiff between upstream squashfs
squashfs3
audio-drv-list="alsa oss sdl" \
Regards
Stefan Lippers-Hollmann
-- Package-specific info:
selected information from lshal(1):
/proc/cpuinfo:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)
nd-a-half, assuming kernel >=2.6.31 + potential backports:
- working out-of-the-box, not active backporting necessary (OpenFWWF
has no declared runtime dependencies, it just needs a kernel
supporting it)
This indirectly also blocks b43-asm from being useful in the archive.
R
severity=important, because pidof is used in many initscripts
and might have a serious impact on services relying on its output.
Regards
Stefan Lippers-Hollmann
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architect
uging with him, I cannot yet comment
upon it; in general it would imho be better to get gspca_stv06xx working
than investing too much time on qc-usb (otherwise qc-usb would also need
to blacklist gspca_stv06xx).
Regards
Stefan Lippers-Hollmann
signature.asc
Description: This is a digitally signed message part.
derived from Mandriva's (cooker) kernel package [1]
and has originally been written by Herton Ronaldo Krzesinski
, I have mostly rediffed the patch against
acerhk-source and changed the hard proc_dir_entry::owner removal into an
ifdef'ed variant, to keep acerhk compatible with kernels
free
components required - the proprietary firmware can be transparently
coinstalled and supersedes openfwwf, if present.
Regards
Stefan Lippers-Hollmann
[1] BUG #513974: ITP: openfwwf -- Open Firmware for Broadcom b43 wlan
devices
Vcs-Svn: svn://svn.berlios.de/fullstory/ope
Please add the attached patch, which has been tested against kernel 2.6.22
and current 2.6.23 snapshots.
Regards
Stefan Lippers-Hollmann
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kerne
inue?
Given the file comments and the current diversion of the upstream Makefile
inside the Debian packaging (which includes config options and upstream
Makefile), it seems to be possible to remove that inclusion alltogether (the
attached patch has been tested with good results).
Regards
vermagic: 2.6.23-rc9-git2-slh64-smp-1 SMP preempt mod_unload
Regards
Stefan Lippers-Hollmann
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.23-rc8-git4-slh64-smp
besides
the automatically added debhelper stanza for depmod.
Feel free to close this bug report.
Regards
Stefan Lippers-Hollmann
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.
fact being built as root, please file a bug
against /tmp/pkg/modules/et131x.
Hit return to Continue?
The attached patch fixes the issue (compile tested only).
Regards
Stefan Lippers-Hollmann
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT pol
/tmp/pkg/modules/qc-usb-source.
Hit return to Continue?
The attached patch links the "kdist" target to "kdist-image" (which is used
by module-assistant), build tested and confirmed to be working.
Regards
Stefan Lippers-Hollmann
-- System Information:
Debian Release:
t config wizard anymore (without
kdelibs4-dev being installed).
Regards
Stefan Lippers-Hollmann
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.22.6-rc1-slh64-smp-1 (SMP w/1
/share/doc/libxine1-xvdr/changelog.gz
-rw-r--r-- root/root 2149 2007-08-28 18:31
./usr/share/doc/libxine1-xvdr/changelog.Debian.gz
Regards
Stefan Lippers-Hollmann
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architect
Hi
The actual install target in debian/libxine1-xvdr.install of course needs to
be fixed as well:
/usr/share/libxine-xvdr/nosignal.mpg --> /usr/share/libxine1-xvdr/nosignal.mpg
Regards
Stefan Lippers-Hollmann
diff -Nrup vdr-plugin-xineliboutput-1.0.0~rc2-5/debian/libxine1-xvdr.inst
tags 446650 + patch
thanks
Hi
The attached patch extracted from upstream CVS adds compatibility with
kernel 2.6.23 to lirc 0.8.0/ 0.8.1/ 0.8.2. Given that kernel 2.6.23 isn't
even in NEW yet, I wouldn't call this issue grave, but rather minor at best.
Regards
Stefan Lipper
fi
db_go || true
fi
Personally I'd suggest just reverting to a simpler debconf design, like the
one used for bcm43-fwcutter, tested patch attached.
Regards
Stefan Lippers-Hollmann
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
kg/usr_src/modules/linux-wlan-ng/src/prism2/driver/prism2_pci.o] Error 1
make[6]: *** [_module_/tmp/pkg/usr_src/modules/linux-wlan-ng/src/prism2/driver]
Error 2
make[6]: Leaving directory `/usr/src/linux-headers-2.6.23.1-slh64-smp-8'
make[5]: *** [default] Error 2
Current upstream svn >=
ends to actually use libraw1394-8 without its device node, but it
needs to be installable in chroot environments in order to satisfy the build
dependency on libraw1394-dev.
Regards
Stefan Lippers-Hollmann
signature.asc
Description: This is a digitally signed message part.
this patch to
the maintainer scripts (and not update-grub itself), as there are reasons
(rescue system, etc.) to execute update-grub inside a chrooted system
manually (with a full /dev/ (bind-)mounted).
Regards
Stefan Lippers-Hollmann
# cdebootstrap --arch=amd64 --flavour=minimal sid
nstalled kernel version (2.6.29 - 2.6.31-rc6-git5)
Please feel free to reassign to dmsetup (lvm2), but I assume grub-probe
simply can't interpret the mangled udev representation since dmsetup got
installed.
Regards
Stefan Lippers-Hollmann
$ grep -v -e ^\# -e ^$ /etc/fstab
/
Hi
On Wednesday 19 August 2009, Felix Zielcke wrote:
> Am Mittwoch, den 19.08.2009, 18:12 +0200 schrieb Stefan
> Lippers-Hollmann:
[...]
> > Since 2.02.51-1 (17 Aug 2009), lvm2 depends on dmsetup, which ships a few
> > udev rules:
> >
> > /lib/udev/rules.d/55-dm.
orts for kernel innards, which are totally inacceptable
for kernel upstream and likely debian-kernel as well. But maybe aufs v1 can
be kept on life support until VFS based unions mounts arrive mainline.
Regards
Stefan Lippers-Hollmann
-- System Information:
Debian Release: squeeze/sid
APT p
ll
ask for an upload.
The whole patch series, as far as if applies to upstream lirc, will be
discussed with upstream as soon as we've imported lirc 0.8.6 (when we have
a non-RC buggy version in testing) and refreshed the it against a more
current upstream version.
Regards
Stefan Lippers-Hollmann
signature.asc
Description: This is a digitally signed message part.
pendency gets added to the next lirc upload.
Regards
Stefan Lippers-Hollmann
signature.asc
Description: This is a digitally signed message part.
..]
I guess I know what breaks, but this makes me wonder...
[...]
> Kernel: Linux 2.6.30-1-686 (SMP w/2 CPU cores)
[...]
Does it oops on kernel 2.6.26 XOR the current default kernel in squeeze,
2.6.30-1-686, (or both)?
Could you please give current svn HEAD[1] or
http://sidux.com/debian/pool/fix.main/l/lirc/lirc-modules-source_0.8.3-5+svnr379.1_all.deb
a try?
Regards
Stefan Lippers-Hollmann
[1] Vcs-Svn: svn://svn.debian.org/svn/pkg-lirc/lirc/trunk/
signature.asc
Description: This is a digitally signed message part.
xine_input_vdr.c[1] stands out and
using a fresh (20091013.2051) CVS checkout indeed reliably fixes the
problem for me.
Regards
Stefan Lippers-Hollmann
[1]
http://xineliboutput.cvs.sourceforge.net/viewvc/xineliboutput/vdr-xineliboutput/xine_input_vdr.c?revision=1.286&view=markup
F
nd running.
[...]
Recommends are a weak depends and installed by default since lenny, given
that there are 15 other kernel modules that have no use for setserial, it
is out of the question to promote it to a recommends. A suggests on the
other hand is a good idea and a corresponding patch has just been
would stand a chance for Debian
inclusion. If there is a chance for this (namely a plan to get rid off
nx-X11 and a few more code contributors), I am very interested in
participating in that endeavour, but as it stands, chances for that don't
seem to be very encouraging.
> cheers,
#x27;t seem to justify immediate action and will
be fixed by the next regular upload.
Regards
Stefan Lippers-Hollmann
signature.asc
Description: This is a digitally signed message part.
Hi
On Mittwoch, 19. März 2008, Sven Mueller wrote:
> Stefan Lippers-Hollmann wrote on 18/03/2008 17:49:
> > Agreed, the current use of local in lirc's initscript is neither covered by
> > SUSv3, the exceptions from SUSv3 described in Debian policy 10.4, nor
> > ac
m
within lirc, but would have to be done to linux-2.6, which isn't an option,
neither upstream (the changes are intended and no in-tree module suffers
from it, furthermore lirc_gpio has been accessing parts it was never meant
to access) nor for Debian's kernel packages.
The solution... I'm not sure yet, but lirc_gpio needs to be fixed in a
non-trivial way and I cannot speculate about the impact or a time frame,
yet.
> greets
Thanks for reporting
Stefan Lippers-Hollmann
signature.asc
Description: This is a digitally signed message part.
fPIC
tools/vdrdiscovery.o: could not read symbols: Bad value
collect2: ld returned 1 exit status
make[1]: *** [libvdr-xineliboutput.so] Error 1
Empirical testing reveals CFLAGS and CXXFLAGS to be the culprits, see
attached (and confirmed to be working) patch.
Regards
Stefan Lippers-Hollma
201 - 300 of 411 matches
Mail list logo
