Hello Debian Developers,
I'm packaging new version of inadyn package [1]. inadyn can run as daemon,
therefore I created init.d script. Daemon supports dropping its privileges
on start as well. I chose inadyn for the user name and inadyn for the group
name with dynamically allocated system IDs.
Package: wnpp
Severity: wishlist
Owner: Vincent Danjean
* Package name: owfs
Version : 2.8p4
Upstream Author : Paul H Allfille
* URL : http://owfs.org
* License : GPL-2, LGPL-2, BSD (depending on components)
Programming Lang: C, C++, C#, Perl, Python, java, r
ilt fine)
This is using Ubuntu's .tar.bz2 chroots as downloaded from Launchpad
and a moderately configured sbuild 0.60.5-1ubuntu2; maybe your chroot
is constructed in a specific way? If you have notes on how you create
your chroots, these would be interesting
--
Loïc Minier
apport_1.16
On Tue, Dec 07, 2010, Loïc Minier wrote:
> The apport failure as bugged me for a while, I tried to reproduce it
> multiple times in the past and even just understanding the failure from
> the source and error message, but couldn't figure it out in the past;
Maybe the difference is in the order
On 07/12/10 at 13:17 +0100, Loïc Minier wrote:
> On Tue, Dec 07, 2010, Loïc Minier wrote:
> > The apport failure as bugged me for a while, I tried to reproduce it
> > multiple times in the past and even just understanding the failure from
> > the source and error message, but couldn't figure it
On Tue, Dec 07, 2010, Lucas Nussbaum wrote:
> Are you building on ext3 or ext4?
ext4
--
Loïc Minier
--
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/20101207131552.
On 07/12/10 at 14:15 +0100, Loïc Minier wrote:
> On Tue, Dec 07, 2010, Lucas Nussbaum wrote:
> > Are you building on ext3 or ext4?
>
> ext4
I could reproduce the failure in a clean chroot generated with
debootstrap --variant=buildd. on IRC, Michael Bienia also said that he
was able to reproduce
On 2010-12-04 12:02, Michael Tautschnig wrote:
Hi Alastair,
I'm by no means a bsd expert and you actually might want to redirect your
question to debian-...@l.d.o instead.
I've a strange issue: I've a perfectly ordinary package, cmor, which fails to
build on s390 and kfreebsd-amd64. In both c
(I'm not subscribed to this list, please CC me on replies.)
I have recently written a tool I call "apt-diff" to compare filesystem
content against APT. It is intended for investigating problems where
packaged files get modified/deleted after installing them from APT
(e.g., by user customization, a
Hello,
> I also
> find it useful for figuring out what customizations I have made to my
> system after I have forgotten about them.
how does it deal with configurations generated in postinstall?
Bye
--
Salvo Tomaselli
signature.asc
Description: This is a digitally signed message part.
> how does it deal with configurations generated in postinstall?
Only files shipped by a package (i.e., appear in its .list file) can be
diff'ed, so if a configuration file was generated from scratch in a
postinst then apt-diff can't show a diff for it. But it does keep track
of how many files it
Tristan Schmelcher writes:
>> how does it deal with configurations generated in postinstall?
>
> Only files shipped by a package (i.e., appear in its .list file) can be
> diff'ed, so if a configuration file was generated from scratch in a
> postinst then apt-diff can't show a diff for it. But it
On 07/12/10 at 17:45 -0800, Tristan Schmelcher wrote:
> (I'm not subscribed to this list, please CC me on replies.)
>
> I have recently written a tool I call "apt-diff" to compare filesystem
> content against APT. It is intended for investigating problems where
> packaged files get modified/delete
13 matches
Mail list logo
