Re: support for merged /usr in Debian

On Jan 01, Bastien ROUCARIES wrote: > > My maintscripts are a total of four commands and they have used for at > > least 9 months in packages with priority important (nano) and required > > (debianutils), with no problems reported. > > If you believe that they are

Re: support for merged /usr in Debian

On Dec 31, Marc Haber wrote: > Please consider keeping support for separate /usr as it is done today. > Mounting /usr in initrd is an acceptable workaround. The whole point of the merged /usr scheme is to support a separate /usr file system, except that this way it

Re: support for merged /usr in Debian

On Dec 31, Bastien ROUCARIES wrote: > Yes I have some question. You do not answered point given in #767754 > about dpkg-divert. Moreover guillem and me consider that symlinking > lib is evil. Because I still do not really understand your objections nor which

Accepted inn2 2.6.0-1 (source i386) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 31 Dec 2015 00:44:10 +0100 Source: inn2 Binary: inn2 inn2-lfs inn2-inews inn2-dev Architecture: source i386 Version: 2.6.0-1 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri <m...@linux.it> Changed-By:

support for merged /usr in Debian

We have a reasonably tested usrmerge package which can be used to convert on the fly a system to merged /usr, and the good news is that there are only three packages which need to be fixed to work on a merged /usr system. Thanks to my conversion program in usrmerge there is no need for a flag

Re: Packages with /outdated/ packaging style

On Dec 28, Santiago Vila wrote: > Hmm... Are you suggesting that "hello-traditional" should be converted to dh? > > I have mixed feelings about putting in the same bag things which are > clearly bugs with things which are not necessarily bugs. Indeed. So far I have not seen

Accepted tin 1:2.3.2-1 (source i386) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 27 Dec 2015 06:20:32 +0100 Source: tin Binary: tin Architecture: source i386 Version: 1:2.3.2-1 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri <m...@linux.it> Changed-By: Marco d'Itri <m...@linux.it>

Accepted usrmerge 3 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 27 Dec 2015 14:26:51 +0100 Source: usrmerge Binary: usrmerge Architecture: source all Version: 3 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri <m...@linux.it> Changed-By: Marco d'Itri <m...

Accepted ladvd 1.1.1~pre1-2 (source i386) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 27 Dec 2015 14:41:24 +0100 Source: ladvd Binary: ladvd Architecture: source i386 Version: 1.1.1~pre1-2 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri <m...@linux.it> Changed-By: Marco d'Itri <m...

Re: Bug#808414: ITP: ms-sys -- Program for writing Microsoft compatible boot records

On Dec 20, lucas castro wrote: > I'll take a look at ms-sys-free. Can you clarify which features it provides over the existing mbr package? -- ciao, Marco signature.asc Description: PGP signature

Re: Bug#808414: ITP: ms-sys -- Program for writing Microsoft compatible boot records

Package: ntfs-3g Version: 0.0.0+20070920-1 Severity: serious On Dec 20, Sam Morris wrote: > That reminds me... I wonder if anyone has looked into the legal status of > boot_array from ntfs-3g? > > https://sources.debian.net/src/ntfs-3g/1:2015.3.14AR.1-1/ntfsprogs/boot.c/

Accepted kmod 22-1 (source i386) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 20 Dec 2015 17:04:10 +0100 Source: kmod Binary: kmod libkmod2 libkmod-dev libkmod2-udeb Architecture: source i386 Version: 22-1 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri <m...@linux.it> Changed-By:

Re: debian.org mail forwarding, SPF and Postfix

On Dec 08, Daniel Pocock wrote: > Can anybody comment on the recommended way to allow mail forwarded from > debian.org mail servers? You whitelist them from your SPF checks, because SPF is the kind of FUSSP which requires the whole Internet to modify their servers to support

Accepted whois 5.2.11 (source i386) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 08 Dec 2015 07:43:48 +0100 Source: whois Binary: whois Architecture: source i386 Version: 5.2.11 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri <m...@linux.it> Changed-By: Marco d'Itri <m...

Re: sid on openvz

On Dec 07, Aurelien Jarno wrote: > Have there also backported recent glibc or systemd to these systems and > do they support such a configuration? This is what we are talking about > here. The *hosts* still use Centos 6, but so far more recent guests releases, even using

Re: sid on openvz

