Re: Seeking consensus for some changes in adduser

On 2022-03-09 21:00:20, Marc Haber wrote: On Wed, 9 Mar 2022 14:10:04 +0100, Harald Dunkel Related question: How are naming collisions between local entries and the entries in a network directory service supposed to be handled? Something like passwd: files sss in /etc/nsswitch.conf

Re: Seeking consensus for some changes in adduser

On 2022-03-08 17:49:04, Marc Haber wrote: (1a) would it be necessary to handle --system accounts differently? I think yes. I think it would be helpful to define "system account" and "normal user". Neither adduser(8) nor useradd(8) provide a sufficient definition, especially wrt the

please document why a package has been dropped from Testing/Bullseye

Hi folks, https://packages.debian.org/search?keywords=rsnapshot doesn't tell, so I wonder what is the recommended way to find out why rsnapshot (or any other package) has been dropped from Testing? rsnapshot is still in Sid. I found #986709, of course, but this information should be much easier

Re: freeipa is in trouble for the next release (again)

On 3/24/21 2:49 PM, Andrey Rahmatullin wrote: On Wed, Mar 24, 2021 at 12:33:53PM +0100, Harald Dunkel wrote: So what would be your suggestion? If you are still asking about getting this package into bullseye then I'm afraid it's not possible. Otherwise, as already suggested, it's possible

Re: freeipa is in trouble for the next release (again)

On 3/24/21 11:05 AM, Andrey Rahmatullin wrote: On Wed, Mar 24, 2021 at 10:02:37AM +0100, Harald Dunkel wrote: For my own part, I run freeipa-server on CentOS 7. I am not affected by #970880. I would be very happy with freeipa-client in Bullseye, even if freeipa-server doesn't make

freeipa is in trouble for the next release (again)

Hi folks, I understand that freeipa-server has a very serious problem (#970880), making it unfit for Bullseye. It is *highly* painful that it puts freeipa-client at risk for the next release, too. We had something similar for Buster about 2 years ago, AFAIR. For my own part, I run

how to ignore signed kernel packages and use the unsigned instead?

Hi folks, I would like to install the unsigned kernel packages instead of the signed ones, but using linux-headers-amd64 and linux-image-amd64 I have to wait for a signature being applied. Obviously the signed kernel image and header packages for amd64 rely upon information not being publicly

Re: f...@packages.debian.org Re: moving mg from salsa to github?

On 2/15/20 10:03 PM, Bernd Zeimetz wrote: So far I did not find a single upstream that was not able to understand a sentence like "Hi, my name is foo and I'm the Debian developer who is maintaining blubb in Debian". Thats correct. The maintainer for mg attached a new label 20200215 without

Re: moving mg from salsa to github?

Hi Marco, On 2020-02-15 20:44, Marco d'Itri wrote: On Feb 15, Harald Dunkel wrote: I am maintainer for mg, currently on salsa. Problem is, upstream doesn't release tar balls anymore, but moved the code to github. I plan to do something like this for ppp, which now has a proper upstream git

Re: moving mg from salsa to github?

On 2/15/20 2:44 PM, Peter Silva wrote: fwiw, looking at the repo on github.  There are tags.  They're just dates, Ideally one would get an idea of what the tags are from upstream, but you could just git clone using a tag. Also github allows you to easily get a tarball given a tag: wget

moving mg from salsa to github?

Hi folks, I am maintainer for mg, currently on salsa. Problem is, upstream doesn't release tar balls anymore, but moved the code to github. No tags. How can I tell Salsa? Should I drop the upstream and pristine-tar branches on Salsa and integrate the repository on github? Would you suggest to

bitte ueberprueft die Energy settings unter Linux

Hi folks, bitte ueberprueft die Power Management Settungs (Energy) auf Eurem Linux Host. Die dpcls sollten *nicht* automatisch ausgehen, sonst ist remote management nicht moeglich. Vielen Dank Harri

Re: Debian vs Linux namespaces

On 3/25/19 11:41 AM, Florian Lohoff wrote: Hi, On Sat, Mar 23, 2019 at 01:34:34PM +0100, Harald Dunkel wrote: Hi folks, AFAICS there are several packages that appear to be unaware of / do not care about containers, e.g. opensmtpd, bind9, apt-cacher-ng, probably everything using pidof

Re: Debian vs Linux namespaces

Hi Ondřej, On 3/23/19 2:26 PM, Ondřej Surý wrote: > Hi Harald, > > since you are using non-default init system, I would recommend sending > patches along with your bug reports if you want to get niche things fixed. > I already did. See the bug reports for lsb and opensmtpd. I stumbled over

Debian vs Linux namespaces

Hi folks, AFAICS there are several packages that appear to be unaware of / do not care about containers, e.g. opensmtpd, bind9, apt-cacher-ng, probably everything using pidof or pidofproc from /lib/lsb/init-\ functions). I noticed that containerization and Linux namespaces are not number one

