On Fri, Jul 13, 2012 at 05:26:28PM +0200, Raphael Hertzog wrote:
retitle 595112 dpkg-maintscript-helper: new helper for moving a conffile
between packages
thanks
On Tue, 31 Aug 2010, Josh Triplett wrote:
Moving a conffile from one package to another seems to prove even more
difficult
the versions
Z : background this process to examine the situation
The default action is to keep your current version.
*** ssh_config (Y/I/N/O/D/Z) [default=N] ?
- Josh Triplett
signature.asc
Description: OpenPGP digital signature
Frank Lichtenheld wrote:
On Sat, May 13, 2006 at 12:16:32AM -0700, Josh Triplett wrote:
The dpkg prompt for a changed conffile offers the option to background
this process to examine the situation; however, choosing this option no
longer has any effect, other than printing a message:
Works
Package: dpkg
Version: 1.14.20
Severity: normal
File: /usr/sbin/dpkg-divert
dpkg-divert supports --admindir, but it does not seem to support --root.
- Josh Triplett
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64
Package: dpkg
Version: 1.15.8.4
Severity: wishlist
File: /usr/bin/dpkg-maintscript-helper
Moving a conffile from one package to another seems to prove even more
difficult than renaming it or removing it. Please consider providing
support for this case in dpkg-maintscript-helper.
Thanks,
Josh
Package: dpkg
Version: 1.15.8.10
Severity: wishlist
File: /usr/bin/dpkg-deb
dpkg-deb --fsys-tarfile /dev/stdin seems to work, but it would help to
have some guarantee in the documentation that it will always work, and
dpkg-deb will never seek on the input.
- Josh Triplett
-- System Information
. In this case, the discrepancy seems
perfectly reasonable. Please consider turning off that warning.
Thanks,
Josh Triplett
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64
.
A simple implementation would just poke all dpkg triggers. A more
sophisticated implementation would check for changes since the last
invocation.
- Josh Triplett
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental
On Wed, Apr 04, 2012 at 08:09:31AM +0200, Raphael Hertzog wrote:
On Tue, 03 Apr 2012, Josh Triplett wrote:
As a more optimal solution, packages could register file triggers on
appropriate paths in /usr/local
Some packages already do (man-db for example).
True. I just want to make sure
On Wed, Apr 04, 2012 at 11:43:48AM +0200, Raphael Hertzog wrote:
On Wed, 04 Apr 2012, Josh Triplett wrote:
In some way we already do:
$ sudo dpkg-trigger --no-await /usr/local/man
$ sudo dpkg --configure -a
Processing triggers for man-db ...
But there's easy way to find out all
On Tue, May 15, 2012 at 12:12:51AM +0200, Marco d'Itri wrote:
reassign 672945 dpkg
severity 672945 wishlist
retitle 672945 dpkg should support moving a conffile between packages
thanks
On May 14, Josh Triplett j...@joshtriplett.org wrote:
netbase 5.0 drops /etc/init.d/networking; thank
On Tue, May 15, 2012 at 01:16:31AM +0200, Marco d'Itri wrote:
On May 15, Josh Triplett j...@joshtriplett.org wrote:
Going by that post, would something like the following in the configure
section of the postinst work?
Not quite, this would be too much easy.
At least, we need to check
On Tue, Jul 31, 2012 at 05:21:38PM +0200, Raphael Hertzog wrote:
On Fri, 13 Jul 2012, Josh Triplett wrote:
On Fri, Jul 13, 2012 at 05:26:28PM +0200, Raphael Hertzog wrote:
Michael Biebl reported in the thread at
http://lists.debian.org/4f31c323.9090...@debian.org
that the difficulty
On Tue, Jul 31, 2012 at 08:47:06PM +0200, Raphael Hertzog wrote:
On Tue, 31 Jul 2012, Josh Triplett wrote:
Consider the original motivation for this. You have a package A, which
contains a daemon B and an init script /etc/init.d/B. You split B and
its init script (and any other
scripts before, and they previously
showed the name of the package, rather than just a temporary dpkg path.
- Josh Triplett
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.17.0-trunk
Package: libdpkg-perl
Version: 1.17.23
Followup-For: Bug #677865
What's the current status of this bug? The most recent mail, in May
2014, mentions a possible improvement in dpkg 1.17.10. Has the
necessarily perl packaging change not yet taken place?
I still see this issue every time I build a
This URL doesn't seem to work; it redirects to
https://anonscm.debian.org/cgit/dpkg/dpkg.git/diff/?id=
which says Bad object name:.
- Josh Triplett
--
To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
ional use
of File::FcntlLock entirely.
- Josh Triplett
On Mon, Jun 06, 2016 at 11:44:00PM +0200, Guillem Jover wrote:
> On Sun, 2016-06-05 at 14:37:51 -0700, Josh Triplett wrote:
> > Control: tags -1 + patch
> >
> > The attached patch implements the change I suggested, dropping fcntl
> > locking in favor of flock,
Control: tags -1 + patch
The attached patch implements the change I suggested, dropping fcntl
locking in favor of flock, and documenting that change in the changelog
along with the rationale.
- Josh Triplett
>From 0c6eddc8200e7bea482ad65c5870f7977847d26a Mon Sep 17 00:00:00 2001
From: J
On Sat, Jun 25, 2016 at 07:08:39PM +0100, Ian Jackson wrote:
> Josh Triplett writes ("Handling Multi-Arch packages that must be installed
> for every enabled architecture?"):
> > That would solve the problem for the couple of cases it has come up in,
> > but it seems
Simon McVittie wrote:
> On Fri, 24 Jun 2016 at 23:01:21 -0700, Josh Triplett wrote:
> > Some packages, if installed on any architecture, must be installed for
> > every enabled architecture. Most notably, an NSS or PAM module package,
> > if enabled in /etc/nsswit
e will have packages depending on libpam0g.
The real dependency is "if any package on the architecture depends on
package X, and package Y is installed, package Y:arch must be
installed", but that's excessively complicated.
Any ideas on how to solve this problem?
- Josh Triplett
David Kalnischkies wrote:
> On Sat, Jun 25, 2016 at 02:01:27AM -0700, Josh Triplett wrote:
> > Sven Joachim wrote:
> > > On 2016-06-24 23:01 -0700, Josh Triplett wrote:
> > > > Some packages, if installed on any architecture, must be installed for
> > > >
On Sat, Jun 25, 2016 at 09:37:37AM +0200, Ben Hutchings wrote:
> On Fri, 2016-06-24 at 23:01 -0700, Josh Triplett wrote:
> > Some packages, if installed on any architecture, must be installed for
> > every enabled architecture. Most notably, an NSS or PAM module package,
> &g
Matthew Garrett wrote:
> Debian package unified metadata format
In general, this looks like a good idea. Having this in a declarative
form would have a variety of good uses.
> Format:
>
> The file shall be stored within the control archive with the name
> “mtree” and shall start with the
g, to bail out on unrepresentable
> dependencies.
That change evidently got dropped as part of further changes to debcargo
(and the Rust packaging policy). Re-adding that will eliminate this
issue.
(Two-sided version constraints will make it possible, in the future, to
avoid the "unrepresentable dependencies" mentioned above; however, those
don't occur often.)
- Josh Triplett
On Tue, Jun 19, 2018 at 04:08:00AM +, Ximin Luo wrote:
> Josh Triplett:
> > While I *would* like to see support for version intervals, this
> > particular issue is a bug introduced through changes to debcargo. The
> > original debcargo intentionally generated v
the requirements of the standard; I'd
like to know what the standard allows/requires.)
Thanks,
Josh Triplett
On Sun, 19 Apr 2020 23:12:28 +0200 Guillem Jover wrote:
> On Sun, 2020-04-19 at 13:45:17 -0700, Josh Triplett wrote:
> > Package: dpkg-dev
> > Version: 1.19.7
> > Severity: normal
> > File: /usr/share/man/man5/deb-control.5.gz
>
> > The deb-control manpage
Package: dpkg-dev
Version: 1.19.7
Severity: normal
File: /usr/share/man/man5/deb-control.5.gz
The deb-control manpage seemed like the right place to look to find out
if Debian control files can have trailing commas in comma-separated
fields (such as Depends). However, it didn't mention whether
On Tue, May 05, 2020 at 06:21:41AM +0200, Guillem Jover wrote:
> On Mon, 2020-04-20 at 11:55:42 -0700, Josh Triplett wrote:
> > On Sun, 19 Apr 2020 23:12:28 +0200 Guillem Jover wrote:
> > > On Sun, 2020-04-19 at 13:45:17 -0700, Josh Triplett wrote:
> > > > Pac
32 matches
Mail list logo