On Dec 03, James Cloos wrote: > Most openvz run on kernels based on 2.6.32, often with significant > updates. These platforms are an important segment, given how affordable > they are. And Debian "stable" is often too archaic for many needs which > fit nicely on a small

Re: [HEADSUP] dropping xconsole support from default rsyslog configuration

On Nov 08, Michael Biebl wrote: > What I'm not quite sure yet is, if I should add a NEWS entry for that. I > guess for most users it would just be useless noise during the upgrade > process. But I'm willing to add it if others think it's useful to have. Please don't. Having

Bug#749647: Ping

On Nov 06, Dima Kogan wrote: > Hi. Can we talk about this again? Should I Cc -devel, or is the I hope not. > reassignment to 'general' enough? It would be totally wrong. > The argument for guile in default 'make' is as before. And also the So I suppose that the arguments

Re: Defaulting to i686 for the Debian i386 architecture

On Sep 28, Ben Hutchings wrote: > We propose to drop support for i386 processors older than 686-class in > the current release cycle. Yes please. > Indeed, the likely reasons for users to choose i386 over amd64 today > are to reduce memory consumption or to run i386

Re: Bug#799336: general: Prepare for quantum computers breaking encryptions

On Sep 18, "Iain R. Learmonth" wrote: > I would have no idea where to start for quantum safe crypto, and while this > is an issue for upstreams mainly, getting an idea of where Debian is in this > landscape currently and identifying the most important areas that need work >

Re: Status of the src:lsb package (was: Debian LSB compliance)

On Sep 17, Didier 'OdyX' Raboud wrote: > This change landed in stretch on September 14. and is de facto the > "outright giving up" of LSB support for Debian, from stretch onwards. As Is there any point in (formally?) maintaining LSB compatibility? Is there any proprietary

Re: Security concerns with minified javascript code

On Sep 01, Nikolaus Rath wrote: > I don't think 28 kB vs 73 kB is a difference that people will notice > over the network in *most* situations. Even at just 100 kB/s that's > 0.28 vs 0.73 seconds, and only when the page is first loaded. Yes, this is a non trivial difference

Re: Security concerns with minified javascript code

On Sep 01, Guido Günther wrote: > Couldn't we just use the non-minified versions in most situations? A Not for anything which has actual users over the network. > heavily loaded wordpress site might not be good example but e.g. doxygen > documentation probably doesn't suffer

Re: system upgrade by systemd

On Aug 31, Dimitri John Ledkov wrote: > Ideally the update generators, targets and units should be split into > a separate package and not installed by default. Since those are > really unexpected on Debian. No, because the system update infrastructure stays idle until some

Re: Summary of the DebConf firmware discussion

On Aug 29, Stefano Zacchiroli z...@debian.org wrote: My rationale for this is as follows. First, Debian official installation image are conceptually part of what we call Debian, i.e., main. I see no other possible logical interpretation of where those images reside w.r.t. the archive

Re: Summary of the DebConf firmware discussion

On Aug 28, Steve McIntyre st...@einval.com wrote: Our users are finding problems with current common hardware - much of it depends on loadable firmware. Much (most?) of that firmware is non-free; we distribute what we can here in the non-free component of the Debian archive. This now means

Accepted usrmerge 2 (source all) into unstable, unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 05 Aug 2015 05:09:52 +0200 Source: usrmerge Binary: usrmerge Architecture: source all Version: 2 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri m...@linux.it Changed-By: Marco d'Itri m...@linux.it Description

Re: Security concerns with minified javascript code

On Aug 26, Russ Allbery r...@debian.org wrote: Maybe there's some pragmatic approach that I haven't thought of yet that will make this less painful. That's what I'm hoping for. Me too: I really care that Debian will continue to be relevant. -- ciao, Marco pgpMdNWptTf8g.pgp Description: PGP

Re: Minutes from the 32bit architectures in Debian-bof

On Aug 25, Russ Allbery r...@debian.org wrote: - for i386, there is still sold new hardware with 32bit-only. Are there open issues for i386 (apart from the 32bit-generic ones)? Discussion that we need to get rid of it one day should be started. Can we fully support cross-grading to

Re: Automated download/update of data files

On Aug 25, Ole Streicher oleb...@debian.org wrote: What is the best way to keep these data up to date in Debian? An automated process as written in the pull request [1] is probably not the right way, since it is a potential privacy violation. One could let the I am frankly tired of people

Re: git interface to snapshot.debian.org

