I agree with Ian.
If package maintainer wants to have a few extra ignore rules locally, why not
use
> .git/info/exclude
file.
I think its high time to fix this.
Osamu
control: severity -1 wishlist
thanks
This behavior was not much of real problem but how this happens was a
bit of mastery for me. Here is what I found out.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615807
If any kind of search term normalization is in place, search result
shouldn't
Hi,
The situation of case sensitivity can be summarized for web browser page
opened by the "dpkg-www" as:
Search term with tailing "*": case sensitive
Search term without tailing "*": case insensitive
As I read Policy 4.3.0
Hi,
On Tue, Mar 08, 2016 at 01:10:49AM +0100, Guillem Jover wrote:
> I don't think the attached patch does what you intended though? --sort
> only works when packing (i.e. when reading from the filesystem).
Very true. Excuse me.
Maybe basic command such as dpkg-deb shoudl not filter output
Package: dpkg
Version: 1.18.4
Severity: wishlist
Tags: patch
Making dpkg-deb to be deterministic by fixing #719845 was good for
reproducible build. But "dpkg-deb -c" output is not human friendly.
Basically, we want it to be sorted by name instead of internal data
order.
Please consider adding
Package: dpkg-dev
Version: 1.17.25
Severity: normal
This is about dpkg-source -x ... for multiple upstream tarbells.
In short, if there are directories matching component names of secondary
tarballs, dpkg-source should not warn them if such directories contain
nothing. (I checked the pertinent
Package: dpkg
Version: 1.17.1
Severity: wishlist
In short, dpkg -L is not friendly to multiarch. Let's make dpkg -L as
friendly as dpkg -l without causing problems to others.
Currently, if I run dpkg -L on a multiarch package, it returns very
unfriendly response. For example:
| $ dpkg -L
Package: dpkg
Version: 1.16.9
Severity: normal
[This may be a minor bug.]
Command: update-alternatives ---config etc.
The displayed selection of auto mode with the same priority
currently seems to be based on the first alphabetic order one.
But the reality for the same priority case seems to
Package: dpkg-dev
Version: 1.15.7.2
Severity: minor
deb-control(5) has been updated for new 3.9 policy but it is not perfect
yet. I attach a sure fix as patch and discuss other points below:
Question: Do we need tomention Breaks in below in place of Conflicts or list
both?
Replaces:
Hi dpkg folks,
I think this old update-alternatives bug needs to be fixed for lenny.
I merged many bug reports. Many of which were reassigned from other
packages. So impact to annoyance of users exists.
If you want to be very conservative patch for lenny, you should use just
following parts of
severity 141325 important
tags 141325 patch
forcemerge 141325 199426 203582 282290 285686 311288 311288
thanks
Hi,
When alternative system has broken link for some reason and only one
package uses that alternative system in manual mode, update-alternative
does not update link properly and exits
11 matches
Mail list logo
