Package: dpkg
Version: 1.20.9
Severity: wishlist
To avoid confusion the man page to dpkg-statoverride should
mention explicitly that it does *not* run chmod or others to
actually change the access permissions to already installed
files, or to files that are not part of a Debian package, or
to
Package: dpkg
Version: 1.19.7
I am pretty sure this is not supposed to happen:
# aptitude upgrade
:
Setting up smartmontools (7.1-1~bpo10+1) ...
Installing new version of config file /etc/default/smartmontools ...
Installing new version of config file /etc/init.d/smartmontools ...
Package: dpkg
Version: 1.19.7
Trying to replace a directory with a symlink on the upgrade
of a private package I stumbled over this:
root@dpcl082:/usr/lib/jvm# dpkg --contents
/var/cache/apt/archives/adoptopenjdk11_11.0.8+10-1_amd64.deb
drwxr-xr-x root/root 0 2020-08-20 12:29 ./
Package: dpkg
Version: 1.18.25
Severity: wishlist
On a package upgrade/reinstall dpkg should show a warning about
a missing config file that is not recovered from the *.deb file.
It is pretty unlikely that a config file has been deleted on
purpose. It is much more likely that a config file has
Apparently its already documented, so please excuse the noise.
Harri
Package: dpkg
Version: 1.19.4
I got this error:
# apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
libdbus-glib-1-2 libdbus-glib-1-dev libdbus-glib-1-dev-bin python-dbus
4
Package: dpkg
Version: 1.18.24
Running atp upgrade I get several lines about "Created symlink" with some
weird chars, turning my log file into a binary file:
:
:
Processing triggers for systemd (232-25+deb9u2) ...
Setting up libhtml-parser-perl (3.72-3) ...
Setting up liblwres141:amd64
Package: dpkg
Version: 1.18.24
Severity: wishlist
Would it be possible to automatically add the most recent
changelog entry to the package.dsc file at build time?
This would make it possible to easily browse the most
recent changes without downloading a giant changelog file.
Regards
Harri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Less wasn't removed, but /usr/bin/less (a symlink!) became
unavailable during the upgrade. After the upgrade from Jessie
to Stretch (including a new "less" package) /usr/bin/less was
back.
Regards
Harri
-BEGIN PGP SIGNATURE-
Package: dpkg
Version: 1.17.25
Use case: dpkg reports a config file conflict. I choose "z" to
edit the file (emacs) in a shell session (bash).
Problem: I cannot leave emacs using ^X-^C or ^Z, because both
^C and ^Z are disabled. Without second terminal I am stuck.
Regards
Harri
Hi Guillem,
On 07/22/15 15:19, Guillem Jover wrote:
If dpkg is unreliable, then what are the package signatures good for?
I'm not sure which package signatures you're talking about. But, no, this
is very old “expected” behavior, it's documented both in the dpkg FAQ:
I can assure you that
Package: dpkg
Version: 1.16.16
gcc-multilib (4:4.7.2-1, amd64) provides a symbolic link for
/usr/include/asm
# dpkg --contents /var/cache/apt/archives/gcc-multilib_4%3a4.7.2-1_amd64.deb
drwxr-xr-x root/root 0 2012-09-27 02:02 ./
drwxr-xr-x root/root 0 2012-09-27 02:02 ./usr/
Hi Guillem,
On 06/24/14 12:27, Guillem Jover wrote:
The correct solution is usually to upgrade to a fixed version.
Sorry to say, but I disagree. Removing a package should not be
blocked completely, if it is not in a dependency chain of
something else. Installing a newer version might not be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: dpkg
Version: 1.17.10
I had installed a package with broken systemd support. When I
try to purge this package again, then I get
# dpkg -P plxc
(Reading database ... 283820 files and directories currently installed.)
Removing plxc
Attached you can find a patch to support an environment
variable DEBKEY providing the key to use. ${DEBKEY}
can be overriden using dpkg-buildpackage -k key.
Hope this helps.
Harri
--- /tmp/dpkg-buildpackage.pl 2013-07-28 11:56:47.0 +0200
+++ scripts/dpkg-buildpackage.pl 2013-08-31
Hi Guillem,
On 08/11/13 17:57, Guillem Jover wrote:
This was already reported, I'll be fixing it pretty soon as part of
a rework of the dpkg-buildpackage code.
Sorry, I had missed #615813 (and maybe others). I would suggest to
merge the bug reports or to close this as a dup.
Many thanx
Package: dpkg-dev
Version: 1.17.1
I have moved to 2048bit rsa sha2 for gpg. Problem: dpkg-buildpackage
insists to use the old 1024bit dsa sha1 key, even though I have set
the new default in .gnupg/gpg.conf and in an environment variable
$GPGKEY.
dpkg-buildpackage -k${GPGKEY} works as expected.
Package: dpkg
Version: 1.15.8.13
If my init script stops the daemon without a $PIDFILE and
with --retry (e.g.
start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --name $NAME )
then the daemon exits with exit value 143 (SIGTERM).
start-stop-daemon should not forward this as an error
Sorry, I have shot myself into the foot. Please close.
Keep on your good work
Harri
--
To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: dpkg
Version: 1.15.8.13
Severity: wishlist
Seems that dpkg does some tricks using ^M on stdout, even
if it is writing into a logfile. Sample:
:
Package installation log:
^MExtracting templates from packages: 33% ^MExtracting templates from packages:
67%^M Extracting templates from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: dpkg-dev
Version: 1.16.9
Severity: wishlist
Would it be possible to support a command line argument
-C somedir to run dpkg-checkbuilddeps in another
directory without pushd and popd and a temporary variable
to safe the exit value?
This
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/28/12 11:11, Raphael Hertzog wrote:
Hi,
On Fri, 28 Dec 2012, Harald Dunkel wrote:
Would it be possible to support a command line argument -C somedir to run
dpkg-checkbuilddeps in another directory without pushd and popd and a
temporary
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: dpkg
Version: 1.16.8
Severity: wishlist
It would be very nice if dpkg could manage system users and groups
created for each package.
At the moment I've got GID 105 for dbus on host A, while 105 is
used for saned on host B (just as an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: dpkg-dev
Version: 1.16.1.2
Severity: wishlist
Can debian/rules access version information from changelog
in some Makefile variables set by dpkg-buildpackage? DPM
and the man page don't tell, afaics.
Version information would be helpful for
Package: dpkg-dev
Version: 1.15.8.11
Severity: wishlist
Working on a private package I got
dpkg-gencontrol: error: error occurred while parsing Depends field: ,
This error message could be much more useful if it would
include a line number.
Regards
Harri
--
To UNSUBSCRIBE, email to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
PS: I checked the backups: The virtualbox record in the status file
hasn't changed since March 25th. Thats the oldest backup I have.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
Hi folks,
This bug should be easy to fix (as shown by Brendan), so
what is the problem here?
This is a serious problem if you want to maintain a
chroot in amd64 to support i386 applications. It would be
very nice if the priority of this bug report is increased
and somebody adds the obvious fix
27 matches
Mail list logo