On Aug 20, Joachim Breitner nome...@debian.org wrote: I have not thought of recreating the history of the upstream versions correctly. I mostly care about the “what was in Debian” aspect of history, but it should not hurt to have the upstream branches as well. I am not sure then that I see how

Re: git interface to snapshot.debian.org

On Aug 18, Joachim Breitner nome...@debian.org wrote: this is a follow-up to my question after the dgit talk today: It would be great to have a git view of the a package’s history in Debian. There I have spent quite a lot of time in 2014 to figure out how to automatically import in git

Re: Debian is not welcome on Microsoft Azure

On Aug 16, Russ Allbery r...@debian.org wrote: This is sadly very typical of any sort of vendor support. I see this all the time for complex software stacks with support contracts (you can only ask them for support if you run it all on some OS that they support) or for anything that requires

Re: certificate creation in postinst, potentially using letsencrypt script

On Aug 02, Daniel Pocock dan...@pocock.pro wrote: Does anybody prefer to see packages create certificates during postinst or is there any preference not to try that and let people do so manually? There is no point in trying to get a certificate from letsencrypt every time you install a package

Accepted libsystemd-dummy 222-1 (source kfreebsd-amd64) into unstable

...@lists.alioth.debian.org Changed-By: Marco d'Itri m...@linux.it Description: libsystemd-dev - Dummy systemd utility library Changes: libsystemd-dummy (222-1) unstable; urgency=medium . * Now generated libsystemd-dev instead of libsystemd-daemon-dev. * sd-daemon.h updated to mimic the real

Accepted ladvd 1.1.1~pre1-1 (source i386) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 01 Aug 2015 15:53:26 +0200 Source: ladvd Binary: ladvd Architecture: source i386 Version: 1.1.1~pre1-1 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri m...@linux.it Changed-By: Marco d'Itri m...@linux.it

Accepted libnet-whois-ripe-perl 1.23-2 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 01 Aug 2015 17:43:35 +0200 Source: libnet-whois-ripe-perl Binary: libnet-whois-ripe-perl Architecture: source all Version: 1.23-2 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri m...@linux.it Changed-By: Marco

Accepted whois 5.2.10 (source i386) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 30 Jul 2015 03:26:56 +0200 Source: whois Binary: whois Architecture: source i386 Version: 5.2.10 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri m...@linux.it Changed-By: Marco d'Itri m...@linux.it Description

Re: Replacement Default Icons for Iceweasel [was Re: The Spirit of Free Software, or The Reality]

On Jul 19, Florian Weimer f...@deneb.enyo.de wrote: Thanks, I think that's an acceptable interim solution until we can obtain permission to ship the actual logos under terms we like. I think it's a crappy solution that makes Debian worse and solves no problem except DFSG-fetishism. -- ciao,