Accepted network-manager-strongswan 1.4.4-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 03 Oct 2018 11:33:28 +0200 Source: network-manager-strongswan Binary: network-manager-strongswan Architecture: source Version: 1.4.4-2 Distribution: unstable Urgency: medium Maintainer: Harald Dunkel Changed-By: Harald Dunkel

libcurl3 vs libcurl4

Hi folks, maybe a stupid question, but how comes libcurl4 doesn't provide a new soname, making it possible to install both libcurl3 and libcurl4 in parallel? Would it be possible for libcurl4 to provide libcurl3 to avoid the conflict? Regards Harri

Accepted network-manager-strongswan 1.4.4-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 10 May 2018 18:55:05 +0200 Source: network-manager-strongswan Binary: network-manager-strongswan Architecture: source Version: 1.4.4-1 Distribution: unstable Urgency: medium Maintainer: Harald Dunkel <ha...@afaics.de> C

Accepted network-manager-strongswan 1.4.3-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 30 Apr 2018 16:44:16 +0200 Source: network-manager-strongswan Binary: network-manager-strongswan Architecture: source Version: 1.4.3-2 Distribution: unstable Urgency: medium Maintainer: Harald Dunkel <ha...@afaics.de> C

Accepted network-manager-strongswan 1.4.2-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 27 Jan 2018 06:08:36 +0100 Source: network-manager-strongswan Binary: network-manager-strongswan Architecture: source Version: 1.4.2-2 Distribution: unstable Urgency: medium Maintainer: Harald Dunkel <ha...@afaics.de> C

Accepted mg 20171014-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 14 Oct 2017 21:22:19 +0200 Source: mg Binary: mg Architecture: source Version: 20171014-1 Distribution: unstable Urgency: medium Maintainer: Harald Dunkel <ha...@afaics.de> Changed-By: Harald Dunkel <ha...@

Accepted mg 20170828-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 05 Sep 2017 00:41:48 +0200 Source: mg Binary: mg Architecture: source Version: 20170828-2 Distribution: unstable Urgency: medium Maintainer: Harald Dunkel <ha...@afaics.de> Changed-By: Harald Dunkel <ha...@

Accepted mg 20170828-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 30 Aug 2017 06:48:53 +0200 Source: mg Binary: mg Architecture: source Version: 20170828-1 Distribution: unstable Urgency: medium Maintainer: Harald Dunkel <ha...@afaics.de> Changed-By: Harald Dunkel <ha...@

Accepted network-manager-strongswan 1.4.2-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 25 Jun 2017 12:36:31 +0200 Source: network-manager-strongswan Binary: network-manager-strongswan Architecture: source Version: 1.4.2-1 Distribution: unstable Urgency: medium Maintainer: Harald Dunkel <ha...@afaics.de> C

Re: Naming of network devices - how to improve it in buster

On Tue, 11 Jul 2017 15:20:41 +0200 Michael Biebl wrote: > Am 11.07.2017 um 12:14 schrieb Guus Sliepen: > > Ok, it should be clear now that the new way of naming interfaces is not > > ideal, but the older ways weren't either. Let's have a look at what we > > want: > > > > - A

Re: Naming of network devices - how to improve it in buster

On Tue, 11 Jul 2017 12:14:59 +0200 Guus Sliepen wrote: > > So, what can we do to improve the situation and get the best of both > worlds? > systemd.link(5) describes a NamePolicy option for interface names. I would suggest to introduce a new policy "keep" to stick with the

Accepted mg 20170401-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 05 Apr 2017 11:26:46 +0200 Source: mg Binary: mg Architecture: source Version: 20170401-1 Distribution: unstable Urgency: medium Maintainer: Harald Dunkel <ha...@afaics.de> Changed-By: Harald Dunkel <ha...@

