Hi Helmut,
On Wed, 09 Jul 2025, Helmut Grohne wrote:
> In Dpkg/Shlibs.pm in sub setup_library_paths, there is the following
> code:
[...]
> It is not clear to us, why that first branch exists. It was originally
> added by Raphaël in support of cross compilation and later changed a
> couple of t
On Fri, 09 Jun 2023, Marco d'Itri wrote:
> On Jun 08, Raphael Hertzog wrote:
>
> > In the same spirit, I'd like to throw an idea... could we decide that
> > base-files is the first package to be configured as part of the bootstrap
> > protocol and change ba
Hi,
On Wed, 17 May 2023, Helmut Grohne wrote:
> For completeness sake, there is one more entry in category 3: We can run
> the dynamic loader from its canonical location explicitly, so we'd
> modify maintainer scripts to start with:
>
> #!/usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 /usr/bi
Hello,
On Tue, 02 May 2023, Helmut Grohne wrote:
> I think there is a caveat (whose severity I am unsure about): In order
> to rely on this (and on DEP 17), we will likely have versioned
> Pre-Depends on dpkg. Can we reasonably rule out the case where and old
> dpkg is running, unpacking a fixed d
Hello,
On Wed, 26 Apr 2023, Simon Richter wrote:
> > This and /bin/sh is the kind of files I'd consider important. And then
> > upon thinking further it became more and more difficult for me to make
> > sense of the objection. On a merged system, we can just move that file
> > to its canonical loc
On Tue, 25 Apr 2023, Luca Boccassi wrote:
> Brilliant! Would never have thought of using divert like that.
+1 Nice trick.
> So, what work would need to happen to make this reality? Do we need
> tooling/scripts/build changes to support the divert scheme, or is it
> "simply" a matter of documenting
Hello,
On Sat, 22 Apr 2023, Helmut Grohne wrote:
> This is looking at it from a performance point of view. Guillem also
> raised that this is changing the source of truth from the dpkg database
> to the actual filesystem, which Guillem considers wrong and I find that
> vaguely agreeable.
smcv alr
Hello,
I'd like to offer some food for thoughts on this issue.
>From what I have understood, Guillem would rather avoid committing
to a new public interface for this specific use-case, i.e. the
fact that the DEP is suggesting "dpkg --add-alias" is problematic
because that feature will be useless
Hello,
On Mon, 03 Apr 2023, Helmut Grohne wrote:
> Please consider it to be a piece of best
> intentions at reconciling feedback wherever I could. At the time of this
> writing it certainly is not consensus, but consensus is what I seek
> here. Without further ado, the full DEP text follows after
On Thu, 03 Sep 2020, Niko Tyni wrote:
> > The $name tried is "Kali" and we don't ship any Dpkg::Vendor::Kali. The
> > code should fallback to Dpkg::Vendor::Debian and this works a few times
> > but after multiples calls, at some point it no longer works and the
> > require statement in the eval blo
On Sat, 02 May 2020, Scott Kitterman wrote:
> Personally, I don't see any real benefit of standardizing on (making up an
> example here) debian/.build over debian/build.
Same here. The arguments against debian/build are very weak. If we care
about a source package building a binary package named
Hello,
On Fri, 27 Apr 2018, Guillem Jover wrote:
> But in any case, I'm still open to data and opinions given that this
> is in the end a matter of trade-offs, so → request for comments. :)
I believe that the "zstd" compression format is providing an interesting
trade-off compared to other compre
On Tue, 13 Feb 2018, Julien Cristau wrote:
> On 02/13/2018 04:29 PM, Raphael Hertzog wrote:
> > I believe that we have had quite some testing already last time and I
> > would be surprised if we got many more RC bugs on dpkg that had to be fixed
> > on a short timeframe. I
On Mon, 12 Feb 2018, Ansgar Burchardt wrote:
> Guillem Jover writes:
> > In any case, I looked the other day into implementing the
> > --map-pathname option for dpkg-query, and I've got most of the code
> > ready. The problem is that this requires adding support for config
> > files and config frag
Hi,
sorry for the delay. I rarely look into this mailbox.
On Tue, 15 Aug 2017, Guillem Jover wrote:
> them quickly after that. Listing the amount of bouncing would also
> be nice, in a similar way how list.d.o does it, or even also sending
> the pre-warnings about possibly imminent unsubscription
Hi Guillem,
On Fri, 04 Aug 2017, Guillem Jover wrote:
> On Fri, 2017-08-04 at 02:19:59 -, ow...@tracker.debian.org wrote:
> > The email debian-dpkg@lists.debian.org bounces too much, it has been
> > unsubscribed from the
> > Debian Package Tracker.
> > Here's the list of subscriptions which h
Hi,
On Wed, 16 Sep 2015, Guillem Jover wrote:
> Thanks all! I'm going to push the attached patch. Hope the S-o-b are
> fine.
Sure, fine for me.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debi
Hello dear maintainer(s),
the Debian LTS team would like to fix the security issues which are
currently open in the Squeeze version of dpkg:
https://security-tracker.debian.org/tracker/CVE-2015-0840
I had a quick look. The squeeze version of dpkg has a much more lax
parser, so the issue might not
Hello Michael,
I stepped down from dpkg development and
http://jenkins.grml.org/view/Debian/job/dpkg-test-binaries/
http://jenkins.grml.org/view/Debian/job/dpkg-test-source/
were mostly my playground.
They are now useless, feel free to remove everything
related to them.
Cheers,
--
Raphaël Hertz
Hello everybody,
it's time to acknowledge that I don't have enough time and motivation for
dpkg (in particular since Guillem is still very upset about me, multiple
years afther the development of multiarch).
I unsubscribed from everything related to dpkg (including this list and
the PTS) and drop
On Thu, 04 Dec 2014, Simon McVittie wrote:
> On Thu, 04 Dec 2014 at 16:39:31 +0100, Niels Thykier wrote:
> > On 2014-12-04 09:11, Simon McVittie wrote:
> [see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770627#70 for full
> analysis]
> > If your interpretation is correct, then I am certainly
On Fri, 07 Nov 2014, Guillem Jover wrote:
> I'm going to revert the commit above (only in 1.17.x, it will be kept
> in 1.18.x), because it is very minimal, just reintroduces again an
> unnecessary package queue stage, and such regression is acceptable if
> it makes buggy bootstrappers work again. B
Hi,
On Mon, 03 Nov 2014, Sébastien POHER wrote:
> - I think Weblate will fit for smaller translations (Debian Security
> Annoucement and such), but dpkg is huge (+22K lines for man/po/fr.po)
> and I don't see myself going from an untranslated chain to another by
> clicking a hundred times;
There
Hi Guillem,
it would be nice if you could behave in a way so that I don't have the
feeling that I don't exist in the dpkg landscape for you.
FWIW (to the lurkers here) I approved Sébastien on the alioth project, I
recruited him as a French translator, and I informed Guillem about the
fact that I
Hi Guillem,
On Fri, 15 Aug 2014, Guillem Jover wrote:
> commit 59e6e1563a88f47d0011ee62bc3c7b763fb9ab4f
> Author: Guillem Jover
> Date: Fri Aug 15 15:26:53 2014 +0200
>
> dpkg-shlibdeps: Do not unnecessarily interpolate strings
>
> This mostly reverts commit 2379a80fbdc49084894b44
Hi,
On Mon, 02 Jun 2014, Aurelien Jarno wrote:
> > Alternatively, we can create an empty package called for example
> > multiarch-no-foreign, which is arch:any and Multi-arch: none. That way
> > all packages which should not be installed as foreign architecture can
> > depend on this one.
> >
> >
Hi,
On Sun, 16 Mar 2014, Guillem Jover wrote:
> > @dpkg/apt maintainers: I thought triggers should be run *after* the
> > package is fully installed and only the order of the triggers is not
> > guaranteed?
>
> W/o having looked into the details, this just seems like another
> instance of #6717
Hi,
On Fri, 14 Feb 2014, Thomas Goirand wrote:
> Looking at the script, it seems *very* complicated and hard to get it
> directly right. I believe I could write a much simpler version for my
> own needs (with less features, probably), reading what's been done in
> dpkg-maintscript-helper.
>
> So,
Hi Thomas,
On Thu, 13 Feb 2014, Thomas Goirand wrote:
> So I wonder, could dpkg-maintscript-helper be in another source package
> than dpkg, so that it could be easily backported?
Even if it was part of another package, it would have strong versioned
dependencies against dpkg because this script
Hi,
On Thu, 05 Dec 2013, Roland Stigge wrote:
> To implement a correct fix, Ben asked for a decision by dpkg
> maintainers, FTP team and policy. Basically, the question is if
I think Guillem's position is rather clear, since he filed #718330
requesting support of data.tar in APT. I also agree wit
Hi,
On Wed, 04 Dec 2013, Guillem Jover wrote:
> There's a thing I'm not entirely sold on yet, and will probably rethink
> it once I wake up, that's the name of the output field, currently
> Build-Profiles, but I'm pondering on Built-For-Profiles for example.
+1 for something else than Build-Profi
On Thu, 21 Nov 2013, Guillem Jover wrote:
> Ok, problem due to variables declared in the wrong scope, fixed
> locally, will push later today.
Thanks, will you also push the test I created or shall I do it?
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Discover the Debian Administrator's Handboo
Hi,
I just tried "dpkg --verify" as normal user and I got this:
$ LANG=C dpkg --verify
dpkg: warning: exim4-config: unable to open /etc/exim4/passwd.client for hash:
Permission denied
Erreur de segmentation
(That's a segfault in French)
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Discover
On Thu, 21 Nov 2013, Raphael Hertzog wrote:
> I was about to file a bug against clang-3.3 but what I discovered looked
> like more a bug in dpkg. It's probably related to the recent optimizations
> that concerns management of file lists.
[...]
> I have created a minimal test ca
Hi Guillem,
I was about to file a bug against clang-3.3 but what I discovered looked
like more a bug in dpkg. It's probably related to the recent optimizations
that concerns management of file lists.
In today's dist-upgrade:
Unpacking llvm-3.3 (1:3.3-13) over (1:3.3-12) ...
Preparing to unpack .
On Sun, 27 Oct 2013, Niels Thykier wrote:
> On 2013-10-27 05:22, Guillem Jover wrote:
> > dpkg-buildpackage: Honor new DEB_SIGN_KEYID environment variable
>
> Could you be convinced to change this to DEBSIGN_KEYID, which is the
> name that e.g. debsign uses? I have a feeling that if debsign an
Hi,
I just saw this on my system where the package cpputest is installed:
$ LANG=C dpkg -l >/dev/null
dpkg-query: error: cannot convert multibyte sequence '— main package
CppUTest is a C/C++ based unit xUnit test framework for unit testing and
for test-driving your code. It is written in C++ bu
Hi,
On Sat, 21 Sep 2013, Guillem Jover wrote:
> I guess there are no mirrors of those mboxes on non-restricted hosts?
> Otherwise having access to those would be very helpful.
I should have them locally via the PTS. Let me know when things are fixed
and what's the commit interval that I should bo
Hello,
On Sun, 11 Aug 2013, Bastien ROUCARIES wrote:
> I wish to contribute to dpkg particularly contributing to #583585
>
> Where should I begin ?
I think that you have found the required answers yourself. As a general
rule, we have documented everything that is important on this page:
https://
Hello,
FYI I have switched the script that generates commit notices to something
better: https://github.com/mhagger/git-multimail
- One thread per "refchange" per "push"
- Commit mails have the short description in the subject and they are
numbered (within the push)
For now, it runs out of my
On Mon, 22 Jul 2013, Charles Plessy wrote:
> Nevertheless, please let me try to refocus on the question of whether
> the Policy can be updated or not.
I believe we can update the policy whatever the status of this specific
bug.
> Here is what is written in the Policy about "postinst configure":
>
On Sat, 20 Jul 2013, Charles Plessy wrote:
> Can you explain what the bug is and what the correction will be ? Because I
The bug is that triggers are run while the dependencies of the triggered
package are not satisfied. The fix is not to do that and wait until those
dependencies are satisfied (b
Hi,
On Thu, 18 Jul 2013, Charles Plessy wrote:
> After reading #671711 and /usr/share/doc/dpkg-dev/triggers.txt.gz, my
> impression is that a package can not become "Unpacked" and keep a list of
> pending triggers, because of the following statements in triggers.txt:
>
> 1) Pending triggers are
On Thu, 18 Jul 2013, Charles Plessy wrote:
> Le Thu, Jul 18, 2013 at 08:55:20AM +0900, Charles Plessy a écrit :
> >
> > regarding “noawait” triggers, the patch already contains the following,
> > which
> > is new and improved compared to the existing documentation.
> >
> > The *-noawait dire
Hi,
On Wed, 17 Jul 2013, Charles Plessy wrote:
> About the problem of triggers being called with Depends not satisfied, can you
> give more explanations or suggest some text for the warning ? Would it be
> enough to add a notice that the triggered postinst script may be called when
> the package
Hi,
On Thu, 16 May 2013, Charles Plessy wrote:
> Guillem recently posted on debian-devel about "noawait" triggers, and I would
> like to send a link to the patch to the Policy once it gets futher
> proof-reading and seconds. Or if it takes time, shall I point to this bug log
> on -devel ?
I don'
Hi,
On Wed, 15 May 2013, Helmut Grohne wrote:
> > This new "Extends" field would imply that all meta-data (including other
> > missing control fields) is shared with the bar package and at build-time
> > it transparently gets a supplementary "Depends: bar (= )" but
> > the .deb would not have any
Hi,
On Tue, 14 May 2013, Игорь Пашев wrote:
> 2013/5/14 Raphael Hertzog :
> > But ansgar's objection about the duplication of the changelog in multiple
> > .deb when it used to be shared via a symlink also makes sense. As does the
> > fact that there's currently no
Hi,
On Mon, 13 May 2013, Guillem Jover wrote:
> The binNMU issue entails two “sub-problems”. The first is the one
> introduced by different entries in binNMUs on multiple architectures.
> The other is the unmatched versions for possible out-of-step binNMU
> versions.
>
> Personally I see very cle
Hi,
On Sun, 12 May 2013, Charles Plessy wrote:
>
> The *-noawait directives should be used unless the
> packages awaiting triggers can not satisfy Depends
> relationships until the triggers have been processed.
> In that case, the inter
Hi Charles,
On Sat, 11 May 2013, Charles Plessy wrote:
> I think that I took care of all of your comments.
>
> Here is an updated patch. Among the changes, it introduces
> sub-section to make the information easier to digest.
Thank you for the work! I have a few fixes and suggestions but otherw
On Tue, 23 Apr 2013, Johannes Schauer wrote:
> Raphael, your argument is very convincing and I am now even more in favour of
> Ian's proposal, thanks! Can you list some of those other use cases you said
> you
> can imagine? Maybe that helps to better decide upon the following:
I gave two already.
On Fri, 19 Apr 2013, Guillem Jover wrote:
> The following commit has been merged in the master branch:
> commit 26a4d1df1119da0a8601b27198086086f9f3249f
> Author: Guillem Jover
> Date: Sat Dec 29 23:59:06 2012 +0100
>
> Use just 'return' instead of 'return undef' in perl code
>
> T
Hi,
On Fri, 19 Apr 2013, Johannes Schauer wrote:
> 1. How bad is the spending of a new metacharacter and how needed is the
>namespace system? If there is no other usecase for these namespaces to
>conditionally include/exclude dependencies, then why introduce it? Is the
>fact that we ca
On Tue, 16 Apr 2013, Wookey wrote:
> So in general it seems like a good idea to me for dpkg shlibs to check
> multiarch paths at build time if it doesn't already, because it'll
> need to soon. I am of course happy to hear of reasons why that will
> break things and we should not do it yet.
All of
On Wed, 10 Apr 2013, Russ Allbery wrote:
> Raphael Hertzog writes:
> > On Fri, 15 Mar 2013, Charles Plessy wrote:
>
> >> +Dpkg defines the folowing states for the packages.
> >> +
> >> + Not-Installed
>
> > I would use the pr
Hi Charles,
On Fri, 15 Mar 2013, Charles Plessy wrote:
> I am still seeking comments for the attached patch, that describes Dpkg
> triggers.
Here are my comments. There's quite a bit of work left.
> >From 6a7fd0e49cb8dbd025771feb95c2dcafb408c1b8 Mon Sep 17 00:00:00 2001
> From: Charles Plessy
>
On Sun, 10 Feb 2013, Guillem Jover wrote:
> > +=item "$v", $v->as_string(), $v->as_string({no_epoch=>1, no_revision=>1})
>
> I've added a small mention about the new options here.
For consistency with other parts of the Dpkg::* perl API (for example in
Dpkg::IPC), there should not be any explicit
Hi,
On Sat, 09 Feb 2013, Bernhard R. Link wrote:
> Instead of doing the magic of generating a version string without epoch
> and revision and a version string without epoch in
> Dpkg::Source::Package, extend Dpkg::Version's as_string function to
> support generating that string.
Ok, why not.
> -
Hi Guillem,
On Tue, 30 Oct 2012, Guillem Jover wrote:
> Will be fixed in a push targetting 1.17.x.
You have accumulated a lot of fixes and changes in the 1.17.x branch and
it would be nice to have this branch public so that you're not the only
one who can work on 1.17.x material and so that we ca
Hi,
On Wed, 29 Aug 2012, Guillem Jover wrote:
> > /bin/as and
> > /usr/bin/@as --> ../../bin/as (symlink)
> >
> > dpkg throws "unable to open /bin/as.dpkg-new No such file or directory"
> >
> > I wish you can fix it :)
>
> When filing the bug, could you also attach the output of:
>
> # dpkg
Hi,
On Sun, 12 Aug 2012, Russ Allbery wrote:
> I'm looking for seconds so that we can finally merge this monster.
> Presented as a diff since that was the request last time, but the branch
> has also been pushed to the Policy Git repository, so if you want to
> review it various other ways, you ca
Hi,
On Fri, 08 Jun 2012, Guillem Jover wrote:
> Hmmm, so I had prepared a patch which basically checks if the package
> has its dependencies fulfilled before calling the postinst script with
> "triggered", and otherwise defers the trigger processing for later (but
> only as long as it is not runni
Hello,
On Sun, 05 Aug 2012, Robert Luberda wrote:
> > Processing triggers for doc-base ...
> > /usr/bin/perl: symbol lookup error: /usr/lib/perl5/auto/UUID/UUID.so:
> > undefined symbol: Perl_xs_apiversion_bootcheck
> > dpkg: error processing doc-base (--unpack):
> > subprocess installed post-in
Hi,
On Tue, 17 Jul 2012, Philipp Kern wrote:
> > I'm happy to prepare a stable update to fix this. Would you accept it?
>
> I presume there are no other RC bugfixes for dpkg/stable pending at the
> moment?
Guillem mentionned an SELinux fix that would be worth including too.
The commit that fixe
Hello,
On Fri, 13 Jul 2012, Michael Gissing wrote:
> Hi all,
>
> I'm not sure whether that's the suitable mailing list, so if theres
> a better one I would really appreciate a hint.
The correct list is debian-ment...@lists.debian.org. debian-dpkg is to
discuss the development of dpkg itself.
(K
On Thu, 12 Jul 2012, Philipp Kern wrote:
> > #681292 against sbuild. Feel free to clone it if necessary.
>
> I just verified a build in stable and get a bunch of these:
>
> dpkg-source --after-build hello-2.6
> parsechangelog/debian: warning: hello-2.6/debian/changelog(l1): unknown
> key-value
On Thu, 12 Jul 2012, Philipp Kern wrote:
> On Thu, Jul 12, 2012 at 08:59:38AM +0200, Raphael Hertzog wrote:
> > > > 3/ we modify sbuild to add the required "binary-only=yes" in the binNMU
> > > >changelog entries. Here's a sample header line:
> &
.
Sorry for that.
> On Wed, 2012-07-11 at 09:23:05 +0200, Raphael Hertzog wrote:
> > So it looks like that the "part of the changelog binNMU solution"
> > was just the possibility to tag a changelog entry "binary-only"
> > with a keyword.
>
>
On Wed, 11 Jul 2012, Russ Allbery wrote:
> I don't think it's mandatory that we save the information, but it
> certainly would be nice. I'd like apt-listchanges to show me the binary
> NMU changelog. I've used that information before on the local system, and
> that's a lot more convenient than go
On Wed, 11 Jul 2012, Jonathan Nieder wrote:
> > 1/ we modify dh_installchangelog to strip the binary-only changelog entry
> >for Multi-Arch: same packages
>
> Wouldn't (1) be throwing away information, unless the stripped
> information goes into another file?
>
> Making the stripped info go i
Hi Guillem,
On Wed, 20 Jun 2012, Guillem Jover wrote:
> I'll be doing a first push today. The remaning things I'll be finishing
> up next are at least the strings cleanup left out from the 1.16.4
> release, the cross-multiarch patches, part of the changelog binNMU
> solution, and some other multia
Hi,
On Tue, 12 Jun 2012, Guillem Jover wrote:
> > This allows us to get rid of the special-casing of bin-nmu in dpkg where
> > we only support one extension (+bX).
> >
> > We have many other cases where it would be helpful to be able to do such
> > binary-only rebuild in different environments and
Hi,
On Sun, 10 Jun 2012, Andreas Barth wrote:
> Asking to be sure: For sbuild, that means instead of changing the file
> debian/changelog before starting the build, a new file
> debian/changelog.binary-rebuild (or however it is named) is created
> and from there on all works "by itself"?
That's t
On Sun, 10 Jun 2012, Jonathan Nieder wrote:
> Raphael Hertzog wrote:
>
> > As such, I suggest that we handle "binary rebuild" differently:
> > - debian/changelog is left unmodified since it's the source changelog
> > => it defines the ${source:Versi
[ Dropping the bug report, moving the discussion to debian-dpkg too ]
Hi,
On Sun, 10 Jun 2012, Guillem Jover wrote:
> On Sat, 2012-06-09 at 15:26:06 +0200, Andreas Barth wrote:
> > However, we discussed that during the multi-arch bof last Debconf, and
> > came to the conclusion that it would be b
On Sat, 14 Apr 2012, Sven Joachim wrote:
> This seems to break dpkg-genchanges, e.g. when building acpid:
And it will break many infrastructure tools. I know that various QA tools
build the path name directly from the package name and the version without
referring to any "Packages" files. And they
On Tue, 03 Apr 2012, Jonathan Nieder wrote:
> Forgive my ignorance: could you explain the rationale for the choice
> that was made for the meaning of "dpkg-query -L " when
> is multiarch:same?
The choice was not made for "dpkg -L" only, it was made in general for
all the package names that dpkg t
Hi,
On Tue, 03 Apr 2012, Bill Allombert wrote:
> > /etc/cron.daily/popularity-contest:
> > dpkg-query: error: --listfiles needs a valid package name but
> > 'gcc-4.7-base' is not: ambiguous package name 'gcc-4.7-base' with more than
> > one installed instance
>
> I think dpkg should just report
Hi,
On Sun, 01 Apr 2012, Raphaël Hertzog wrote:
> The following commit has been merged in the master branch:
> commit ad37fc9b564a3cabccbf8b169d461695483edad8
> Author: Raphaël Hertzog
> Date: Sun Apr 1 13:37:26 2012 +0200
>
> Fix format string in French translation causing a build failure
On Sun, 01 Apr 2012, Michael Prokop wrote:
> * Raphael Hertzog [Sun Apr 01, 2012 at 10:01:26AM +0200]:
>
> > it looks like the auto-build of dpkg by jenkins is broken since quite some
> > time. The problem is in the way that you create the source package.
>
> > Som
Hello Mika,
it looks like the auto-build of dpkg by jenkins is broken since quite some
time. The problem is in the way that you create the source package.
Somehow we must regenerate the build files with "autoreconf -f -i" and
this requires "autoconf, automake, gettext, flex" to be installed.
Che
Hi,
On Mon, 19 Mar 2012, Guillem Jover wrote:
> The following commit has been merged in the master branch:
> commit 69b4245a2f0d994aef3fab5f4644b308e416efcd
> Author: Raphaël Hertzog
> Date: Fri Jan 14 16:07:26 2011 +
>
> t-multiarch: Add initial tests for dpkg architecture database
>
Hi,
On Sun, 18 Mar 2012, Guillem Jover wrote:
> With multiarch, non-installed selections w/o an architecture, do not
> make sense, in addition there's no guarantee they match any entry
> from the available file and the db could end up with a selection that
> could not be addressed from the command
Hi,
On Fri, 09 Mar 2012, Philipp Kern wrote:
> I'd appreciate if you could go ahead and push the xz strategies patch
> for dpkg-deb to unstable. The conversion of d-i udebs to xz
> compression blocks on this and should better not be delayed further.
> The other components are ready / will be patc
Hi,
On Wed, 14 Mar 2012, Sven Joachim wrote:
> Here is a patch adding two missing newlines on output:
Thanks.
> Note that libc-bin:amd64 is actually purged, however it remains in the
> status file (note that the "Multi-Arch: foreign" field is missing):
Ok, fixed that as well by ignoring "not-in
On Wed, 14 Mar 2012, Raphael Hertzog wrote:
> If it outputs nothing on your system, then you're fine. Otherwise
> it should give you some instructions to follow to bring it back to a
> coherent state.
There was a bug in the script. An updated version is attached.
Note that it
Hello,
For people who have been playing with multiarch and are scared by
Guillem's (uncoordinated) announce, I have written a small script
to detect whether you have been affected by one of the theoretical
problems that Guillem diagnosed (you only need libdpkg-perl and perl).
If it outputs nothin
On Fri, 09 Mar 2012, Colin Watson wrote:
> happening. The result of this work is attached, minus changelog which I
> can write up if this is acceptable.
Thank you for this! A quick comment though:
> +# Returns a list of all packages with pending triggers.
> +sub triggers_pending {
> + my @re
On Tue, 06 Mar 2012, John D. Hendrickson and Sara Darnell wrote:
> Debian [easily] installs 850 pkgs at a time: each having
> dependencies. Dependencies are resolved to to build the list: BUT
> the order to install / configure is un-ordered.
There is an order for the configuration since we ensure
Hi,
On Sat, 03 Mar 2012, Guillem Jover wrote:
> I've already said elsewhere why I didn't reply to the RT mail, and while
> obviously I'm not them, I'd venture to say their (IMO unjustified) angry
> reaction has been (partially) due to your campaign of fear mongering...
There has been no such camp
Hi,
On Sat, 03 Mar 2012, Helge Kreutzmann wrote:
> If I should simply "git push" and "git pull" thats fine with me as
> well, just last time this was not desired.
If you use "git pull --rebase" instead of "git pull", it should
be mostly fine.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Pre-o
Hi,
On Sat, 03 Mar 2012, Helge Kreutzmann wrote:
> Hello,
> after the recent git update in testing the wrapper stopped working:
>
> ~/skripte/git-wrapper udpate
> /home/helge/skripte/git-wrapper: invalid syntax
It turns out the problem is not in the script, it's in what you typed.
"udpate" inste
Hello,
On Sat, 03 Mar 2012, Helge Kreutzmann wrote:
> Hello,
> after the recent git update in testing the wrapper stopped working:
>
> ~/skripte/git-wrapper udpate
> /home/helge/skripte/git-wrapper: invalid syntax
> /home/helge/skripte/git-wrapper update: update the current branch of the
> repos
On Sat, 03 Mar 2012, Guillem Jover wrote:
> [ Replying to this now, because it appears some people seem to think
> mails that go unanswered are considered as accepted facts... ]
Answering mails (when the other side is expecting an answer) is important
when you want to assume the leadership on dp
Hi,
On Wed, 29 Feb 2012, Guillem Jover wrote:
> Despite the circumstances, I've still managed to find some motivation
> to work on finishing reviewing and fixing code.
Thanks for this!
> Last week I got the bulk of the stuff done, input interfaces, correct
> in-core db layout, cross-grading work
On Wed, 15 Feb 2012, Raphael Hertzog wrote:
> On Wed, 15 Feb 2012, Joey Hess wrote:
> > If your manual pages are already being installed to the correct
> > directories, you don't need to use dh_installman to install them,
> > you can just use dh_install. dh_installman wil
On Thu, 23 Feb 2012, Goswin von Brederlow wrote:
> > Package: 3depict
> > Source: 3depict (0.0.9-1)
> > Version: 0.0.9-1+b1
>
> Except that doesn't have to work (sorry for the ubuntu part):
>
> Package: gcc
> Source: gcc-defaults (1.93ubuntu1)
> Version: 4:4.4.3-1ubuntu1
>
> What would the versi
On Wed, 15 Feb 2012, Joey Hess wrote:
> Raphael Hertzog wrote:
> > Joey, would it be possible to also extract the language code from the
> > path when the dirname matches m{/man/([a-z][a-z](?:_[A-Z][A-Z])?)/man\d$} ?
> >
> > It's specific enough to avoid wrong gu
Hi,
the commit d7c001aa6b3d49f1542df05cde60406be2e981ec did not work out as
expected.
Stop using brace expansion to install man pages
The reason for using brace expansion in the first place was due to
debhelper starting to abort on empty glob expansion, needed because
transla
1 - 100 of 767 matches
Mail list logo