Accepted kmod 21-1 (source i386 all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 05 Jul 2015 21:18:24 +0200 Source: kmod Binary: kmod module-init-tools libkmod2 libkmod-dev libkmod2-udeb Architecture: source i386 all Version: 21-1 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri m...@linux.it

Re: The Spirit of Free Software, or The Reality

On Jul 16, Mike Hommey m...@glandium.org wrote: I, myself, find our DFSG-freeness pickiness going too far, and I'm sick of this icon thing. So, here's what I'm going to do: unless I hear non-IANAL objection until the next upstream release due on august 11 (and I'm BCCing the DPL in case he

Re: Bug#791857: ITP: daemonize -- tool to run a command as a daemon

On Jul 09, Martín Ferrari tin...@tincho.org wrote: I can say that it does: start-stop-daemon misses some functionality you need for programs that don't daemonise and log to stdout/stderr, which is something I needed only last week. Having said that, I think that This looks like a job for

Re: Proposal: enable stateless persistant network interface names

On Jun 26, Thomas Goirand z...@debian.org wrote: Actually it requires us to keep maintaining the Revert-udev-network-device-renaming patch as long as there will be systems with a 70-persistent-net.rules file renaming eth* to eth*. The other solution would be to upstream that patch (maybe

Re: Proposal v2: enable stateless persistant network interface names

On Jun 25, Martin Pitt mp...@debian.org wrote: Unlike /dev nodes, network interfaces can't have aliases as far as I know. Am I missing anything? No. As is usual with udev, the people who do not understand how it works are always ready to propose solutions. -- ciao, Marco pgp5RW1jnlifi.pgp

Re: Proposal v2: enable stateless persistant network interface names

On Jun 25, Marvin Renich m...@renich.org wrote: If the priority of the goals is realigned to make sense, then we must eliminate any solution that satisfies the no-state-file goal if it does not also satisfy the human-usable goal. If this brings us back to where we currently are, so be it.

Re: Adding support for LZIP to dpkg, using that instead of xz, archive wide

On Jun 15, Thomas Goirand z...@debian.org wrote: I'm not at a stage where I want to involve the CTTE right now. I still would prefer to gather opinions and see where it goes. My opinion is that you have not proved either that lz is widely used or that it is better than xz. -- ciao, Marco

Re: libre version of iceweasel

On Jun 09, Luke Kenneth Casson Leighton l...@lkcl.net wrote: open question: is there a perceived need to dig into the source code of firefox and, just as was done with google-chrome to create chromium-browser, permanently patch out certain features? No: I am a grown up and I can choose by

Accepted whois 5.2.9 (source i386) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 08 Jun 2015 02:18:47 +0200 Source: whois Binary: whois Architecture: source i386 Version: 5.2.9 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri m...@linux.it Changed-By: Marco d'Itri m...@linux.it Description

Re: Proposal v2: enable stateless persistant network interface names

On Jun 05, Milan P. Stanic m...@arvanta.net wrote: Now, USB Ethernet interface (usb) and bridge (br0) have the same MAC. This is not relevant, because virtual interfaces like br0 are not subject to renaming. -- ciao, Marco pgpfCA5WWp_SS.pgp Description: PGP signature

Re: Proposal v2: enable stateless persistant network interface names

On Jun 03, Vincent Danjean vdanjean...@free.fr wrote: stretch+1 (or maybe +2): - Check existance/non-emptiness of /etc/udev/rules.d/70-persistent-net.rules in udev.preinst, Show critical debconf note, and refuse to upgrade No. It is always a real pain when a preinst script

Re: Bug#786902: O: ifupdown -- high level tools to configure network interfaces

On May 30, Dmitry Smirnov only...@debian.org wrote: I'm not yet sure what can replace ifupdown in bonded NIC configurations with ifenslave... I am not sure about the obsolete bonding driver, but NM supports the new teaming driver. [1] systemd-networkd support is planned but not being

Re: Bug#786902: O: ifupdown -- high level tools to configure network interfaces

On May 27, Christoph Anton Mitterer cales...@scientia.net wrote: And I guess it's rather uncommon on Debian to use NM e.g. on server systems (probably also because most people wonder why they need a bloated daemon/etc. running just for a network that is brought up/down once every nnn days)

Re: Bug#786902: O: ifupdown -- high level tools to configure network interfaces

On May 27, Paul Wise p...@debian.org wrote: a featureful systemd-networkd. Will that make NetworkManager obsolete or will there be cases where it will still be needed? I am not sure that there is a clear plan about this: when this question was asked at FOSDEM the answer was a bit vague. :-)

Re: Bug#786902: O: ifupdown -- high level tools to configure network interfaces

On May 26, Andrew Shadura andre...@debian.org wrote: In current state ifupdown is probably good enough for what it is used for, except a few bugs. For advanced uses, it seems, Python-based ifupdown2 may become a good alternative in the future, and some simpler things wicd, NM and

Re: please use signed git commits (and tags)

On May 25, Samuel Thibault sthiba...@debian.org wrote: I use the attached script to easily create and sign my tags. Isn't this the equivalent of gbp-buildpackage --git-tag-only? Not everybody uses gbp. -- ciao, Marco pgp8bVvnDmsWf.pgp Description: PGP signature

Re: please use signed git commits (and tags)

On May 24, Thomas Koch tho...@koch.ro wrote: Git supports signing of commits since version 1.7.9. Everybody should sign git commits always. I do not see a significant benefit in signing all commits as long as release tags are signed. I use the attached script to easily create and sign my

Re: udev vs fuse: Transport endpoint is not connected

On May 18, Mathieu Malaterre ma...@debian.org wrote: Could a udev guru please comment on the (somewhat) famous issue `Transport endpoint is not connected` happening when a udev rule tries to mount fuse filesystem ? The only description I found of this issue I think that the fuse process is

Accepted whois 5.2.8 (source i386) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 18 May 2015 00:37:32 +0200 Source: whois Binary: whois Architecture: source i386 Version: 5.2.8 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri m...@linux.it Changed-By: Marco d'Itri m...@linux.it Description

Re: Proposal: enable stateless persistant network interface names

On May 13, D. Jared Dominguez jared_doming...@dell.com wrote: - it does not seem to me to provide any benefit over the firmware-based names since in practice both would use by default an interface index in the common case Firmware based in what sense? From the biosdevname readme,

Re: Proposal: enable stateless persistant network interface names

On May 11, Marvin Renich m...@renich.org wrote: I see a large enough consensus about switching by default to ifnames, and I believe that the few people who want MAC-based names for USB interfaces can easily set NamePolicy=mac or write a custom rule. Huh? This thread seems to have lots

Re: Proposal: enable stateless persistant network interface names

On May 11, Ben Hutchings b...@decadent.org.uk wrote: For ARM (and any other architecture using Device Tree) the on-board indices should be specified as aliases 'ethernet0', 'ethernet1', etc. Is this something that I can experiment on by patching just the device tree definition or does it

Re: Proposal: enable stateless persistant network interface names

On May 08, Martin Pitt mp...@debian.org wrote: I propose to retire [mac], i. e. drop /lib/udev/rules.d/75-persistent-net-generator.rules and enable [ifnames] by default. I see a large enough consensus about switching by default to ifnames, and I believe that the few people who want MAC-based

Re: Proposal: enable stateless persistant network interface names

On May 08, Marc Haber mh+debian-de...@zugschlus.de wrote: That would mean changing local code to _both_ handle en* and eth*, which is (a) a surprise and (b) unsatisfying in _my_ personal opinion. I'd rather have it fully and consistently or not at all. Not at all is going to be harder and

Re: Q: why binary-log by systemd-journald is not enabled by default?

On May 09, Stefano Zacchiroli z...@debian.org wrote: significant (and it will spread to other places, e.g., backups). No matter how journald will be integrated more tightly in Debian, can we haz a saner default? I agree: free disk space may not be free even when nothing else uses it, e.g.

Re: Packages to install be default for Stretch

On May 05, Ansgar Burchardt ans...@debian.org wrote: I would like to re-evaluate what we change by default for Stretch, that Me too. Let's look at the problem from a different point of view. This is what I remove when building cloud images for my employer's infrastructure: dpkg --purge \

Re: Packages to install be default for Stretch

On May 06, Josh Triplett j...@joshtriplett.org wrote: That said, as mentioned in my response, I think rsyslog ought to stay important until something else replaces it. Logging of *some* kind is important. We have journald. :-) Why, when it's just an apt install at away? It's one more