can't push new version to collab-maint

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi folks, trying to push a new version of mg to collab-maint I get an error message "unable to update info/refs+" {harri@cecil:mg (pristine-tar) 588} git push Counting objects: 4, done. Delta compression using up to 8 threads. Compressing

Accepted network-manager-strongswan 1.4.1-1 (amd64 source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 22 Oct 2016 14:25:40 +0200 Source: network-manager-strongswan Binary: network-manager-strongswan Architecture: amd64 source Version: 1.4.1-1 Distribution: unstable Urgency: medium Maintainer: Harald Dunkel <ha...@afaics

Re: kurze downtime der jenkins server um 12:00

Sorry for the noise, that was a bad To: address. Regards Harri On 10/18/2016 09:14 AM, Harald Dunkel wrote: > Hi folks, > > zur RAM Erweiterung gibt es heute um 12:00 eine kurze Downtime > der Jenkins Server > > invde8i001 > mbrjenkins01 > nvode

kurze downtime der jenkins server um 12:00

Hi folks, zur RAM Erweiterung gibt es heute um 12:00 eine kurze Downtime der Jenkins Server invde8i001 mbrjenkins01 nvode7i001 semde7i001 sprjenkins01 Regards Harri

Accepted network-manager-strongswan 1.4.0-1 (amd64 source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 19 Sep 2016 09:42:42 +0200 Source: network-manager-strongswan Binary: network-manager-strongswan Architecture: amd64 source Version: 1.4.0-1 Distribution: unstable Urgency: medium Maintainer: Harald Dunkel <ha...@afaics

Accepted network-manager-strongswan 1.3.1-2 (amd64 source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 28 Aug 2016 09:47:28 +0100 Source: network-manager-strongswan Binary: network-manager-strongswan Architecture: amd64 source Version: 1.3.1-2 Distribution: unstable Urgency: medium Maintainer: Harald Dunkel <ha...@afaics

Re: howto avoid "apt-get update" going guru?

Hi Martin, On 07/05/16 10:09, Martin Bagge / brother wrote: > On 2016-07-05 06:32, Harald Dunkel wrote: >> >> I didn't mention klecker-ftp anywhere in my config files. >> Its not on the round-robin list for ftp.debian.org either: >> >> # host ftp.debian.

Re: howto avoid "apt-get update" going guru?

On 07/05/16 06:32, Harald Dunkel wrote: > Hi folks, > > this morning I found "apt-get update" getting stuck due to an > unresponsive host: > Sorry, this was supposed to go to debian-user. Regards Harri

howto avoid "apt-get update" going guru?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi folks, this morning I found "apt-get update" getting stuck due to an unresponsive host: # cat /etc/apt/sources.list deb http://ftp.debian.org/debian sid main contrib non-free deb-src http://ftp.debian.org/debian sid main contrib non-free #

Accepted mg 20160118-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 08 Feb 2016 12:37:58 +0100 Source: mg Binary: mg Architecture: source Version: 20160118-2 Distribution: unstable Urgency: medium Maintainer: Harald Dunkel <ha...@afaics.de> Changed-By: Harald Dunkel <ha...@

Accepted mg 20160118-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 30 Jan 2016 11:01:58 +0100 Source: mg Binary: mg Architecture: source Version: 20160118-1 Distribution: unstable Urgency: medium Maintainer: Harald Dunkel <ha...@afaics.de> Changed-By: Harald Dunkel <ha...@

Re: debian/control: enhanced version dependencies?

Hi folks, On 01/15/2016 05:07 PM, Johannes Schauer wrote: > > Whenever discussions about new dependency syntax come up I like to remind > people of all the time (about six years now) and effort it took to get the > build profile syntax [1] accepted by the archive, supported by all tools and >

Re: debian/control: enhanced version dependencies?

On 01/14/2016 10:11 AM, Andrey Rahmatullin wrote: > On Thu, Jan 14, 2016 at 09:35:31AM +0100, Harald Dunkel wrote: >> For running a local set of meta packages I would like to >> express package dependencies depending upon other packages >> installed, e.g. >> >

debian/control: enhanced version dependencies?

Hi folks, For running a local set of meta packages I would like to express package dependencies depending upon other packages installed, e.g. Package: xyz Version: all Depends: ${misc:Depends} , dbus (systemd >= 215) Hopefully you get the meaning. Package xyz could make sure that dbus

iscsi support in Jessie

Hi folks, Some years ago I have setup an iscsi target using targetcli 2.0 on Wheezy. Actually it works pretty well, but there were some serious upgrade problems to 2.1 and 3.0, making targetcli go away for Jessie :-(. See #764005 and #751226. I lost confident in a newer version. Now I have to

Accepted network-manager-strongswan 1.3.1-1 (i386 source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 11 Sep 2015 07:48:41 +0200 Source: network-manager-strongswan Binary: network-manager-strongswan Architecture: i386 source Version: 1.3.1-1 Distribution: sid Urgency: low Maintainer: Harald Dunkel <ha...@afaics.de> C

Re: DEB_SIGN_KEYID vs DEBSIGN_KEYID

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/08/15 18:48, Guido Günther wrote: On Sun, Jun 07, 2015 at 10:36:41AM +0200, Harald Dunkel wrote: Hi folks, Trying to get rid of my old GPG key I stumbled over this: For devscripts you can define a variable DEBSIGN_KEYID. For dpkg

DEB_SIGN_KEYID vs DEBSIGN_KEYID

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi folks, Trying to get rid of my old GPG key I stumbled over this: For devscripts you can define a variable DEBSIGN_KEYID. For dpkg it is called DEB_SIGN_KEYID. git-buildpackage doesn't support a keyid environment variable at all, as it seems.

Re: conflicts between Debian's and upstream's Debian package

Hi Andreas, On 02/20/15 18:54, Andreas Tille wrote: Hi Harald, Is there any reason why you do not even now are talking about package name and upstream URL featuring the same name? Its not fruitful to leave your discussion partners in the dark. Sorry, but I don't want to blame anybody

Re: conflicts between Debian's and upstream's Debian package

On 02/24/15 15:09, Harald Dunkel wrote: Sorry, but I don't want to blame anybody producing bad packages. It shouldn't matter here. Should be: Sorry, but I don't want to blame anybody to produce bad packages. Name and upstream URL shouldn't matter here. Sorry for my bad English. Regards

Accepted network-manager-strongswan 1.3.0-2 (i386 source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 17 Feb 2015 13:24:00 +0100 Source: network-manager-strongswan Binary: network-manager-strongswan Architecture: i386 source Version: 1.3.0-2 Distribution: unstable Urgency: medium Maintainer: Harald Dunkel ha...@afaics.de

conflicts between Debian's and upstream's Debian package

Hi folks, I would like to use upstream's Debian/Ubuntu packages for a certain tool 'foo'. Its closer to what I need, and I don't have migrate between both versions before asking the mailing list for help or for reporting/fixing problems. Problem: The Debian maintainer messed up the version

Re: conflicts between Debian's and upstream's Debian package

Hi Daniel, On 02/20/15 13:09, Daniel Leidert wrote: Just to understand your problem: there is a package foo. Debian provides it with version 1:A-B and upstream provides some self-compiled packages with the same name under version C-D (and C-D 1:A-B) and you want to force apt to install the

Re: network-manager-strongswan kicked out from Jessie, even though there is a fix?

On 02/06/15 10:01, Dominique Dumont wrote: network-manager-strongswan is still in unstable and will be part of stretch once jessie is out and the RC bugs are fixed. Sorry, I thought it was kicked out completely. Your work is definitely not a waste of time: it can be used for stretch or

Re: network-manager-strongswan kicked out from Jessie, even though there is a fix?

On 02/05/15 16:58, Thibaut Paumard wrote: I understand that it can make you sad, especially since you missed the final deadline by only a few days, but you didn't waste your time: its too late for jessie, but you will be able to push your package into jessie-backports, once it is available,

Re: network-manager-strongswan kicked out from Jessie, even though there is a fix?

On 02/05/15 15:38, Dominique Dumont wrote: Sorry that's not possible: this package was removed from Jessie back in September. Freeze policy excludes package removed more than 1 week ago [1] Highly discouraging. Feels like I wasted my time. :-( -- To UNSUBSCRIBE, email to

Re: network-manager-strongswan kicked out from Jessie, even though there is a fix?

On 02/04/15 12:22, Dominique Dumont wrote: According to PTS [1], this package was kicked out because of a FTBS [2]. Is this bug fixed ? I have pushed a new version 1.3.0-1.3 to mentors, providing a workaround for #773764 as well.

Re: network-manager-strongswan kicked out from Jessie, even though there is a fix?

On 02/04/15 12:22, Dominique Dumont wrote: According to PTS [1], this package was kicked out because of a FTBS [2]. Is this bug fixed ? Sorry, I had built network-manager-strongswan on Wheezy to use it on Wheezy and Jessie. I didn't notice the FTBFS on sid. Building on Jessie I still get

network-manager-strongswan kicked out from Jessie, even though there is a fix?

Hi folks, Do you think it would it be possible to fix network-manager-strongswan for Jessie? Currently it seems it has been kicked out due to #773764, even though the report provides an easy fix to make it work at least for xfce4 and gnome on Jessie. I have pushed an NMU (1.3.0-1.2) to mentors

Re: question about versioned dependencies in debian/control

PS: The error message is: Setting up git-man (1:2.1.2-0~xgo70+1) ... dpkg: dependency problems prevent configuration of git: git depends on git-man ( 1:2.1.2); however: Version of git-man on system is 1:2.1.2-0~xgo70+1. Regards Harri -- To UNSUBSCRIBE, email to

question about versioned dependencies in debian/control

Hi folks, I am building local git packages for Wheezy derived from the official source package. Problem with debian/control: : Package: git Architecture: any Multi-Arch: foreign Depends: ${shlibs:Depends}, perl-modules, liberror-perl, git-man ( ${source:Upstream-Version}), git-man (

Re: question about versioned dependencies in debian/control

On 10/22/14 16:57, Simon McVittie wrote: 1:2.1.2-0~xgo70+1 is less than 1:2.1.2, because 1:2.1.2 is equal to 1:2.1.2-0 in version number order, and 0~x is less than 0. You can confirm this: % dpkg --compare-versions 2-0~x lt 2-0 echo yes yes I would suggest 1:2.1.2-0+xgo70+1

Re: [Pkg-swan-devel] say goodbye to network-manager-strongswan?

On 07/28/14 11:38, Yves-Alexis Perez wrote: I don't currently use the network-manager strongSwan plugin but that's mostly because it doesn't work. AFAICT it didn't work due to #741415. Today its broken again. It says Could not find VPN plugin service for

Accepted network-manager-strongswan 1.3.0-1.1 (source amd64)

Changed-By: Harald Dunkel hdun...@aixigo.de Description: network-manager-strongswan - network management framework (strongSwan plugin) Closes: 741415 Changes: network-manager-strongswan (1.3.0-1.1) unstable; urgency=low . * Non-maintainer upload. * use charon-nm instead of charon (Closes

Re: Transition plan for changing the default init system

On 07/16/14 23:22, Tollef Fog Heen wrote: So we are proposing the following scheme: a/ Upload a new init package. This is a new, essential package that will replace sysvinit as the package that ensures your system has an init system. We want to build this binary package from a package which

Re: nmudiff enhancements

Hi folks, On 07/17/14 03:16, Christian Hofstaedtler wrote: * Wookey woo...@wookware.org [140716 23:48]: I do think there is plenty more room for soialising more NMUing. There are piles of bugs in the archive that mostly just need uploading, and many packages with a backlog of minor bugs, or

Re: say goodbye to network-manager-strongswan?

On 07/16/14 17:56, Thomas Goirand wrote: To try to kill your frustration, I have sponsored the upload of your fix to the delayed/10 queue. If everything goes well, then in 15 days, network-manager-strongswan will be back in Jessie. Thanx very much for your help Regards Harri -- To

Re: say goodbye to network-manager-strongswan?

On 07/16/14 17:56, Thomas Goirand wrote: BTW, it feels weird that the package build-depends on debhelper when it really is using CDBS. The debian/copyright is also quite wrong, as it doesn't include the copyright notice for the GPL v2 (and I believe that's mandatory, right?). Not commenting

say goodbye to network-manager-strongswan?

Hi folks, how comes that network-manager-strongswan has been dropped from testing? This package is extremely important for road- warrior setups using IPsec. Regards Harri -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Re: say goodbye to network-manager-strongswan?

Hi Thijs, On 07/16/14 12:35, Thijs Kinkhorst wrote: As it turns out, this package got removed because it has an unfixed release critical bug (which interestingly enough you yourself reported). When this bug is fixed, the package will transition back to testing. Of course I know that I

Re: say goodbye to network-manager-strongswan?

Hi Simon, On 07/16/14 12:36, Simon McVittie wrote: If the change you proposed works correctly, an NMU seems appropriate. I am using the fix in a private package since I created the bug report. Seems to work fine (using strongswan 5.x). I have appended a diff to the bug report. Hope this

Re: say goodbye to network-manager-strongswan?

On 07/16/14 15:17, Holger Levsen wrote: Especially if the NMU is properly done (eg documented in the BTS, uploaded to DELAYED-foo, etc) I've hardly seen any complaints in recent years. Surely I could have done better in providing a clean fix to #741415, making it more easy for the Debian

new bug severity new upstream

Hi folks, would it be reasonable to introduce a new bug severity new upstream? Regards Harri -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:

download of source packages alarmed clamav

Hi folks, I am running a transparent http proxy integrated with clamav. Problem: If I run apt-get source pymilter, then I get # apt-get source pymilter Reading package lists... Done Building dependency tree Reading state information... Done NOTICE: 'pymilter' packaging is maintained in the 'Svn'

Re: download of source packages alarmed clamav

On Tue, 25 Jun 2013 10:46:23 +0300 Marius Gavrilescu mar...@ieval.ro wrote: That package contains a directory named test/ with emails with spam, viruses and similar. This might have caused the clamav warning. Its not a warning. The download failed. Regards Harri -- To UNSUBSCRIBE,

Re: download of source packages alarmed clamav

On Tue, 25 Jun 2013 10:54:53 +0300 Marius Gavrilescu mar...@ieval.ro wrote: On Tue, Jun 25, 2013 at 09:52:26AM +0200, Harald Dunkel wrote: Its not a warning. The download failed. Yes, I should have said failure. Anyway, the probable cause is the existence of emails with viruses as tests

question about Conflicts:

Hi folks, How can I tell a Debian package to conflict with a real package foo, but not with other packages providing foo? Regards Harri -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:

usb sata docking station: backup button?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi folks, Does anybody know some way to bind an action to the button most usb sata docking stations come with? Regards Harri -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux)

combined dependencies?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi folks, would it be possible to support combined dependencies, e.g. if package A and B are installed, then package C(A) has to be installed, too? That might be helpful for dkms packages, for example. A would be the kernel, B the dkms package, and

Re: combined dependencies?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Michael, On 08/20/11 08:55, Michael Tautschnig wrote: What event would induce installation of C(A)?! Let's assume neither A nor B are installed. apt-get install A (no point installing C(A)) apt-get install B (B does not depend on C(A),

how to divert /etc/profile?

Hi folks, I would like to install a private package diverting /etc/profile (to support /etc/profile.d). Problem: There is no owner for this file. What would you suggest? Any helpful comment would be highly appreciated. Harri -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org

Re: how to divert /etc/profile?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/04/11 12:32, Timo Weingärtner wrote: Hi Harald, Am Montag, 2011-07-04 schrieb Harald Dunkel: I would like to install a private package diverting /etc/profile (to support /etc/profile.d). Problem: There is no owner for this file. What

Re: distinguish between core and main?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/07/11 00:59, Russ Allbery wrote: Harald Dunkel ha...@afaics.de writes: Not exactly. I would like to get a stable build and runtime environment for the packages in main/testing. Yes, that's what I'm saying doesn't actually exist

Re: distinguish between core and main?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/10/11 07:24, Harald Dunkel wrote: I do not see that. All packages were available at build time in the right version. Where should this broken dependency come from, unless you are ignoring dependencies on promoting packages from unstable

Re: distinguish between core and main?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/06/11 07:06, Russ Allbery wrote: I still think this whole conversation is based on a false premise. I think the original request originated from a belief that there is some separable part of core Debian which could be held stable, and that

Re: distinguish between core and main?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Neil, On 06/04/11 19:01, Neil Williams wrote: Testing compatibility is the larger problem. Automated tests can only go so far. Dependencies are one thing, bugs which arise because one setup is using a version which has already been replaced

Re: distinguish between core and main?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/05/11 13:17, Tshepang Lekhonkhobe wrote: On Sun, 2011-06-05 at 08:29 +0200, Harald Dunkel wrote: Understood. If you reduce the number of packages to be released by focusing on a core package set with 1000 or 1500 packages instead of +3

Re: distinguish between core and main?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/04/11 07:56, Paul Wise wrote: Sounds like you are looking for backports.debian.org? Backports for Squeeze contains just about 400 package, AFIACS. Regards Harri -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment:

Re: distinguish between core and main?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/04/11 09:05, Paul Wise wrote: Alternatively you might want to install from testing directly. Not everything from testing is installable on stable, which is where backports comes in. Installing testing for the whole system is no option. The

Re: distinguish between core and main?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/04/11 07:26, Andrei POPESCU wrote: This is one of those recurrent discussions coming up on debian-devel. It is my impression (as a lurker) that most Debian Developers do not want to have second-class packages and it is a feature that all

Re: distinguish between core and main?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Neil, On 06/04/11 12:36, Neil Williams wrote: On Sat, 04 Jun 2011 10:12:42 +0200 Harald Dunkel ha...@afaics.de wrote: Installing testing for the whole system is no option. The base system (the core packages) should be provided by the most

distinguish between core and main?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi folks, Having 3+ packages within a single main repository is pretty bulky. Would it be possible to distinguish between the core Debian and main somehow? I don't want to keep anybody out. I just would like to use the core packages of Debian

Re: problem with /etc/kernel scripts

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Ben, On 03/31/11 15:22, Ben Hutchings wrote: On Thu, 2011-03-31 at 10:59 +0200, Harald Dunkel wrote: [...] Of course I understand that this is highly complex. Maybe it would help to introduce some scheme to register event handlers to run after

Re: problem with /etc/kernel scripts

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/21/11 14:22, Ben Hutchings wrote: On Mon, 2011-03-21 at 06:17 +0100, Harald Dunkel wrote: Do you think that dkms should drop its /etc/kernel/postinst.d/dkms script? AFAICS this script might be called before the headers are installed

problem with /etc/kernel scripts

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi folks, I am using upstream's build procedure for creating Linux kernel packages (make deb-pkg). For 2.6.38 it gives you these packages: linux-firmware-image_2.6.38-1_amd64.deb linux-headers-2.6.38_2.6.38-1_amd64.deb

Re: problem with /etc/kernel scripts

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/20/11 18:23, Ben Hutchings wrote: On Sun, 2011-03-20 at 16:49 +0100, Harald Dunkel wrote: Obviously the dkms script should not be run by the postinst script of linux-image, but of linux-headers. Shouldn't we distinguish between the hooks

many packages FTBFS, if $TAPE is set

Hi folks, Many packages FTBFS (silently!) if an environment variable TAPE is set. That happens if your rules script uses something like tar -c modules | bzip2 -9 omfs.tar.bz2 for example. If $TAPE is set, then tar writes to $TAPE instead of stdout (possibly corrupting the tape you had

Re: many packages FTBFS, if $TAPE is set

Hi Bas, You could write 'tar cfz file.tgz files' instead of 'tar -c -f file.tgz -z files'. Seems that looking for a missing '-f' or 'f' would be pretty error-prone and much more difficult than a simple test ! -s watchdog.tar after building the package. My point is: We need some central quality

Re: many packages FTBFS, if $TAPE is set

Hi Eduard, Eduard Bloch wrote: verify his/her own package. But in this case a central check would be cheap and easy to implement. Almost zero effort compared to the damage done by corrupting tapes. Oh, come on. People who put $TAPE into the default environment may also link /dev/null to

Mozilla plugins to depend upon virtual mozilla-plugin-browser?

Hi folks, Would it be possible that the Mozilla plugins depend upon a virtual mozilla-plugin-browser package? All browsers with the same plugin interface could provide this feature, and foreign browsers would not be kept out. Many thanx in advance Harri -- To UNSUBSCRIBE, email to [EMAIL

Accepted xrsh 5.92-8 (source all)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 18 Feb 2006 10:59:10 +0100 Source: xrsh Binary: xrsh Architecture: source all Version: 5.92-8 Distribution: unstable Urgency: low Maintainer: Marc 'HE' Brockschmidt [EMAIL PROTECTED] Changed-By: Harald Dunkel [EMAIL PROTECTED

Accepted blockade 20041028-9 (source powerpc)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 20 Jan 2006 07:26:58 +0100 Source: blockade Binary: blockade Architecture: source powerpc Version: 20041028-9 Distribution: unstable Urgency: low Maintainer: Marc 'HE' Brockschmidt [EMAIL PROTECTED] Changed-By: Harald Dunkel

Accepted blockade 20041028-7 (source powerpc)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 11 Oct 2005 19:57:34 +0200 Source: blockade Binary: blockade Architecture: source powerpc Version: 20041028-7 Distribution: unstable Urgency: low Maintainer: Harald Dunkel [EMAIL PROTECTED] Changed-By: Harald Dunkel [EMAIL

  1   2   >