Bug#485513: ITP: smbind -- PHP-based tool for managing DNS zones for BIND
Package: wnpp Severity: wishlist Owner: Giuseppe Iuculano <[EMAIL PROTECTED]> * Package name: smbind Version : 0.4.7 Upstream Author : Ole Myhre <[EMAIL PROTECTED]> * URL : http://sourceforge.net/projects/smbind/ * License : GPL Programming Lang: Php Description : PHP-based tool for managing DNS zones for BIND Smbind is a PHP-based tool for managing DNS zones for BIND via the web. Supports per-user administration of zones, error checking, and a PEAR DB database backend. This tool will enable you to administer your bind-based DNS server without having to touch your zone files with a text editor, while also providing a redundant backup of the data stored in both a PEAR DB database and in the normal text configuration files. Since it is web-accessible, those without shell access or command-line skills (or whom are just plain lazy) can enjoy DNS administration from the comfort of a remote browser. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (990, 'stable'), (500, 'proposed-updates'), (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.25.5-iuculano Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#487263: ITP: atmail -- An Open Source Webmail Client
Package: wnpp Severity: wishlist Owner: Giuseppe Iuculano <[EMAIL PROTECTED]> * Package name: atmail Version : 1.01 Upstream Author : @Mail <[EMAIL PROTECTED]> * URL : http://www.atmail.org/ * License : Apache License Version 2.0 Programming Lang: Php Description : An Open Source Webmail Client AtMail is an open source webmail client written in PHP. It aim to provide a elegant Ajax webmail client for existing IMAP mailservers, with less bloat and a focus on an intuitive, simple user interface. The open source version of AtMail provides users with a lightweight, yet powerful webmail client. The software can be installed on a variety of platforms with ease and without the hassles that most webmail platforms impart. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#492807: ITP: procinfo-ng -- displays system information from /proc
Package: wnpp Severity: wishlist Owner: Giuseppe Iuculano <[EMAIL PROTECTED]> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 * Package name: procinfo-ng Version : 2.0.196 Upstream Author : Thaddeus Messenger <[EMAIL PROTECTED]> * URL : http://procinfo-ng.sourceforge.net * License : GPL Programming Lang: C++ Description : displays system information from /proc Procinfo-NG is a small program that gathers some system information from diverse files under /proc and prints it to the screen. Procinfo-NG is a complete rewrite of the old system monitoring app procinfo. The goal is to make more readable (and reusable) code and to restore broken functionality. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkiOU6gACgkQNxpp46476ap6sACeLp+34LO762Z2falQMU7+JuiS FYUAn08UbdIkpaOBo/DMBRGBlG7mr1e7 =T/A6 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#492922: ITP: arpon -- arp handler inspection
Package: wnpp Severity: wishlist Owner: Giuseppe Iuculano <[EMAIL PROTECTED]> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 * Package name: arpon Version : 1.40 Upstream Author : Andrea Di Pasquale <[EMAIL PROTECTED]> * URL : http://arpon.sourceforge.net * License : BSD Programming Lang: C Description : arp handler inspection ArpON (Arp handler inspectiON) is a portable handler daemon with some nice tools to handle all ARP aspects. It makes Arp a bit safer. This is possible using two kinds of anti Arp Poisoning tecniques, the first is based on SARPI or "Static Arp Inspection", the second on DARPI or "Dynamic Arp Inspection" approach. You can use ArpON to pentest some switched/hubbed LAN with/without DHCP protocol, in fact you can disable the daemon in order to use the tools to poison the ARP Cache -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkiPi1kACgkQNxpp46476aqt+QCdHNmvK/09FtkXT8XLClEi4N5l TbkAmwRHVRZNi4rKt32eAXadZtMzSqOe =Mco1 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#492922: ITP: arpon -- arp handler inspection
Guus Sliepen ha scritto: > On Tue, Jul 29, 2008 at 11:27:55PM +0200, Giuseppe Iuculano wrote: > >> Description : arp handler inspection > > That is not a short description, that is just the expansion of the > acronym. Yes, this won't to be package synopsis. > That is just ripped from the website. Yes, this is only a rip from upstream website. > It is not very clear to me if this > is a stand-alone daemon or some command-line tools or both, both > if it works > as a real, bona-fide ARP daemon or if it is some kind of intrusion > detection tool or vulnerability scanner. Arpon is quite versatile, the main goal is to be an anti arp poisoning daemon, but it can be an arp passive sniffer, arp cache manager ecc.. You can read this: http://arpon.sourceforge.net/manpage.html http://arpon.sourceforge.net/documentation.html > Other interesting things to know: How does arpon relate to existing > packages like arpalert, arping, arptables and farpd? Sorry, I don't understand this question, what problems could I have with arping arpalert ecc.? > Does it also > handle Neighbour Discovery packets (IPv6's equivalent of ARP)? As before, the main goal is to be an anti arp poisoning daemon, I'm not sure, but with IPv6 this shouldn't be relevant. Giuseppe Iuculano. signature.asc Description: OpenPGP digital signature
Bug#495284: ITP: apf -- easy iptables based firewall system
Package: wnpp Severity: wishlist Owner: Giuseppe Iuculano <[EMAIL PROTECTED]> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 * Package name: apf Version : 9.6-4 Upstream Author : R-fx Networks <[EMAIL PROTECTED]> * URL : http://www.r-fx.org/apf.php * License : GPL Programming Lang: bash Description : easy iptables based firewall system Advanced Policy Firewall (APF) is an iptables(netfilter) based firewall system designed around the essential needs of today's Internet deployed servers and the unique needs of custom deployed Linux installations. The configuration of APF is designed to be very informative and present the user with an easy to follow process, from top to bottom of the configuration file. The management of APF on a day-to-day basis is conducted from the command line with the 'apf' command, which includes detailed usage information and all the features one would expect from a current and forward thinking firewall solution. Summary of features: - - detailed and well commented configuration file - - granular inbound and outbound network filtering - - user id based outbound network filtering - - application based network filtering - - trust based rule files with an optional advanced syntax - - global trust system where rules can be downloaded from a central management server - - reactive address blocking (RAB), next generation in-line intrusion prevention - - debug mode provided for testing new features and configuration setups - - fast load feature that allows for 1000+ rules to load in under 1 second - - inbound and outbound network interfaces can be independently configured - - global tcp/udp port & icmp type filtering with multiple methods of executing filters (drop, reject, prohibit) - - configurable policies for each ip on the system with convenience variables to import settings - - packet flow rate limiting that prevents abuse on the most widely abused protocol, icmp - - prerouting and postrouting rules for optimal network performance - - dshield.org block list support to ban networks exhibiting suspicious activity - - spamhaus Don't Route Or Peer List support to ban known "hijacked zombie" IP blocks - - any number of additional interfaces may be configured as firewalled (untrusted) or trusted (not firewalled) - - additional firewalled interfaces can have there own unique firewall policies applied - - intelligent route verification to prevent embarrassing configuration errors - - advanced packet sanity checks to make sure traffic coming and going meets the strictest of standards - - filter attacks such as fragmented UDP, port zero floods, stuffed routing, arp poisoning and more - - configurable type of service options to dictate the priority of different types of network traffic - - intelligent default settings to meet every day server setups - - dynamic configuration of your servers local DNS revolvers into the firewall - - optional filtering of common p2p applications - - optional filtering of private & reserved IP address space - - optional implicit blocks of the ident service - - configurable connection tracking settings to scale the firewall to the size of your network - - configurable kernel hooks (ties) to harden the system further to syn-flood attacks & routing abuses - - advanced network control such as explicit congestion notification and overflow control - - special chains that are aware of the state of FTP DATA and SSH connections to prevent client side issues - - control over the rate of logged events, want only 30 filter events a minute? 300 a minute? - you are the boss - - logging subsystem that allows for logging data to user space programs or standard syslog files - - logging that details every rule added and a comprehensive set of error checks to prevent config errors - - if you are familiar with netfilter you can create your own rules in any of the policy files - - pluggable and ready advanced use of QoS algorithms provided by the Linux - - 3rd party add-on projects that compliment APF features -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkil9/IACgkQNxpp46476aq+UACeMLOoO5PeUxXm/Uzmp39pVXmf emoAoJwcX9p/CpCqgHWlibGIbGCbxX6I =90zt -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#503395: ITP: libapache2-mod-spamhaus -- Apache module that use DNSBL to deny access to a known bad IP address
Package: wnpp Severity: wishlist Owner: Giuseppe Iuculano <[EMAIL PROTECTED]> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 * Package name: libapache2-mod-spamhaus Version : 0.5 Upstream Author : Luca Ercoli <[EMAIL PROTECTED]> * URL : http://sourceforge.net/projects/mod-spamhaus/ * License : GPL Programming Lang: C Description : Apache module that use DNSBL to deny access to a known bad IP address mod_spamhaus is an Apache module that use DNSBL in order to block spam relay via web forms, preventing URL injection, block http DDoS attacks from bots and generally protecting your web service denying access to a known bad IP address. It take advantage of the Spamhaus Block List (SBL) and the Exploits Block List (XBL) querying xbl-sbl.spamhaus.org Spamhaus's DNSBLs are offered as a free public service for low-volume non-commercial use. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkkDPLUACgkQNxpp46476aoy7QCfbk1xnO8swp+ppixTANmSWFyP VaMAnRrttNnEwBAPFzarhH/yTmqO/lAx =tDZa -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#503395: ITP: libapache2-mod-spamhaus -- Apache module that use DNSBL to deny access to a known bad IP address
Ralf Hildebrandt ha scritto: > Or zen.spamhaus.org (which is actually a BIT more, but the recommended > list) Recommended for smtp service, not for web server. Giuseppe. signature.asc Description: OpenPGP digital signature
Bug#503469: ITP: nmapsi4 -- interface to nmap, the Network scanner
Package: wnpp Severity: wishlist Owner: Giuseppe Iuculano <[EMAIL PROTECTED]> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 * Package name: nmapsi4 Version : 0.1 Upstream Author : Francesco Cecconi <[EMAIL PROTECTED]> * URL : http://nmapsi4.netsons.org/web/ * License : GPL Programming Lang: C++ Description : interface to nmap, the Network scanner NmapSI4 s a complete Qt-based Gui with the design goals to provide a complete nmap interface for Users, in order to menagement all options of this power security net scanner. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkkEWzYACgkQNxpp46476aoTpgCfdNxjcfS5oj75/6IDsUjIoplQ eXgAn1Ywhf7KZy/fVlMlW3wbSBlELx0N =NfXb -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#504165: ITP: dm-raid45 -- Source for the dm-raid45 driver
Package: wnpp Severity: wishlist Owner: Giuseppe Iuculano <[EMAIL PROTECTED]> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 * Package name: dm-raid45 Version : 20081027 Upstream Author : Heinz Mauelshagen <[EMAIL PROTECTED]> * URL : http://people.redhat.com/heinzm/sw/dm/dm-raid45/ * License : GPL Programming Lang: C Description : Source for the dm-raid45 driver This package provides the source code for the dm-raid45 kernel modules. This software extends device-mapper by RAID4 and RAID5 mappings. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkkMJWIACgkQNxpp46476aovqACePI2pnTKfV54Xd4BHaHuTd2JV dhQAnjVhdSb3w5aq2q23wMMis/PUNewY =uArc -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#513577: ITP: fspy -- filesystem activity monitoring tool
Package: wnpp Severity: wishlist Owner: Giuseppe Iuculano -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 * Package name: fspy Version : 0.1.0 Upstream Author : Richard Sammet * URL : http://mytty.org/fspy/ * License : GPL Programming Lang: C Description : filesystem activity monitoring tool fspy is an easy to use Linux filesystem activity monitoring tool which is meant to be small, fast and to handle system resources conservative. You can apply filters, use diffing and your own output format in order to get the best results. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkmC9FoACgkQNxpp46476apZQgCdE6xtxMfPFa9fR89NFyaFM7ub p8YAn12zj8bx44ovdX9SVHKfFfZAa00k =mulS -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#440968: ITP: qmailadmin -- web interface for managing a qmail system with virtual domains
Package: wnpp Severity: wishlist Owner: Giuseppe Iuculano <[EMAIL PROTECTED]> * Package name: qmailadmin Version : 1.2.11 Upstream Author : Ken Jones <[EMAIL PROTECTED]> * URL : http://sourceforge.net/projects/qmailadmin/ * License : GPL Programming Lang: C Description : free software package that provides a web interface for managing a qmail system with virtual domains QmailAdmin is a web interface for managing email addresses in virtual domains created by Vpopmail. It provides admin for adding/deleting users, Aliases, Forwards, Mailing lists and Autoresponders. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (990, 'stable'), (500, 'proposed-updates'), (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.22.5-iuculano Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: chromium-browser from experimental has included h.264 by default?
Hi, Il 10/05/2010 22:15, Iker Salmón San Millán ha scritto: > Hi, i didn't know where or how to report this, but i have readed in a > forum that an user has tried |chromium-browser from experimental and > seems that it includes by default those privative codecs. I have tried > by myself and i agree with him, but maybe i am wrong. No, it doesn't contain those, see below > Purging those packages and installin chronium-browser from experimental > i can watch those videos without installing anything else. > > Is this correct? does chromium-browser package in debian have |h264 > codecs included? is this because it is in experimental and they will be > separated later? or just a mistake? or maybe those codecs are included > in other package installed that i haven't seen? Chromium in Debian is built against the system FFmpeg headers via pkg-config. This means when Chromium is launched it will assume that FFmpeg is present in the system library path. In this way you can decide which codecs chromium will use. If you can watch youtube html5 video, probably you have installaed libavcodec52, libavformat52 and libavutil50 from debian-multimedia[1] or other third repositories. BTW, here[2] you can find instructions how to report a bug in Debian [1]http://debian-multimedia.org/ [2]http://www.debian.org/Bugs/Reporting Cheers, Giuseppe. signature.asc Description: OpenPGP digital signature
Re: chromium-browser from experimental has included h.264 by default?
severity 580947 important thanks Il 11/05/2010 10:44, Reinhard Tartler ha scritto: > checking [2], reveals that I'm partly wrong. There is an in-source copy > of ffmpeg, that there is an option 'use_system_ffmpeg=1' passed to the > buildscript. This indicates that I indeed missed that upstream now > considers this. Still, I also note that a library > out/Release/obj.target/third_party/ffmpeg/libffmpeg.a is being > built. also note the following changelog comment: > >* Ops, libavutil50 is not yet in Debian, removed from depends (Closes: > #580769) > - update debian/control > > > > I can only assume that the functionality to link and use the system > ffmpeg is severely broken. One more reason to have bug #580947 at > severity serious. I disagree with this interpretation, please explain why this is broken. chromium doesn't compile with the current version of ffmpeg in unstable because it is too outdated, this means I had three choices: - compile with use_system_ffmpeg=0 and build_ffmpegsumo=0 (this means drop ffmpeg support) - compile with use_system_ffmpeg=1 and build_ffmpegsumo=0 --> FTBFS - compile with use_system_ffmpeg=1 and build_ffmpegsumo=1 (this means compile and ship ffmpeg-mt) There was another solution, and this is now adopted in the latest experimental package, Compile with use_system_ffmpeg=1 and build_ffmpegsumo=0, but use the in-sources include path for headers, see [1] and [2]. In this way, chromium doesn't FTBFS but use the system ffmpeg libs (if they are available). Unfortunately it searches also libavutil50, this is in not yet in the archive, it is in NEW (experimental) or in debian-multimedia repository. [1]http://patch-tracker.debian.org/patch/series/view/chromium-browser/5.0.375.29~r46008-2/ffmpeg-no-pkgconfig.patch [2]http://src.chromium.org/viewvc/chrome/trunk/src/media/base/media_posix.cc?r1=43030&r2=43029&pathrev=43030 Cheers, Giuseppe. signature.asc Description: OpenPGP digital signature
Re: chromium-browser from experimental has included h.264 by default?
Il 11/05/2010 17:35, Ben Hutchings ha scritto: > How can you expect this to work? The ABI of the system ffmpeg libraries > is not going to match the ABI defined by the bundled headers. You must > patch chromium to work with the system ffmpeg headers. chromium doesn't link against the ffmpeg libraries, it dlopen() them, so you are right for libavcodec52 libavformat52, but for libavutil50 it searches /usr/lib/chromium-browser/libavutil.so.50 , and this is a symlink to /usr/lib/libavutil.so.50 . If it doesn't find it you have the "Aw, Snap!" message or the "Sorry, your browser does not support the element." message. In a standard Debian system, and with standard I mean a system with no other third repositories, simply it doesn't use that lib. At this point I removed that patch and made a new one that affects only libavutil50 (not yet available in the archive): -#include -#include +#include "patched-ffmpeg-mt/libavutil/avutil.h" +#include "patched-ffmpeg-mt/libavutil/log.h" So if I'm not wrong now there isn't any ABI incompatibility here because libavutil50 doesn't exist as official package. Is this acceptable? Cheers Giuseppe signature.asc Description: OpenPGP digital signature
Re: chromium-browser from experimental has included h.264 by default?
Il 12/05/2010 06:38, Reinhard Tartler ha scritto: > TBH, I'm very skeptical. While I'm not sure why google has decided to > choose astrange's branch/fork, I fear that there have been too many > changes to the external public API that this is not going to work out. > I'm basing this opinion on the Giuseppe's observation that Chromium does > not even compile against ffmpeg 0.5 (debian' system) ffmpeg. > It would be of course interesting to see how this works out with ffmpeg > 0.6 (currently in NEW), but for totally unrelated reasons to this one, I > fear it won't be processes as well, just like mplayer. I already tried to compile against the ffmpeg in NEW, and it compiles fine (and works fine). For this reason, waiting the new version in NEW, the ugly hack for the current version in unstable was a tentative to obtain a working chromium for users with and without debian-multimedia repository in sources.list. > For this reason, I think that chromium > upstream is providing excellent security support for its copy of ffmpeg! I full agree, I contacted the chromium security team some time ago asking an help to triage all security vulnerabilities in our sec tracker. I was impressed by their responsiveness and helpfulness. Cheers, Giuseppe. signature.asc Description: OpenPGP digital signature
Re: SRWare Iron: Chromium without the data-mining
Il 18/05/2010 19:12, Ryan Oram ha scritto: > "Chrome Incognito Tracks Visited Sites" > http://www.lewiz.org/2010/05/chrome-incognito-tracks-visited-sites.html I just backported upstream commit that fixes this huge privacy killer bug... > This seems to be becoming a theme. As Chromium has much of the same > privacy issues as Chrome (SRWare Iron is made from Chromium and the > code is striped from Chromium), this "feature" is surely in Chromium > as well. > I find this completely unacceptable. Please report[1] these privacy issues more explicitly than referring to a related blog post. [1]http://www.debian.org/Bugs/Reporting Cheers, Giuseppe signature.asc Description: OpenPGP digital signature
Bug#583826: RFH: chromium-browser -- Chromium browser
Package: wnpp Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I request assistance with maintaining the chromium-browser package. In reality, the team mentioned in the Maintainer field currently consists of me. This package really needs a team to work on it. Alioth project: https://alioth.debian.org/projects/pkg-chromium/ Currently I use bzr because the original Ubuntu maintainers use it and because I didn't find a way to to use git-import-dsc/git-buildpackage/etc with the only debian/ dir. The package description is: Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. . Chromium serves as a base for Google Chrome, which is Chromium rebranded (name and logo) with very few additions such as usage tracking and an auto-updater system. . This package contains the Chromium browser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkwC1rUACgkQNxpp46476aoUAQCfV5BG4B1fdH9k5KmToMUAtl8x i9wAn3M8DEFqflScV1a1fZSW0xyz2lye =ZEZU -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100530212102.27926.89613.report...@sd6-casa.iuculano.it
Re: chromium-browser in Debian Sid
On 06/30/2010 06:15 AM, Aaron Toponce wrote: > I just noticed that the chromium-browser package releases in Debian > GNU/Linux unstable are synced version-for-version with the google-chrome > beta package provided by the 3rd party Google Linux repository. Is this > intentional? No, we follow the stable channel. > What's the rationale behind using the beta releases for > chromium-browser in Debian rather than just using the nightlies? Should we use the Chromium nightly builds ? Really? :) Cheers, Giuseppe. signature.asc Description: OpenPGP digital signature
dkms needs a pre-depends entry (Policy 3.5)
On 07/17/2010 03:50 PM, Julien Cristau wrote: > You should not specify a `Pre-Depends' entry for a package before this > has been discussed on the `debian-devel' mailing list and a consensus > about doing that has been reached. > > Did you do that? No I didn't, I'm doing that now. dkms needs lsb-release in Pre-Depends, otherwise if lsb-release is unpacked but not yet configured, dkms modules can fail to install with the following error: (#589308) Setting up nvidia-kernel-dkms (195.36.24-4) ... Loading new nvidia-195.36.24 DKMS files... Traceback (most recent call last): File "/usr/bin/lsb_release", line 26, in import lsb_release ImportError: No module named lsb_release Traceback (most recent call last): File "/usr/bin/lsb_release", line 26, in import lsb_release ImportError: No module named lsb_release First Installation: checking all kernels... Building only for 2.6.32-5-amd64 Traceback (most recent call last): File "/usr/bin/lsb_release", line 26, in import lsb_release ImportError: No module named lsb_release Traceback (most recent call last): File "/usr/bin/lsb_release", line 26, in import lsb_release Any objections to add the Pre-Depends entry? Cheers, Giuseppe. signature.asc Description: OpenPGP digital signature
Re: dkms needs a pre-depends entry (Policy 3.5)
On 07/17/2010 05:49 PM, Julien Cristau wrote: > This looks to me like a missing dependency on lsb-release in > nvidia-kernel-dkms, not in dkms. And I don't understand why a > Pre-Depends would be necessary anywhere. Care to explain? nvidia-kernel-dkms postint runs /usr/lib/dkms/common.postinst (added by dh_dkms) so imho this is not a missing dependency in nvidia-kernel-dkms. Anyway you are right, I was under the impression that lsb-release was used in preinst, and not in postinst. So a Depends entry is sufficient, I will fix that soon. Cheers. Giuseppe. signature.asc Description: OpenPGP digital signature
Re: chromium-browser from experimental has included h.264 by default?
On 08/10/2010 09:25 PM, Adam D. Barratt wrote: >> > Chromium isn't meant to be released with Squeeze. We'll reevaluate for >> > Squeeze+1. > Is that still the case? No, it isn't. Please see #581265 and in particular message #32, #37 and #44 Cheers, Giuseppe. signature.asc Description: OpenPGP digital signature