Re: Packages to install be default for Stretch

On May 06, Ansgar Burchardt ans...@debian.org wrote: But is this enough reason to keep w3m at priority standard? Personally I would rather use ssh -D or such than bothering with a rather limited text-mode browser. Agreed. -- ciao, Marco pgppFLgum_uM8.pgp Description: PGP signature

Re: Packages to install be default for Stretch

On May 06, Ansgar Burchardt ans...@debian.org wrote: Note that I believe this has changed over time: with the advent of VMs and containers the expectations what a system should minimally provide have become smaller. The differences between VMs and normal servers are very small, limited only

Re: Packages to install be default for Stretch

On May 06, Neil Williams codeh...@debian.org wrote: So, no, there isn't something broken - the uploader needs to file the bug as set out in the developer reference. And please have this fixed in stable as well. -- ciao, Marco pgp6i77j5JMCo.pgp Description: PGP signature

Re: Half-cycle

On May 04, mudongliang mudonglianga...@hotmail.com wrote: I fear that such a short release cycle would strongly disincentive many commercial vendors from supporting Debian systems: it already happened to Fedora. Can you give the detailed problem that happened to Fedora? Too many

Re: Half-cycle

On May 04, Marc Haber mh+debian-de...@zugschlus.de wrote: Too many releases, no more Plesk. Is not having P(l)est really a bad thing? If you sell servers or hosting and want to have customers, then yes. (Also, customers would not care less if the servers came with Centos installed so only

Re: Half-cycle

On May 02, Dimitri John Ledkov x...@debian.org wrote: Could we: Freeze in 6-8 months Release in 10-12 months I fear that such a short release cycle would strongly disincentive many commercial vendors from supporting Debian systems: it already happened to Fedora. There is also the problem

Re: upgrading to jessie on container with old kernel

On May 02, Brian May br...@microcomaustralia.com.au wrote: If I upgrade a Jessie openvz container on my proxmox box, systemd fails to start up. This is no surprise, the kernel seems to be rather old: Indeed. Did you check if a newer PVE kernel maybe has a backport of the features needed to use

Re: DUCC-IT 2015 a Milano: deadline per pasti e magliette

On Apr 15, Elena ``of Valhalla'' valha...@trueelena.org wrote: Si avvicina la data della DUCC-IT 2015 e con essa un po' di deadline. Potete iniziare a pubblicare una bozza di programma, in particolare con gli orari di inizio/fine di tutte le giornate? Il wiki dice ancora forse anche Domenica

Accepted tin 1:2.3.1-1 (source i386) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 27 Mar 2015 06:36:17 +0100 Source: tin Binary: tin Architecture: source i386 Version: 1:2.3.1-1 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri m...@linux.it Changed-By: Marco d'Itri m...@linux.it Description

Accepted whois 5.2.7 (source i386) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 25 Mar 2015 23:04:44 +0100 Source: whois Binary: whois Architecture: source i386 Version: 5.2.7 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri m...@linux.it Changed-By: Marco d'Itri m...@linux.it Description

Accepted whois 5.2.6 (source i386) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 23 Mar 2015 04:28:39 +0100 Source: whois Binary: whois Architecture: source i386 Version: 5.2.6 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri m...@linux.it Changed-By: Marco d'Itri m...@linux.it Description

Accepted ladvd 1.1.0-1 (source i386) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 20 Mar 2015 15:23:54 +0100 Source: ladvd Binary: ladvd Architecture: source i386 Version: 1.1.0-1 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri m...@linux.it Changed-By: Marco d'Itri m...@linux.it Description

Accepted kmod 20-1 (source i386 all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 08 Mar 2015 19:10:08 +0100 Source: kmod Binary: kmod module-init-tools libkmod2 libkmod-dev libkmod2-udeb Architecture: source i386 all Version: 20-1 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri m...@linux.it

Accepted libberkeleydb-perl 0.55-1 (source i386) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 08 Mar 2015 18:56:14 +0100 Source: libberkeleydb-perl Binary: libberkeleydb-perl Architecture: source i386 Version: 0.55-1 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri m...@linux.it Changed-By: Marco d'Itri m

Accepted whois 5.2.5 (source i386) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 03 Mar 2015 02:15:57 +0100 Source: whois Binary: whois Architecture: source i386 Version: 5.2.5 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri m...@linux.it Changed-By: Marco d'Itri m...@linux.it Description

Re: how to remove libsystemd0 from a live-running debian desktop system

On Feb 18, Simon Richter s...@debian.org wrote: With my embedded hat on, it would be nice if there was an easy way to drop this extra dependency, as it means a lot of essentially dead code loaded on systems that don't use systemd. http://anonscm.debian.org/cgit/users/md/libsystemd-dummy.git/

Re: how to remove libsystemd0 from a live-running debian desktop system

On Feb 16, Alastair McKinstry alastair.mckins...@sceal.ie wrote: The breakage of compatibility of existing systems (e.g. with /usr on a separate partition) has left a sour taste. I spent a weekend repairing systemd introduces no such breakage. Also, /usr on a separate partition was partially

Re: how to remove libsystemd0 from a live-running debian desktop system

On Feb 16, Luke Kenneth Casson Leighton l...@lkcl.net wrote: to debian-users: you don't have complete choice (yet), but i have demonstrated with a few hours work that there is a way to run (certain) desktop environments without requiring libsystemd0 or any of its dependencies, and after a

Accepted inn2 2.5.4-3 (source i386) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 15 Feb 2015 20:37:37 +0100 Source: inn2 Binary: inn2 inn2-lfs inn2-inews inn2-dev Architecture: source i386 Version: 2.5.4-3 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri m...@linux.it Changed-By: Marco d'Itri

Accepted whois 5.2.4 (source i386) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 25 Jan 2015 04:07:20 +0100 Source: whois Binary: whois Architecture: source i386 Version: 5.2.4 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri m...@linux.it Changed-By: Marco d'Itri m...@linux.it Description

Re: length of a package extended description

On Jan 09, Vincent Lefevre vinc...@vinc17.net wrote: Shouldn't the length be limited by the Debian policy? Shouldn't the length be limited by common sense? In this case I think that listing the packages without the description of each one would be enough... -- ciao, Marco pgpbuMAQ6Ch9n.pgp

Accepted whois 5.2.4~bpo70+1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 09 Jan 2015 03:50:55 +0100 Source: whois Binary: whois Architecture: source amd64 Version: 5.2.4~bpo70+1 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri m...@linux.it Changed-By: Marco d'Itri m...@linux.it

Accepted whois 5.2.3 (source i386) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 26 Dec 2014 20:12:24 +0100 Source: whois Binary: whois Architecture: source i386 Version: 5.2.3 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri m...@linux.it Changed-By: Marco d'Itri m...@linux.it Description

Re: one package altering other package's postrm

On Dec 13, Alexandre Detiste alexandre.deti...@gmail.com wrote: Would it be OK / ugly / forbiden to do a rm -f /var/lib/dpkg/info/cron.postrm in systemd-cron preinst script ? Ugly, but sometimes there is no other option. I am quite sure that I had to do this once or twice in my packages and

Re: Technical committee acting in gross violation of the Debian constitution

On Dec 04, Matthias Urlichs matth...@urlichs.de wrote: If you can run a CGI inside a chroot/container/whatever, you can run a small web server on a local port / Unix socket, and reverse-proxy it, just as easily. While using many more times the resources. You obviously have no idea of the

Re: Technical committee acting in gross violation of the Debian constitution

On Dec 04, Christoph Anton Mitterer cales...@scientia.net wrote: While using many more times the resources. You obviously have no idea of the challenges of providing secure web hosting for non-trivial quantities of web sites. So what do you want to imply would be secure? The point is not

Re: Summary:Re: Bug#762194: Proposal for upgrades to jessie

On Nov 28, Svante Signell svante.sign...@gmail.com wrote: a) Upgrades should _not_ change init: whatever is installed should be kept. I disagree: upgrades should get the default init system unless the system administrator chooses otherwise. b) New installs should get systemd-sysv as default

