On 10 June 2014 04:58, Axel Beckert a...@debian.org wrote:
One remark though about something I didn't notice with the previous
version:
aptitude doesn't seem to cleanly build twice in a row. After a
non-chrooted build with debuild and debclean afterwards,
pdebuild for the chrooted build
of aptitude-common. (Closes: #746960)
* Remove non-ASCII punctuation from changelog. (Closes: #745680)
* Drop apt-xapian-index to Suggests.
(and misc. upstream changes, as noted in NEWS)
Regards
Daniel Hartwig
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
On 2 June 2014 19:29, Axel Beckert a...@debian.org wrote:
There are at least the following packaging changes which is not
mentioned in the changelog entry, but IMHO should:
* There's a new build-dependency on libxapian-dev. This seems due to
upstream changes. Nevertheless this should be
On 2 June 2014 19:48, Axel Beckert a...@debian.org wrote:
Hi Daniel,
Daniel Hartwig wrote:
Will add:
* debian/control: New Build-Depends on libxapian-dev,
replacing libept-dev.
Thanks.
Uploaded (mentors.d.n).
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
~rc1-2) experimental; urgency=low
[ Daniel Hartwig ]
* do not run tests in parallel
* debian/patches:
- 12_test-debian.patch: NoDetachDaemon_Case is broken and leaves an
orphaned process; disabled to keep buildd happy (Closes: #709169)
- 14_test-reliability.patch: improve
feedback on some ambiguous items), improvements to the
package descriptions, and migrating to dh_python2.
Changes since the last upload:
distcc (3.1-6) unstable; urgency=low
[ Daniel Hartwig ]
* distcc suggests dmucs
* debian/distcc.init:
- rename from distcc.init.d
- also use --oknodo
On 2 March 2013 00:12, Paul Johnson pauljoh...@gmail.com wrote:
Hello,
Its me again. Once again, I'm throwing myself on your mercy because
although I like programming and packaging, I am having a horrible time
finding my way through your web pages to adopt a package and keep it
up to date.
Package: sponsorship-requests
Severity: important
Hello mentors
I am seeking a sponsor for NMU of guile-1.6 to fix an RC bug.
http://mentors.debian.net/debian/pool/main/g/guile-1.6/guile-1.6_1.6.8-10.3.dsc
The changes are:
guile-1.6 (1.6.8-10.3) unstable; urgency=low
* Non-maintainer
On 5 September 2012 17:53, Axel Beckert a...@debian.org wrote:
I wish to make stable-0.6 the new master while avoiding a merge or
revert+merge on master (the difference between them is quite large).
I'd have expected a merge as I think the CLI fixups in 0.6.9 (which
are IIRC the main changes
On 5 September 2012 14:55, Florian Schlichting
fschl...@zedat.fu-berlin.de wrote:
Have you considered keeping branch names as they are, and setting
git-debian-branch (and git-upstream-branch) in debian/gbp.conf /
.gbp.conf?
Yes, but master will never be used again so I'd rather not leave it
On 5 September 2012 15:48, Thomas Goirand z...@debian.org wrote:
I never understood why everyone insist in using the default name master.
This doesn't express anything at all. Instead, you should be using:
- wheezy
- sid
- experimental
Right. That has been a sort of long-term goal ;-)
For
Hello mentors
Two months ago I release aptitude 0.6.9 to experimental. Many of
those changes will not make it in to Wheezy and I am refactoring and
publishing some of the updates under 0.6.8.n. This refactoring is
proving to be a better base of development going forward so I plan to
forget
Package: sponsorship-requests
Severity: important
Hi mentors
Looking for a sponsor for my package distcc:
http://mentors.debian.net/package/distcc
http://mentors.debian.net/debian/pool/main/d/distcc/distcc_3.1-5.dsc
It has not been actively maintained for some time and the maintainer
has
13 matches
Mail list logo
