On Fri, Sep 03, 2021 at 08:23:07AM -0400, Roberto C. Sánchez wrote:
As a Debian Developer, I would consider it bad form to go creating
things under /home from a package's maintainer script, though that does
not appear to be a specific policy violation.
I idly wonder whether it should be, althou
On Fri, Sep 03, 2021 at 03:41:00PM +0200, Harald Dunkel wrote:
> On 9/3/21 13:57, Roberto C. Sánchez wrote:
> > That sounds like potentially buggy behavior. Can you give a specific
> > example?
> >
>
> ntp (Debian)
> sane (Debian)
> gitlab-runner (not Debian)
> zabbix-age
On 9/3/21 13:57, Roberto C. Sánchez wrote:
That sounds like potentially buggy behavior. Can you give a specific
example?
ntp (Debian)
sane (Debian)
gitlab-runner (not Debian)
zabbix-agent (not Debian)
Apparently the postinst scripts of ntp and sane have been f
On 9/3/21 11:40, Erwan David wrote:
I would do this the other way (but not eay tpo migrate) : add your users
in another directory (/srv/home or something else) where you mpount your
remote home directory, and keep system using /home.
I agree, but unfortunately this is not an option.
Roberto C. Sánchez wrote:
> On Fri, Sep 03, 2021 at 08:03:23AM -0400, Greg Wooledge wrote:
>> Out of curiosity, I checked my system to see if there were any system
>> users with home directories under /home. The only one I found is "ntp".
>>
>> Then I looked at the ntp.postinst script, and it h
On Fri, Sep 03, 2021 at 08:39:09AM -0400, Roberto C. Sánchez wrote:
> So, the existence of /home/ntp on the OP's system, or any system
> installed from a Debian release prior to the last 4-ish years, could be
> attributed to some process or series of actions that decides, "hey, this
> ntp user's ho
On Fri, Sep 03, 2021 at 08:33:25AM -0400, Greg Wooledge wrote:
> On Fri, Sep 03, 2021 at 08:23:07AM -0400, Roberto C. Sánchez wrote:
> > On Fri, Sep 03, 2021 at 08:03:23AM -0400, Greg Wooledge wrote:
> > > Out of curiosity, I checked my system to see if there were any system
> > > users with home d
On Fri, Sep 03, 2021 at 08:23:07AM -0400, Roberto C. Sánchez wrote:
> On Fri, Sep 03, 2021 at 08:03:23AM -0400, Greg Wooledge wrote:
> > Out of curiosity, I checked my system to see if there were any system
> > users with home directories under /home. The only one I found is "ntp".
> How old is y
On Fri, Sep 03, 2021 at 08:03:23AM -0400, Greg Wooledge wrote:
> On Fri, Sep 03, 2021 at 07:57:44AM -0400, Roberto C. Sánchez wrote:
> > On Fri, Sep 03, 2021 at 11:14:45AM +0200, Harald Dunkel wrote:
> > > Hi folks,
> > >
> > > how can I tell the debhelper scr
On Fri, Sep 03, 2021 at 08:03:23AM -0400, Greg Wooledge wrote:
> On Fri, Sep 03, 2021 at 07:57:44AM -0400, Roberto C. Sánchez wrote:
> > On Fri, Sep 03, 2021 at 11:14:45AM +0200, Harald Dunkel wrote:
> > > Hi folks,
> > >
> > > how can I tell the debhelper scr
On Friday, September 03, 2021 05:40:18 AM Erwan David wrote:
> Le 03/09/2021 à 11:14, Harald Dunkel a écrit :
> > how can I tell the debhelper scripts to not install home directories
> > for system services in /home (managed on a remote host in my
> > environment), but to
On Fri, Sep 03, 2021 at 07:57:44AM -0400, Roberto C. Sánchez wrote:
> On Fri, Sep 03, 2021 at 11:14:45AM +0200, Harald Dunkel wrote:
> > Hi folks,
> >
> > how can I tell the debhelper scripts to not install home directories
> > for system services in /home (man
On Fri, Sep 03, 2021 at 11:14:45AM +0200, Harald Dunkel wrote:
> Hi folks,
>
> how can I tell the debhelper scripts to not install home directories
> for system services in /home (managed on a remote host in my environment),
> but to use /var/lib instead?
>
That sounds like
Le 03/09/2021 à 11:14, Harald Dunkel a écrit :
Hi folks,
how can I tell the debhelper scripts to not install home directories
for system services in /home (managed on a remote host in my environment),
but to use /var/lib instead?
I know I can block dpkg using apparmor, but this would break
Hi folks,
how can I tell the debhelper scripts to not install home directories
for system services in /home (managed on a remote host in my environment),
but to use /var/lib instead?
I know I can block dpkg using apparmor, but this would break many
postinst scripts, at least for 3rd-party
On Wed, 2015-01-07 at 11:19 -0800, Don Armstrong wrote:
> If you attach the actual rules file, then we might get to that answer.
>
> It's also possible that you didn't have debugging symbols included in
> the first place (-g).
It turns out I'm either blind, stupid, or probably both. The = was
act
On Wed, 07 Jan 2015, Kip Warner wrote:
> So back to my original question, why was it being ignored?
If you attach the actual rules file, then we might get to that answer.
It's also possible that you didn't have debugging symbols included in
the first place (-g).
[Furthermore, dh_strip always run
n I ask is dh_make had actually created the
original template debian/rules using the debhelper 7 syntax and that was
what was in it.
> Finally, your debian/rules is missing a #!/usr/bin/make -f, which means
> that it isn't going to work at all.
Another pastebin copy / paste typo. It
On Tue, 06 Jan 2015, Kip Warner wrote:
> I am trying to debianize a personal package for native compilation. I
> packaged it using the debhelper 7 syntax as aided with dh_make.
>
> After customizing my debian/* metadata and scripts, I noticed that
> dh_strip is still stripping de
Hey list,
I am trying to debianize a personal package for native compilation. I
packaged it using the debhelper 7 syntax as aided with dh_make.
After customizing my debian/* metadata and scripts, I noticed that
dh_strip is still stripping debugging symbols from my executable, even
though debian
On Tue, May 31, 2005 at 03:57:59AM +1000, Stephen Grant Brown wrote:
> Hi All,
>
> I have debhelper 4.0.2 installed. How do I download and install debhelper >=
> 4,1,46 without going from the stable distributon of Debian Linux?
>
> Thanks in advance for your help.
>
>
Hi All,
I have debhelper 4.0.2 installed. How do I download and install debhelper >=
4,1,46 without going from the stable distributon of Debian Linux?
Thanks in advance for your help.
Stephen Grant Brown
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe&q
El jueves, 14 de agosto de 2003, a las 18:23, Bob Proulx escribe:
> So if I modify the control file such as to reduce the debhelper
> version dependency then I also modify the version number.
>
> [...]
>
> Really any valid methodology would work. Something like this would
"dependencies loop",
> specially debhelper.
>
> The source for debhelper 4.1.52 can be compiled, but not installed, as
> it depends on debconf-utils at least 1.1.1. Version 1.2.35 is available,
> but for building, it depends on debhelper at least 4.1.27, that
> obviously
El sábado, 16 de agosto de 2003, a las 13:47, Travis Crump escribe:
> Wouldn't it be a bug in the package if it build-depended on debhelper 4,
> but didn't actually use any features not available in debhelper 3
I suppose that, of course it would. But filing bugs is free (as in
be
El domingo, 17 de agosto de 2003, a las 02:45, Rob Weir escribe:
> There's a backport of debhelper 4.1.56 available from here:
>
> deb http://people.debian.org/~aurel32/BACKPORTS stable main
Thanks a lot. I will be trying it soon.
> Make sure you check www.apt-get.org to se
Travis Crump wrote:
> Wouldn't it be a bug in the package if it build-depended on debhelper 4,
> but didn't actually use any features not available in debhelper 3[in
> which case it should build-depend on debhelper 3]?[and I have debhelper
> 4.1.52 and dh_shl
Rob Weir wrote:
On Thu, Aug 14, 2003 at 04:26:29PM +0200, Ismael Valladolid Torres wrote:
Mensaje escrito por Bob Proulx el 14/08/2003 1:54:
For my own backports I have been changing the debhelper version
dependency in the debian/control file to specify the woody version. I
have not backported
On Thu, Aug 14, 2003 at 04:26:29PM +0200, Ismael Valladolid Torres wrote:
> Mensaje escrito por Bob Proulx el 14/08/2003 1:54:
> >For my own backports I have been changing the debhelper version
> >dependency in the debian/control file to specify the woody version. I
> &g
Hi,
Looking at the list archives, I know this has been discussed before.
I am trying to backport some packages from unstable to woody. For some
of them, I get stuck into something like a "dependencies loop",
specially debhelper.
The source for debhelper 4.1.52 can be compile
Ismael Valladolid Torres wrote:
> I am trying to backport some packages from unstable to woody. For some
> of them, I get stuck into something like a "dependencies loop",
> specially debhelper.
For my own backports I have been changing the debhelper version
dependency in the
Mensaje escrito por Bob Proulx el 14/08/2003 1:54:
For my own backports I have been changing the debhelper version
dependency in the debian/control file to specify the woody version. I
have not backported debhelper. This process has worked pretty well so
far.
Indeed that was what I was thinking
On Mon, Jun 09, 2003 at 02:44:28PM +0100, Karl E. Jorgensen wrote:
[testing maintenance scripts]
> I believe that they *should* check build-dependencies; otherwise
> building debian from scratch might become impossible...
It would be nice; aj mentioned a while back that it wasn't done for
woody be
ld-depends
> > > or not;
> >
> > They don't, currently. Even so, gradual upgrades of debconf and
> > debhelper in step would have got around such a restriction.
>
> True. But unless the previous versions are kept, then it might become
> impossible to build a sarge fr
On Fri, Jun 06, 2003 at 06:27:30PM +0100, Colin Watson wrote:
> On Fri, Jun 06, 2003 at 12:10:45PM -0400, David Z Maze wrote:
> > I don't actually know whether the testing scripts check build-depends
> > or not;
>
> They don't, currently. Even so, gradual upgrade
On Fri, Jun 06, 2003 at 12:10:45PM -0400, David Z Maze wrote:
> "Karl E. Jorgensen" <[EMAIL PROTECTED]> writes:
>
> > debhelper 4.1.45 (=sid/sarge) builds OK, then resulting .deb then
> > depends on debconf-utils (>= 1.1.1) [source: debconf]
> >
&
On Fri, Jun 06, 2003 at 12:10:45PM -0400, David Z Maze wrote:
> I don't actually know whether the testing scripts check build-depends
> or not;
They don't, currently. Even so, gradual upgrades of debconf and
debhelper in step would have got around such a restriction.
"Karl E. Jorgensen" <[EMAIL PROTECTED]> writes:
> debhelper 4.1.45 (=sid/sarge) builds OK, then resulting .deb then
> depends on debconf-utils (>= 1.1.1) [source: debconf]
>
> debconf 1.2.35 (=sarge) build-depends on debhelper (>= 4.1.27)
> Which makes me
v]
libdv 0.99-2 (=sid/sarge) build-depends on debhelper (>= 4.1.1)
debhelper 4.1.45 (=sid/sarge) builds OK, then resulting .deb then
depends on debconf-utils (>= 1.1.1) [source: debconf]
debconf 1.2.35 (=sarge) build-depends on debhelper (>= 4.1.27)
So...
To backport libdv
Hello
Where can I download a potato version of debhelper, dpkg, debconf (and
apt ?) ?
For Xfree 4.02 (and many more woody packages I would like to compile on
my potato system) I must have debhelper > 2.1.18, but debhelper requires
debconf-utils but debconf (which provide debconf-utils) requi
On Fri, Feb 04, 2000 at 11:32:50AM +0100, Wojciech Zabolotny wrote
> Hi All,
>
> I'd like to compile/install the ted package on my slink box. Unfortunately
> the slink debhelper lacks the dh_installmime and dh_link functions, (and
> maybe some others) needed by the source pac
On Fri, Feb 04, 2000 at 11:32:50AM +0100, Wojciech Zabolotny wrote:
> I'd like to compile/install the ted package on my slink box. Unfortunately
> the slink debhelper lacks the dh_installmime and dh_link functions, (and
> maybe some others) needed by the source package of ted.
&
Hi All,
I'd like to compile/install the ted package on my slink box. Unfortunately
the slink debhelper lacks the dh_installmime and dh_link functions, (and
maybe some others) needed by the source package of ted.
Is it safe to upgrade the debhelper alone, and leave the rest of the slink
unto
On Wed, Jan 05, 2000 at 09:23:03PM +0100, Jens Günther wrote:
>
> Therefore I suggest to either bring debhelper and packages it depends on to
> a state in which they can be used in a slink environment (maybe putting
> these packages in proposed-updates) or to prevent them from b
oblems might arise for the
> development process I do not dare to guess.
>
> Therefore I suggest to either bring debhelper and packages it depends on to
> a state in which they can be used in a slink environment (maybe putting
> these packages in proposed-updates) or to prevent them fro
dh_compress
dh_fixperms
chown: --no-dereference (-h) is not supported on this system
dh_fixperms: command returned error code
make: *** [binary-arch] Error 1
---end quote---
Package: debhelper
Version: 2.0.80
Versions of the packages debhelper depends on:
ii perl5.004.04-7 L
On Tue, Jan 04, 2000 at 11:47:57AM +0100, Jens Guenther wrote
> Hi,
>
> I tried to build several potato packages for my slink machine. This failed,
> because some debhelper scripts were not available. After installing the
> potato version of debhelper, it failed again, this ti
Jens Guenther wrote:
> I tried to build several potato packages for my slink machine. This failed,
> because some debhelper scripts were not available. After installing the
> potato version of debhelper, it failed again, this time because some command
> (it might have been "chown&
* Jens Guenther <[EMAIL PROTECTED]> writes:
> Compilation worked fine. The only problem was that the package building
> process did not work. I could have installed the programs by hand, but I
> would have to bypass the package control system and would get problems when
> the real packages eventua
On Tue, Jan 04, 2000 at 02:23:16PM +0100, Jens Guenther wrote:
> > Some may be useless, e.g. sources that explicitly require glibc-2.1
> > or gcc-2.95.
> The problems I encountered where in no case compiler- or library-related.
> Compilation worked fine. The only problem was that the package buil
Hi!
> > Potato sources seem to be useless for slink installations.
>
> Some may be useless, e.g. sources that explicitly require glibc-2.1
> or gcc-2.95.
The problems I encountered where in no case compiler- or library-related.
Compilation worked fine. The only problem was that the package build
Hi,
* Jens Guenther <[EMAIL PROTECTED]> writes:
> I tried to build several potato packages for my slink machine. This failed,
> because some debhelper scripts were not available. After installing the
> potato version of debhelper, it failed again, this time because some command
&
Hi,
I tried to build several potato packages for my slink machine. This failed,
because some debhelper scripts were not available. After installing the
potato version of debhelper, it failed again, this time because some command
(it might have been "chown") did not support some co
On Tue, 2 Nov 1999, Joey Hess wrote:
>What was the error message?
>
Script started on Wed Nov 3 11:24:08 1999
[EMAIL PROTECTED]:~/tmp$ cd debhelper-2.0.67
[EMAIL PROTECTED]:~/tmp/debhelper-2.0.67$ fakeroot ./debian/rules binary
sh -e debian/fixlinks
touch link-stamp
./dh_clean
* XRDLAB <[EMAIL PROTECTED]> writes:
> I tried compiling the latest version of debhelper (from potato) under
> slink and could not succeed. Is there anything that I should upgrade
As it is "only" a Perl script, you can just use the package.
> before I can do that?
XRDLAB wrote:
> I tried compiling the latest version of debhelper (from potato) under
> slink and could not succeed. Is there anything that I should upgrade
> before I can do that?
What was the error message?
--
see shy jo
Hi,
I tried compiling the latest version of debhelper (from potato) under
slink and could not succeed. Is there anything that I should upgrade
before I can do that?
Thanks,
sridhar
Sridhar M. A.
Department of Physics
University of Mysore
57 matches
Mail list logo