Re: Summary:Re: Bug#762194: Proposal for upgrades to jessie

On Nov 28, Simon Richter s...@debian.org wrote: I disagree: This is not safe and can break systems. Everything is not safe and can break systems, so this is not a very compelling argument. I have a system where the network connection is so important that the pppd is invoked via the inittab,

Re: enforced systemd services (was: Misc Developer News (#37))

On Nov 25, Arturo Borrero Gonzalez arturo.borrero.g...@gmail.com wrote: Is there a Debian-specific policy on how to apply these directives? We are working on one, but the general idea is please enable as many security features as feasible. :-) -- ciao, Marco pgpfFub5bB57R.pgp Description:

Re: Bug#769907: general: non-sysvinit init systems are made of fail

On Nov 20, Sam Hartman hartm...@debian.org wrote: The first issue (fstab now fatally blocks boot) is something the systemd maintainers have considered (as I understand it) and rejected. The behaviour of systemd will not be changed, but I have plans to add a fstab sanity check to preinst. --

Re: policy regarding redistributable binary files in upstream tarballs

On Nov 19, Salvo Tomaselli tipos...@tiscali.it wrote: Should the upstream tarball be repackaged to remove them, or not? They do not need to be removed at least if they can be rebuilt from the source in the package (but they do not have to). -- ciao, Marco pgpY1j9xGsHSF.pgp Description: PGP

Re: Being part of a community and behaving

On Nov 17, Steve Langasek vor...@debian.org wrote: This is what many still (retorically) wonder about: we the systemd maintainers did not reject that change, https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=15;bug=746578 Please try to be less selective in your quoting: the issue was

Re: Being part of a community and behaving

On Nov 16, Theodore Ts'o ty...@mit.edu wrote: I was really confused that this needed to go to the TC; from what I could tell, it had no downside systems using systemd, and it made things better on non-systemd systems. What was the downside of making the change, and why did it have to go to

Re: RFC: DEP-14: Recommended layout for Git packaging repositories

On Nov 14, Raphael Hertzog hert...@debian.org wrote: This is just a proof that storing the patches as real commits is useful. And that's the point of the patch-queue tag. Instead of having the patches only as real commits in the local repository, they get pushed to the public repository too

<    1   2   3   4   5   6   7   8   9   10   >