Re: [Aptitude-devel] Please giveback aptitude/0.8.6-1 on mips64el

2017-03-06 Thread YunQiang Su 
On Tue, Mar 7, 2017 at 4:47 AM, James Cowgill  wrote:
> Hi,
>
> On 06/03/17 20:23, Axel Beckert wrote:
>> Hi James,
>>
>> James Cowgill wrote:
 https://buildd.debian.org/status/fetch.php?pkg=aptitude&arch=mips64el&ver=0.8.6-1&stamp=1488829841&raw=0
ackage tracker
> This package tracker is better than the old one on many aspects (easy to
> extend, more dynamic, responsive, packed with new features such as
> subscription management on the web, team subscriptions, etc.) but should
> you find some features that are lacking or some other problems, then
> please file bug reports against the tracker.debian.org pseudo-package.
> Also don't hesitate to help us by contributing patches for those issues.
>
> Not convinced? Go back to the old package tracking system.
 Again some tool in the documentation tool chain segfaults on mips64el.
>>>
>>> Done.
>>
>> Thanks for the prompt reaction!
>>
>>> This bug in libxml2 is Loongson specific so it will only happen on
>>> some buildds.
>>
>> Fits with our observation. Usually when the package is later build on
>> a different buildd, then it builds fine.
>>
>> But I can't find any such bug on
>> https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libxml2
>> Do you know where I can find the according bug report?
>
> Sorry, I think I phrased that wrong - there may not be a bug in libxml2.
> It's been known for some time that the Loongsons have issues with
> certain newer MIPS instructions (as used on mips64el). I'm not sure if
> this bug has ever been fully investigated, but since it only happened on
> Loongson I think it was just written off as a hardware glitch.
>
> Yunqiang, did you ever look into it (only asking because you appear to
> be a maintainer of libxml2)?
>

I also don't think that it is a bug of libxml2.
Let me have it a try on newer Loongson machine: 3A 3000.

> Thanks,
> James
>

___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Processed: Re: aptitude: refuses to upgrade packages, 'g' says "Actions: no changes"

2017-03-06 Thread Debian Bug Tracking System 
Processing control commands:

> reopen -1
Bug #836708 {Done: "Manuel A. Fernandez Montecelo" 
} [aptitude] aptitude: refuses to upgrade packages, 
'g' says "Actions: no changes"
Bug reopened
Ignoring request to alter fixed versions of bug #836708 to the same values 
previously set

-- 
836708: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836708
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#836708: aptitude: refuses to upgrade packages, 'g' says "Actions: no changes"

2017-03-06 Thread Vincent Lefevre 
Control: reopen -1

Hi,

On 2017-03-06 22:57:18 +0100, Manuel A. Fernandez Montecelo wrote:
> 2016-09-05 02:33 Vincent Lefevre:
> > On 2016-09-05 01:50:04 +0200, Vincent Lefevre wrote:
> > > In the UI, I've selected various packages for upgrade; I can see
> > > no breakages. But the 'g' key doesn't have any effect, it just
> > > says: "[1(1)/...] Actions: no changes" with no explanations.
> > 
> > And 'e' (Examine) just says:
> > 
> >  --\ Leave the following recommendations unresolved:
> >libmtp9 recommends libmtp-runtime
> > 
> > libmtp9 recommends libmtp-runtime
> > --\ The following actions will resolve this dependency:
> >  -> Cancel the removal of libmtp-runtime
> >  -> Downgrade libmtp-runtime [1.1.12-1 (now, testing, unstable) -> 
> > 1.1.8-1+b1 (
> >  -> Leave the dependency "libmtp9 recommends libmtp-runtime" unresolved.
> > 
> > which makes no sense since nothing related to libmtp is proposed.
> 
> This was implemented after your complaint in #819636 (not upgrading
> "lightly" if it means breaking a recommend relationship), which then
> needed #822329 to not be so eager on fixing unfulfilled recommends.

Except that libmtp-runtime was already installed, so that the
dependency was satisfied! And I didn't request it to be removed.
So, the above message is simply buggy.

In any case, "Actions: no changes" is not a meaningful error message and
isn't even documented anywhere (neither in the man page, nor in the manual).
So, the fact that this message appears is a bug.

Regards,

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#841506: aptitude: cannot reinstall package available as update

2017-03-06 Thread Jonas Smedegaard 
Quoting Manuel A. Fernandez Montecelo (2017-03-06 22:33:18)
> Control: tags -1 + moreinfo
> 
> 
> Hi Jonas,
> 
> 2016-10-21 11:22 Jonas Smedegaard:
> >Package: aptitude
> >Version: 0.8.3-1+b1
> >Severity: important
> >
> >-BEGIN PGP SIGNED MESSAGE-
> >Hash: SHA256
> >
> >Aptitude has thrown me into limbo (hence severity important):
> >
> >A kernel update failed (ran out of space in /boot, and/or bugs in kernel
> >hooks for sicherboot), flagging it as needing a reinstall.
> >
> >Choosing "L" to reinstall and then "G", is refused with (in danish, on
> >my system) a message saying that no packages will be installed, removed
> >or upgraded, some packages could be upgraded, and I should press "U" to
> >do that.
> >
> >Seems that check is missing the option of reinstall in its logic.
> 
> I think that the problem might be that it cannot use the same version of
> the package to download, if it's not available in the list of packages,
> so it cannot do nothing, other than suggesting to upgrade.

Not sure I follow what you are saying above.  Seems you are saying that 
you suspect that pressing "L" cannot work.  I have reinstalled packages 
before in that way.


> Do you remember if it allowed you to fix the system by using "+"
> (install or upgrade) instead?

No, I did not try to use "+": Aptitude explicitly told that it needed 
_reinstall_ and it worked to _request_ a reinstall but then failed to 
_execute_ the request. Frankly didn't occur to me to try trick aptitude 
by requesting an _update_ for a package with no newer version available 
but in broken state.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature
___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Processed: Re: Bug#710687: aptitude: highlight the "alternative dependencies bar |"

2017-03-06 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 + wontfix
Bug #707324 [aptitude] aptitude: hint users about [added] alternative 
dependencies on upgrade/install
Added tag(s) wontfix.
> close -1
Bug #707324 [aptitude] aptitude: hint users about [added] alternative 
dependencies on upgrade/install
Marked Bug as done

-- 
707324: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#707322: Bug#710687: aptitude: highlight the "alternative dependencies bar |"

2017-03-06 Thread Manuel A. Fernandez Montecelo 

Control: tags -1 + wontfix
Control: close -1


Hi,

2013-06-02 05:12 Christoph Anton Mitterer:


On Sun, 2013-06-02 at 09:40 +0800, Daniel Hartwig wrote:

Personally I dont have trouble with that.  Although it does place some
burden on the administrator, the information is well structured and
certainly not hidden.

Well but it's definitely not obvious... even when you're on stable (not
to talk when you track testing or unstable with countless of updates
every day)... you will see many updates (when the next stable comes)...
and it's basically impossible to go through all packages and manually
compare what was added and what has gone. Changelogs are also only of
limited help, given the vast amount of entries, and sometimes such
information is simply missing.

In the direction of new alternatives being added, it is perhaps possible
to go through all packages and look for new ones... I did this the day
before for a small installation with ~3000 packages took me 4 hours
and you fell like crazy afterwards.


Implementing and maintaining this in aptitude is vastly more costly than
4h, probably many more than 40h as well, and (I am sure) the source many
bugs or crashes and complications as the libraries evolve, so sorry, but
I am not keen on extending aptitude in that direction...

In the case of stable systems, things only change every stable release
happening every few years, so one can surely dedicate some time to the
packages that one is interested into (e.g. media players).  Sometimes
upstream packages become dead or undergo big changes (e.g. forks with
more features, the Debian package mantaining the name but becoming
orphan/obsolete/buggy/neglected), so if one does not pay a lot of
attention to the external world which aptitude cannot know anyway, the
decisions will just be uninformed.

And well, if not interested or motivated enough, well, one can just
ignore it and probably not missing much -- as most people do.


In summary, the cost/benefit doesn't look good to me, and I wouldn't
even know hwre to beging to look for that information and try to
implement it without slowing down aptitude operations in the general
cases, so I am just going to close these as +wontfix.

This could perhaps be more easily implemented with python-apt, or
something similar to apt-listchanges, perhaps even invoked automatically
as it happens with apt-listchanges or apt-listbugs.



For the other way round, getting rid of packages which you once
installed because e.g. package foo recommended,... but after a while it
dropped the Recommends... but apt/aptitude won't notice because in the
meantime package bar recommends/suggests it as well (however one never
wanted to use it for/with that)... is basically impossible.


It is possible to limit the number of packages to review to match only
those with suggests and no recommends or things like that with search
patterns, to down the list to some manageable size to review more
closely.


Cheers.
--
Manuel A. Fernandez Montecelo 

___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Processed: Re: Bug#710687: aptitude: highlight the "alternative dependencies bar |"

2017-03-06 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 + wontfix
Bug #707322 [aptitude] aptitude: show which dependencies (or 
suggests/recommends/enhances) a package would loose on upgrade
Added tag(s) wontfix.
> close -1
Bug #707322 [aptitude] aptitude: show which dependencies (or 
suggests/recommends/enhances) a package would loose on upgrade
Marked Bug as done

-- 
707322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707322
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#846570: aptitude: Fails when trying to upgrade apt

2017-03-06 Thread Manuel A. Fernandez Montecelo 
Control: close -1 



Hi,

2016-12-02 10:44 Ulrich Klauer:

Package: aptitude
Version: 0.8.3-1+b2
Severity: important

When running an "aptitude safe-upgrade" on a Debian testing system that,
among other things, was meant to upgrade the apt package (from 1.3.1 to
1.4~beta1), I got this output:


...
Vorbereitung zum Entpacken von .../libapt-pkg5.0_1.4~beta1_amd64.deb ...
Entpacken von libapt-pkg5.0:amd64 (1.4~beta1) über (1.3.1) ...
libapt-pkg5.0:amd64 (1.4~beta1) wird eingerichtet ...
(Lese Datenbank ... 266980 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../0-libapt-inst2.0_1.4~beta1_amd64.deb ...
Entpacken von libapt-inst2.0:amd64 (1.4~beta1) über (1.3.1) ...
Vorbereitung zum Entpacken von .../1-apt_1.4~beta1_amd64.deb ...
Entpacken von apt (1.4~beta1) über (1.3.1) ...
dpkg: Fehler: dpkg-Status-Datenbank ist von einem anderen Prozess gesperrt
dpkg: Fehler: dpkg-Status-Datenbank ist von einem anderen Prozess gesperrt
dpkg: Fehler: dpkg-Status-Datenbank ist von einem anderen Prozess gesperrt
E: Sub-process /usr/bin/dpkg returned an error code (2)
E: Unterprozess dpkg --set-selections hat Fehlercode zurückgegeben (2)
E: Couldn't revert dpkg selection for approved remove/purge after an error was 
encountered!
E: Unterprozess dpkg --set-selections hat Fehlercode zurückgegeben (2)
E: Couldn't restore dpkg selection states which were present before this 
interaction!
dpkg: Fehler: dpkg-Status-Datenbank ist von einem anderen Prozess gesperrt
E: Konnte Sperre /var/lib/dpkg/lock nicht bekommen - open (11: Die Ressource 
ist zur Zeit nicht verfügbar)
E: Sperren des Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, 
wird es von einem anderen Prozess verwendet?
E: Die System-Sperre konnte nicht zurückerlangt werden! (Vielleicht läuft noch 
ein apt oder dpkg?)
E: Konnte Sperre /var/lib/dpkg/lock nicht bekommen - open (11: Die Ressource 
ist zur Zeit nicht verfügbar)
E: Sperren des Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, 
wird es von einem anderen Prozess verwendet?

Aktueller Status: 1 (+1) broken, 182 (-13) upgradable.
W: Zwischenspeicher-Datei konnte nicht gesperrt werden. Das bedeutet in der 
Regel, dass dpkg oder ein anderes APT-Werkzeug bereits Pakete installiert. 
Öffnen im Nur-Lesen-Modus. Alle Änderungen, die Sie am Status von Paketen 
durchführen, werden VERLOREN gehen!


The messages are mostly in German. The essential point, however, is that
dpkg could not get a lock on its database. I had of course no parallel
invocation of aptitude, apt, dpkg or anything running at the time, only
this "aptitude safe-upgrade".

It may be that it is actually a bug in a script for the apt package? If so,
please feel free to reassign.


I think that it was something like that, yes, but now it's a bit late to
reassign, so I think that it's better to just close it (since it's not
present in later versions).

In the future there will be a new feature in dpkg to deal with this kind
of cases more gracefully, which we hope to implement for stretch+1.


Cheers.
--
Manuel A. Fernandez Montecelo 

___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Processed: Re: aptitude: Fails when trying to upgrade apt

2017-03-06 Thread Debian Bug Tracking System 
Processing control commands:

> close -1
Bug #846570 [aptitude] aptitude: Fails when trying to upgrade apt
Marked Bug as done

-- 
846570: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846570
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#836708: aptitude: refuses to upgrade packages, 'g' says "Actions: no changes"

2017-03-06 Thread Manuel A. Fernandez Montecelo 

Control: tags -1 + wontfix
Control: close -1


Hi,

2016-09-05 01:50 Vincent Lefevre:

Package: aptitude
Version: 0.8.3-1
Severity: normal

In the UI, I've selected various packages for upgrade; I can see
no breakages. But the 'g' key doesn't have any effect, it just
says: "[1(1)/...] Actions: no changes" with no explanations.


That means that the currently selected action is "no changes" (== cancel
install actions, for example).



Quitting aptitude and retarting it doesn't solve the problem.
Neither does trying "Next".

Here's the log from

 aptitude --log-file=/tmp/aptitude.log --log-level=info

2016-09-05 01:43:58 [139874063632256] temp.cc:207 INFO aptitude.temp - 
Initialized the temporary file module using the base directory 
/tmp/aptitude-root.18653:XjDwmS
2016-09-05 01:43:58 [139874063632256] apt.cc:329 INFO aptitude.apt.globals - 
Closing apt cache.
2016-09-05 01:43:58 [139874063632256] apt.cc:398 INFO aptitude.apt.globals - 
Loading apt cache.
2016-09-05 01:44:02 [139874063632256] problemresolver.h:3804 INFO 
aptitude.resolver.search - Initially broken dependency: libmtp9:amd64 1.1.12-1 
-S> {libmtp-runtime:amd64 1.1.12-1 libmtp-runtime:amd64 1.1.8-1+b1}



this


2016-09-05 02:33 Vincent Lefevre:

On 2016-09-05 01:50:04 +0200, Vincent Lefevre wrote:

In the UI, I've selected various packages for upgrade; I can see
no breakages. But the 'g' key doesn't have any effect, it just
says: "[1(1)/...] Actions: no changes" with no explanations.


And 'e' (Examine) just says:

 --\ Leave the following recommendations unresolved:
   libmtp9 recommends libmtp-runtime

libmtp9 recommends libmtp-runtime
--\ The following actions will resolve this dependency:
 -> Cancel the removal of libmtp-runtime
 -> Downgrade libmtp-runtime [1.1.12-1 (now, testing, unstable) -> 1.1.8-1+b1 (
 -> Leave the dependency "libmtp9 recommends libmtp-runtime" unresolved.

which makes no sense since nothing related to libmtp is proposed.


This was implemented after your complaint in #819636 (not upgrading
"lightly" if it means breaking a recommend relationship), which then
needed #822329 to not be so eager on fixing unfulfilled recommends.

So you just need to acknowledge the missing recommends with '!' to
continue with the installation (or select a different solution).

Relevant entries in the NEWS file:

 * Actions involving unfulfilled Recommends invoke the resolver
   (Closes: #819636)

   With APT::Install-Recommends="true" (the default), actions resulting in
   unavailable Recommends (e.g., the recommended package is upgraded instead of
   remaining in the required version) invoke the resolver, for the user to take
   decision.

 * Invoke the resolver for unfulfilled Recommends only once (Closes: #822329)

   After the fix for #819636, the resolver was invoked after every action taken
   (in curses mode) to see if there were any unfulfilled dependencies.  This is
   too slow for some people/systems, so this is now only invoked will full
   check of dependencies (Recommends / "soft deps") before the final action.


So marking as +wontfix (for the lack of not-a-bug).


Cheers.
--
Manuel A. Fernandez Montecelo 

___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Processed: Re: aptitude: refuses to upgrade packages, 'g' says "Actions: no changes"

2017-03-06 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 + wontfix
Bug #836708 [aptitude] aptitude: refuses to upgrade packages, 'g' says 
"Actions: no changes"
Added tag(s) wontfix.
> close -1
Bug #836708 [aptitude] aptitude: refuses to upgrade packages, 'g' says 
"Actions: no changes"
Marked Bug as done

-- 
836708: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836708
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#841506: aptitude: cannot reinstall package available as update

2017-03-06 Thread Manuel A. Fernandez Montecelo 

Control: tags -1 + moreinfo


Hi Jonas,

2016-10-21 11:22 Jonas Smedegaard:

Package: aptitude
Version: 0.8.3-1+b1
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Aptitude has thrown me into limbo (hence severity important):

A kernel update failed (ran out of space in /boot, and/or bugs in kernel
hooks for sicherboot), flagging it as needing a reinstall.

Choosing "L" to reinstall and then "G", is refused with (in danish, on
my system) a message saying that no packages will be installed, removed
or upgraded, some packages could be upgraded, and I should press "U" to
do that.

Seems that check is missing the option of reinstall in its logic.


I think that the problem might be that it cannot use the same version of
the package to download, if it's not available in the list of packages,
so it cannot do nothing, other than suggesting to upgrade.

Do you remember if it allowed you to fix the system by using "+"
(install or upgrade) instead?


(Also, it would be helpful to include the exact message, and if possible
in english --LANG=C aptitude--, because it's sometimes difficult to
pinpoint the exact source of the code complaining)


Cheers.
--
Manuel A. Fernandez Montecelo 

___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Processed: Re: aptitude: cannot reinstall package available as update

2017-03-06 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 + moreinfo
Bug #841506 [aptitude] aptitude: cannot reinstall package available as update
Added tag(s) moreinfo.

-- 
841506: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#855543: clarify configuration files on man page

2017-03-06 Thread Manuel A. Fernandez Montecelo 

Control: tags -1 + wontfix
Control: close -1

Hi,

2017-02-20 00:31 積丹尼 Dan Jacobson:

Package: aptitude
Version: 0.8.5-1
Severity: wishlist
File: /usr/share/man/man8/aptitude-curses.8.gz

Man page says

   /etc/apt/apt.conf, /etc/apt/apt.conf.d/*, ~/.aptitude/config
  The configuration files for aptitude.  ~/.aptitude/config overrides
  /etc/apt/apt.conf. See apt.conf(5) for documentation of the format
  and contents of these files.

it should also say if it overrides /etc/apt/apt.conf.d/* and if
overrides means "is read after" or "is only read instead of".


This is documented in in apt.conf, in the top "DESCRIPTION", as
mentioned in the documentation, and it basically depends on the
implementation details of (lib)apt.

For aptitude, ~/.aptitude/config is read afterwards.  I don't think that
whether is read after or instead is an important detail or has any
material consequence from a high-level point of view, and it can change
over time, and I haven't found examples which document things to this
level... so closing as +wontfix as well.


--
Manuel A. Fernandez Montecelo 

___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Processed: Re: clarify configuration files on man page

2017-03-06 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 + wontfix
Bug #855543 [aptitude] clarify configuration files on man page
Added tag(s) wontfix.
> close -1
Bug #855543 [aptitude] clarify configuration files on man page
Marked Bug as done

-- 
855543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855543
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#834967: say -t is different than /

2017-03-06 Thread Manuel A. Fernandez Montecelo 

Control: tags -1 + wontfix
Control: close -1


Hi,

2016-08-21 06:21 積丹尼 Dan Jacobson:

Package: aptitude
Version: 0.8.3-1
Severity: wishlist
File: /usr/share/man/man8/aptitude-curses.8.gz

At

  -t , --target-release 
  Set the release from which packages should be installed. For
  instance, "aptitude -t experimental ..."  will install packages
  from the experimental distribution unless you specify otherwise.

  This will affect the default candidate version of packages
  according to the rules described in apt_preferences(5).

  This corresponds to the configuration item APT::Default-Release.

please remind the user that -t is not the same as "/"

  To select a particular version of the package, append "="
  to the package name: for instance, "aptitude install apt=0.3.1".
  Similarly, to select a package from a particular archive, append
  "/" to the package name: for instance, "aptitude install
  apt/experimental". You cannot specify both an archive and a version
  for a package.


This is documented in apt_preferences, as referred in the aptitude
documentation.  One sets the default release to get packages from the
given release with a given priority, the other only select the given
version to upgrade a package, while leaving the rest at the same
priority as defined in config files.

I think that the current documentation is correct, thus closing as
+wontfix.



and that they should use "/" for cases like:
[...]
# aptitude -t unstable reinstall $@
The following packages will be REINSTALLED:
 midori


I am not sure what you want to achieve there, but the appropriate action
depends if one wants to only consider a given version of a package or to
install/upgrade several packages from a different suite, so there's no
right rule for all cases.

In particular, it doesn't seem to make much sense to me to attempt to
reinstall a package passing neither -t suite nor /suite, even if
aptitude allows that, because conceptually "reinstall" is mostly to
install the same version again.

But as usual with aptitude, it doesn't attempt to limit the possibility
to do slightly or outright odd things :)

--
Manuel A. Fernandez Montecelo 

___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Processed: Re: say -t is different than /

2017-03-06 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 + wontfix
Bug #834967 [aptitude] say -t is different than /
Added tag(s) wontfix.
> close -1
Bug #834967 [aptitude] say -t is different than /
Marked Bug as done

-- 
834967: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834967
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

Re: [Aptitude-devel] Please giveback aptitude/0.8.6-1 on mips64el

2017-03-06 Thread James Cowgill 
Hi,

On 06/03/17 20:23, Axel Beckert wrote:
> Hi James,
> 
> James Cowgill wrote:
>>> https://buildd.debian.org/status/fetch.php?pkg=aptitude&arch=mips64el&ver=0.8.6-1&stamp=1488829841&raw=0
>>>ackage tracker
This package tracker is better than the old one on many aspects (easy to
extend, more dynamic, responsive, packed with new features such as
subscription management on the web, team subscriptions, etc.) but should
you find some features that are lacking or some other problems, then
please file bug reports against the tracker.debian.org pseudo-package.
Also don't hesitate to help us by contributing patches for those issues.

Not convinced? Go back to the old package tracking system.
>>> Again some tool in the documentation tool chain segfaults on mips64el.
>>
>> Done.
> 
> Thanks for the prompt reaction!
> 
>> This bug in libxml2 is Loongson specific so it will only happen on
>> some buildds.
> 
> Fits with our observation. Usually when the package is later build on
> a different buildd, then it builds fine.
> 
> But I can't find any such bug on
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libxml2
> Do you know where I can find the according bug report?

Sorry, I think I phrased that wrong - there may not be a bug in libxml2.
It's been known for some time that the Loongsons have issues with
certain newer MIPS instructions (as used on mips64el). I'm not sure if
this bug has ever been fully investigated, but since it only happened on
Loongson I think it was just written off as a hardware glitch.

Yunqiang, did you ever look into it (only asking because you appear to
be a maintainer of libxml2)?

Thanks,
James



signature.asc
Description: OpenPGP digital signature
___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

Re: [Aptitude-devel] Please giveback aptitude/0.8.6-1 on mips64el

2017-03-06 Thread Axel Beckert 
Hi James,

James Cowgill wrote:
> > https://buildd.debian.org/status/fetch.php?pkg=aptitude&arch=mips64el&ver=0.8.6-1&stamp=1488829841&raw=0
> > 
> > Again some tool in the documentation tool chain segfaults on mips64el.
> 
> Done.

Thanks for the prompt reaction!

> This bug in libxml2 is Loongson specific so it will only happen on
> some buildds.

Fits with our observation. Usually when the package is later build on
a different buildd, then it builds fine.

But I can't find any such bug on
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libxml2
Do you know where I can find the according bug report?

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#613276: aptitude didn't mark an automatically installed package as automatically installed

2017-03-06 Thread Manuel A. Fernandez Montecelo 


Control: close -1


Hi Josh and Ian,

2011-02-13 21:44 Josh Triplett:

Package: aptitude
Version: 0.6.3-3.2
Severity: normal

In doing an upgrade from lenny to squeeze, I noticed that diffutils and
isc-dhcp-client got automatically installed due to dependencies from
diff and dhcp3-client respectively, but neither package got marked as
automatically installed.


2012-04-10 22:45 Ian Zimmerman:

Package: aptitude
Version: 0.6.6-1
Followup-For: Bug #613276

The same happens for me during a routine weekly update of wheezy, with
package libatk-wrapper-java-jni selected explicitly, and gconf-service +
libgconf-2-4 selected for me by aptitude, but not marked as
dependencies.


Specially during 2015 and 2016 I was working on improving the handling
of automatic flags, which had been getting worse in the previous years,
due to slight misadjustments between [lib]apt and aptitude growing apart
over time.

In particular, I tested this upgrading from old iceweasel to the new
iceweasel which depends on firefox-esr, and it seems to work fine in all
cases when I upgrade (firefox-esr is always marked as automatically
installed).

So I think that this is fixed, closing now, but if you still detect such
problems please reopen or submit a new bug report.


Cheers.
--
Manuel A. Fernandez Montecelo 

___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Processed: Re: aptitude didn't mark an automatically installed package as automatically installed

2017-03-06 Thread Debian Bug Tracking System 
Processing control commands:

> close -1
Bug #613276 [aptitude] aptitude didn't mark an automatically installed package 
as automatically installed
Marked Bug as done

-- 
613276: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613276
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

Re: [Aptitude-devel] Please giveback aptitude/0.8.6-1 on mips64el

2017-03-06 Thread James Cowgill 
Hi,

On 06/03/17 20:09, Axel Beckert wrote:
> Dear mips64el Buildd Admins,
> 
> can you please giveback aptitude/0.8.6-1 on mips64el?
> 
> Axel Beckert wrote on 25. Jan. 2017:
>> According to
>> https://buildd.debian.org/status/fetch.php?pkg=aptitude&arch=mips64el&ver=0.8.5-1&stamp=1485311229&raw=0
>> something (probably xsltproc) segfaulted while building parts of the
>> documentation (which obviously worked fine on other architectures and
>> is architecture-independent).
>>
>> Even though it's no more mentioned in the /topic of #debian-devel, I
>> assume that's of the recently shown up build problems on mips64el.
> 
> Same story again with 0.8.6-1:
> 
> https://buildd.debian.org/status/fetch.php?pkg=aptitude&arch=mips64el&ver=0.8.6-1&stamp=1488829841&raw=0
> 
> Again some tool in the documentation tool chain segfaults on mips64el.

Done. This bug in libxml2 is Loongson specific so it will only happen on
some buildds.

Thanks,
James



signature.asc
Description: OpenPGP digital signature
___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Please giveback aptitude/0.8.6-1 on mips64el (was: Please giveback aptitude/0.8.5-1 on mips64el)

2017-03-06 Thread Axel Beckert 
Dear mips64el Buildd Admins,

can you please giveback aptitude/0.8.6-1 on mips64el?

Axel Beckert wrote on 25. Jan. 2017:
> According to
> https://buildd.debian.org/status/fetch.php?pkg=aptitude&arch=mips64el&ver=0.8.5-1&stamp=1485311229&raw=0
> something (probably xsltproc) segfaulted while building parts of the
> documentation (which obviously worked fine on other architectures and
> is architecture-independent).
> 
> Even though it's no more mentioned in the /topic of #debian-devel, I
> assume that's of the recently shown up build problems on mips64el.

Same story again with 0.8.6-1:

https://buildd.debian.org/status/fetch.php?pkg=aptitude&arch=mips64el&ver=0.8.6-1&stamp=1488829841&raw=0

Again some tool in the documentation tool chain segfaults on mips64el.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE


signature.asc
Description: Digital signature
___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Processed: Re: Bug#573626: Bug#573626: Bug#573626: aptitude: Terrible Interactive Search Performance

2017-03-06 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 + wontfix
Bug #573626 [aptitude] Terrible Interactive Search Performance
Added tag(s) wontfix.
> close -1
Bug #573626 [aptitude] Terrible Interactive Search Performance
Marked Bug as done

-- 
573626: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#836265: marked as done (aptitude: keeps reselecting sysvinit)

2017-03-06 Thread Debian Bug Tracking System 
Your message dated Mon, 6 Mar 2017 20:30:54 +0100
with message-id <20170306193052.uaya2vnqjpn4r...@reva.itsari.org>
and subject line Re: Bug#836265: aptitude: keeps reselecting sysvinit
has caused the Debian Bug report #836265,
regarding aptitude: keeps reselecting sysvinit
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
836265: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aptitude
Version: 0.8.3-1

On every "mark upgradeable", I find myself with sysvinit selected for install 
and not
marked as automatically selected (and subsequently I manually request for it 
not to be
installed).

The only dependency on it comes from libguestfs0, which depends on "systemd | 
sysvinit",
with systemd being already installed, so it looks like sysvinit has no valid 
reason to
be pulled - except maybe that this transitional package is marked essential, 
which is
probably a bug it itself, but can probably explain the behavior.
--- End Message ---
--- Begin Message ---

Forgot to actually close, sorry for the noise.


--
Manuel A. Fernandez Montecelo --- End Message ---
___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Processed: Re: Bug#836265: aptitude: keeps reselecting sysvinit

2017-03-06 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 - moreinfo + wontfix
Bug #836265 [aptitude] aptitude: keeps reselecting sysvinit
Removed tag(s) moreinfo.
Bug #836265 [aptitude] aptitude: keeps reselecting sysvinit
Added tag(s) wontfix.

-- 
836265: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#836265: aptitude: keeps reselecting sysvinit

2017-03-06 Thread Manuel A. Fernandez Montecelo 

Control: tags -1 - moreinfo + wontfix


2016-09-01 12:24 Sven Joachim:



If so, the bug might be that aptitude considers any version essential
even if only a non-candidate version is marked as essential.


Note that apt behaves the same way, see #216768.  See also the changelog
entry for 0.8.1-1:

,
| aptitude (0.8.1-1) unstable; urgency=low
| [...]
| - Bug fixes:
|   * Install new Essential or Required packages with the commands
| "full-upgrade" (command line) and MarkUpgradable ('U' in the curses
| interface) (Closes: #555896, #757028)
`



2016-09-01 16:20 David Kalnischkies:

(I am "just" one of the libapt maintainer, but for me that falls in the
same category as the bugs about that against apt: "wontfix as long as it
isn't closed as not-a-bug-but-a-feature")



Yep, the feature above was implemented due to the bigger problem that
aptitude was not installing essential packages of newer releases
automatically.

I'm not willing to rework the code now to behave in the old way or to
consider the case originating from this bug report -- so closing as
+wontfix.


(Perhaps pinning can help with this case if it's annoying enough, it's
the only solution that comes from the top of my head).

--
Manuel A. Fernandez Montecelo 

___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#837946: closed by m...@debian.org (Manuel A. Fernandez Montecelo) (Bug#837946: fixed in aptitude 0.8.6-1)

2017-03-06 Thread Marcel Partap 
Haha how sad, now I can't even test it. With some in between use of apt-get the 
issue receded here even on 8.5. Thanks for fixing it though! 😀

___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#826783: marked as done (libapt-pkg5.0: aptitude aborts due to a fd leak)

2017-03-06 Thread Debian Bug Tracking System 
Your message dated Mon, 6 Mar 2017 20:08:45 +0100
with message-id <20170306190843.fwicvtdjc3yd6...@reva.itsari.org>
and subject line Re: libapt-pkg5.0: aptitude aborts due to a fd leak
has caused the Debian Bug report #826783,
regarding libapt-pkg5.0: aptitude aborts due to a fd leak
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
826783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapt-pkg5.0
Version: 1.2.12
Severity: normal

Dear Maintainer,

after trying to upgrade several packages from the KDE suite in aptitude, I got a
strange SIGABRT when trying to download them. Via gdb, I obtained
backtrace:

Program received signal SIGABRT, Aborted.
[Switching to Thread 0xab40 (LWP 8710)]
0xb773cdad in __kernel_vsyscall ()
(gdb) bt
#0  0xb773cdad in __kernel_vsyscall ()
#1  0xb6d5de26 in __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:55
#2  0xb6d5f3f7 in __GI_abort () at abort.c:89
#3  0xb6d9b2a0 in __libc_message (do_abort=2, fmt=0xb6e90ff3 "*** %s ***: %s 
terminated\n") at ../sysdeps/posix/libc_fatal.c:175
#4  0xb6e2aeb7 in __GI___fortify_fail (msg=0xb6e90f8a "buffer overflow 
detected") at fortify_fail.c:31
#5  0xb6e290b8 in __GI___chk_fail () at chk_fail.c:28
#6  0xb6e2adda in __fdelt_chk (d=1083) at fdelt_chk.c:25
#7  0xb75eeafe in pkgAcquire::SetFds(int&, fd_set*, fd_set*) () from 
/usr/lib/i386-linux-gnu/libapt-pkg.so.5.0
#8  0xb75f418f in pkgAcquire::Run(int) () from 
/usr/lib/i386-linux-gnu/libapt-pkg.so.5.0
#9  0x8045f2a9 in download_manager::do_download (this=0x84f96cd4) at 
../../../../src/generic/apt/download_manager.cc:35
#10 0x8012b8db in download_thread::operator() (this=0x84ff0df8) at 
../../src/download_thread.cc:226
#11 0x801fee7f in 
cwidget::threads::noncopy_bootstrap::operator() 
(this=0xa318) at /usr/include/cwidget/generic/threads/threads.h:279
#12 0x801febfd in 
cwidget::threads::thread::bootstrap
 > (p=0x84f771e0) at /usr/include/cwidget/generic/threads/threads.h:117
#13 0xb70cc2ce in start_thread (arg=0xab40) at pthread_create.c:334
#14 0xb6e1a23e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122

After googling the __fdelt_chk function, it seems to check that the
passed fd is less than FD_SETSIZE and abort otherwise. Fair enough, 1083
seems pretty high.

Then I looked at the file descriptors that were open:

debian:/mnt/extras/src# lsof -p $(pidof aptitude)
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
  Output information may be incomplete.
COMMAND   PID USER   FD   TYPE DEVICE SIZE/OFFNODE NAME
aptitude 2856 root  cwdDIR8,628672 2113538 /home/jirka  


   
aptitude 2856 root  rtdDIR8,6 4096   2 /


   
aptitude 2856 root  txtREG8,6  6610336 1770506 /usr/bin/aptitude-curses 


   
aptitude 2856 root  memREG8,6   149869 4096209 
/usr/share/locale/cs/LC_MESSAGES/libc.mo


aptitude 2856 root  memREG8,6 31813113 2080784 
/var/cache/apt/pkgcache.bin 


aptitude 2856 root  memREG8,646736  230569 
/lib/i386-linux-gnu/libnss_files-2.22.so


aptitude 2856 root  memREG8,696128  230332 
/lib/i386-linux-gnu/libnsl-2.22.so  


aptitude 2856 root  memREG8,6269

[Aptitude-devel] Processed: Re: aptitude internal error

2017-03-06 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 + moreinfo
Bug #855288 [aptitude] aptitude internal error
Added tag(s) moreinfo.

-- 
855288: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#855288: aptitude internal error

2017-03-06 Thread Manuel A. Fernandez Montecelo 

Control: tags -1 + moreinfo


--
Manuel A. Fernandez Montecelo 

___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#841875: marked as done (better message for build-dep error)

2017-03-06 Thread Debian Bug Tracking System 
Your message dated Mon, 06 Mar 2017 18:34:00 +
with message-id 
and subject line Bug#841875: fixed in aptitude 0.8.6-1
has caused the Debian Bug report #841875,
regarding better message for build-dep error
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
841875: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841875
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aptitude
Version: 0.8.3-1+b1
Severity: wishlist
File: /usr/bin/aptitude-curses

Please use a message like apt-get does.
# aptitude build-dep linux
Unable to find the source package for "linux"
Unable to apply some actions, aborting
# apt-get build-dep linux
Reading package lists... Done
E: You must put some 'source' URIs in your sources.list
--- End Message ---
--- Begin Message ---
Source: aptitude
Source-Version: 0.8.6-1

We believe that the bug you reported is fixed in the latest version of
aptitude, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 841...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Manuel A. Fernandez Montecelo  (supplier of updated aptitude 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 05 Mar 2017 23:19:57 +0100
Source: aptitude
Binary: aptitude aptitude-common aptitude-doc-cs aptitude-doc-en 
aptitude-doc-es aptitude-doc-fi aptitude-doc-fr aptitude-doc-it aptitude-doc-ja 
aptitude-doc-nl aptitude-doc-ru
Architecture: source all amd64
Version: 0.8.6-1
Distribution: unstable
Urgency: medium
Maintainer: Aptitude Development Team 
Changed-By: Manuel A. Fernandez Montecelo 
Description:
 aptitude   - terminal-based package manager
 aptitude-common - architecture independent files for the aptitude package 
manager
 aptitude-doc-cs - Czech manual for aptitude, a terminal-based package manager
 aptitude-doc-en - English manual for aptitude, a terminal-based package manager
 aptitude-doc-es - Spanish manual for aptitude, a terminal-based package manager
 aptitude-doc-fi - Finnish manual for aptitude, a terminal-based package manager
 aptitude-doc-fr - French manual for aptitude, a terminal-based package manager
 aptitude-doc-it - Italian manual for aptitude, a terminal-based package manager
 aptitude-doc-ja - Japanese manual for aptitude, a terminal-based package 
manager
 aptitude-doc-nl - Dutch manual for aptitude, a terminal-based package manager
 aptitude-doc-ru - Russian manual for aptitude, a terminal-based package manager
Closes: 831858 836567 837946 841347 841875 849370 852666 853037 854897 855329
Changes:
 aptitude (0.8.6-1) unstable; urgency=medium
 .
   [ Manuel A. Fernandez Montecelo ]
   * New upstream release. Please see /usr/share/aptitude/NEWS for a change
 log with more details.
 .
 - User visible changes:
   * [cmdline] Better message when there are no deb-src in sources.list
 (Closes: #841875)
 .
 - Bug fixes:
   * Use a more strict mask for comparison of dependency operators, thanks 
to
 Aaron M. Ucko for the initial patch (Closes: #836567, #837946, #849370)
   * Fix reading tag and their classification in subtrees (Closes: #853037)
   * Fix misdetection of auto-installed packages from apt
 (Closes: #831858, #841347)
 .
 - Translation updates:
   * ru.po: Russian translation by Lev Lamberov (Closes: #855329)
   * Dutch documentation translation by Frans Spiesschaert (Closes: #854897)
 .
 .
   * Remove wrong "From:" from contributor name in prev. changelog entry.
   * d/patches:
 - drop ftbfs-fix-french-doc.patch
 .
   [ Axel Beckert ]
   * Restrict build-dependency on google-mock to >= 1.8.0 as aptitude FTBFS
 with earlier versions since the adaptions for 1.8.0 in 0.8.4-1.
 (Closes: #852666)
Checksums-Sha1:
 2cd0ea536524eebc8a4e31eb4d9cbc6ebc1fe879 2990 aptitude_0.8.6-1.dsc
 e2b6237cdd3acc6cd8869dbaf6470e8cad805c91 4714728 aptitude_0.8.6.orig.tar.xz
 5c8a939b0511be877a4db3379c2d34656b128a3f 53184 aptitude_0.8.6-1.debian.tar.xz
 aa7705ceeb8d0d18543db4bbfa5fd12e9e441c0f 1587236 
aptitude-common_0.8.6-1_all.deb
 0a106be903adb0f081a9e9a13c796d47acb0d0ff 22809940 
aptitude-dbgsym_0.8.6-1_amd64.deb
 4fea0c534

[Aptitude-devel] Bug#855329: marked as done (aptitude: please, fix a minor mistake in Russian translation)

2017-03-06 Thread Debian Bug Tracking System 
Your message dated Mon, 06 Mar 2017 18:34:00 +
with message-id 
and subject line Bug#855329: fixed in aptitude 0.8.6-1
has caused the Debian Bug report #855329,
regarding aptitude: please, fix a minor mistake in Russian translation
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
855329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855329
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aptitude
Version: 0.8.5-1
Severity: minor
Tags: l10n patch

Dear Maintainer,

please, fix a minor mistake in Russian translation. Find the patch attached.

Cheers,
Lev Lamberov


-- Package-specific info:
Terminal: rxvt-unicode
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.8.5
Compiler: g++ 6.3.0 20170121
Compiled against:
  apt version 5.0.1
  NCurses version 6.0
  libsigc++ version: 2.10.0
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.0.20161126
  cwidget version: 0.5.17
  Apt version: 5.0.1

aptitude linkage:
linux-vdso.so.1 (0x7ffca5c07000)
libapt-pkg.so.5.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 
(0x7fbd5b1ad000)
libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 
(0x7fbd5af7d000)
libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 
(0x7fbd5ad4d000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7fbd5ab45000)
libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 
(0x7fbd5a845000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7fbd5a53d000)
libboost_iostreams.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.62.0 (0x7fbd5a325000)
libboost_filesystem.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.62.0 (0x7fbd5a105000)
libboost_system.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.62.0 (0x7fbd59efd000)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7fbd59ae5000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fbd598c5000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7fbd5953d000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fbd59235000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7fbd5901d000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fbd58c7d000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fbd58a75000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7fbd5885d000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fbd5863d000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7fbd5842d000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7fbd58205000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7fbd57fed000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fbd57de5000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7fbd57bdd000)
/lib64/ld-linux-x86-64.so.2 (0x55722ab95000)

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages aptitude depends on:
ii  aptitude-common0.8.5-1
ii  libapt-pkg5.0  1.4~rc1
ii  libboost-filesystem1.62.0  1.62.0+dfsg-4
ii  libboost-iostreams1.62.0   1.62.0+dfsg-4
ii  libboost-system1.62.0  1.62.0+dfsg-4
ii  libc6  2.24-9
ii  libcwidget3v5  0.5.17-4+b1
ii  libgcc11:6.3.0-6
ii  libncursesw5   6.0+20161126-1
ii  libsigc++-2.0-0v5  2.10.0-1
ii  libsqlite3-0   3.16.2-2
ii  libstdc++6 6.3.0-6
ii  libtinfo5  6.0+20161126-1
ii  libxapian301.4.3-1

Versions of packages aptitude recommends:
ii  libparse-debianchangelog-perl  1.2.0-12
ii  sensible-utils 0.0.9

Versions of packages aptitude suggests:
pn  apt-xapian-index
ii  aptitude-doc-en [aptitude-doc]  0.8.5-1
ii  aptitude-doc-ru [aptitude-doc]  0.8.5-1
ii  debtags 2.1.2
ii  tasksel 3.39

-- no debconf information
Fro

[Aptitude-devel] Bug#853037: marked as done (aptitude: debtags view: duplicate tags, some with missing description)

2017-03-06 Thread Debian Bug Tracking System 
Your message dated Mon, 06 Mar 2017 18:34:00 +
with message-id 
and subject line Bug#853037: fixed in aptitude 0.8.6-1
has caused the Debian Bug report #853037,
regarding aptitude: debtags view: duplicate tags, some with missing description
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
853037: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853037
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aptitude
Version: 0.8.5-1
Severity: normal

When I go to the debtags view I get some duplicate tags, where one copy
of the tag has no description and the other has one. There are some
examples below but there are a lot more in other facets.

--\ accessibility - Accessibility Support (285)
  --- input
  --- input - Input Systems (131)
  --- speech
  --- speech - Speech Synthesis (100)
--\ admin - System Administration (2323)
  --- boot
  --- boot - System Boot (94)
  --- cluster
  --- cluster - Clustering (43)
  --- filesystem
  --- filesystem - Filesystem Tool (199)
  --- install
  --- install - System Installation (19)
--\ culture - Culture (1506)
  --- TODO  

 
  --- TODO - Need an extra tag (163)
  --- chinese
  --- chinese - Chinese (82)
  --- japanese
  --- japanese - Japanese (198)
  --- korean
  --- korean - Korean (38)
  --- norwegian
  --- norwegian - Norwegian (16)
  --- nynorsk
  --- nynorsk - Norwegian Nynorsk (7)
  --- slovak
  --- slovak - Slovak (18)
  --- taiwanese
  --- taiwanese - Taiwanese (33)
--\ devel - Software Development (19817)

 
  --- TODO
  --- TODO - Need an extra tag (59)
  --- buildtools
  --- buildtools - Build Tool (140)
  --- code-generator
  --- code-generator - Code Generation (119)
  --- compiler
  --- compiler - Compiler (124)
...

-- Package-specific info:
Terminal: xterm-256color
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.8.5
Compiler: g++ 6.3.0 20170121
Compiled against:
  apt version 5.0.1
  NCurses version 6.0
  libsigc++ version: 2.10.0
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.0.20161126
  cwidget version: 0.5.17
  Apt version: 5.0.1

aptitude linkage:
linux-vdso.so.1 (0x7fff7a779000)
libapt-pkg.so.5.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 
(0x7f62e675d000)
libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 
(0x7f62e652d000)
libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 
(0x7f62e6303000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f62e60fc000)
libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 
(0x7f62e5dff000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f62e5af5000)
libboost_iostreams.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.62.0 (0x7f62e58dd000)
libboost_filesystem.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.62.0 (0x7f62e56c4000)
libboost_system.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.62.0 (0x7f62e54c)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7f62e50af000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f62e4e92000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f62e4b0f000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f62e480b000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f62e45f4000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f62e4256000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f62e4052000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7f62e3e3b000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f62e3c1f000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f62e3a0f000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f62e37e9000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7f62e35d7000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f62e33cf000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f62e31c8000)
/lib64/ld-linux-x86-64.so

[Aptitude-devel] Bug#852666: marked as done (aptitude: FTBFS with Google Mock releases before 1.8.0)

2017-03-06 Thread Debian Bug Tracking System 
Your message dated Mon, 06 Mar 2017 18:34:00 +
with message-id 
and subject line Bug#852666: fixed in aptitude 0.8.6-1
has caused the Debian Bug report #852666,
regarding aptitude: FTBFS with Google Mock releases before 1.8.0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
852666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aptitude
Version: 0.8.5

distribution: Ubuntu 16.10 yakkety
sources: https://anonscm.debian.org/cgit/aptitude/aptitude.git
tag: 0.8.5
branch: master

echo ---
echo Checking Build Dependencies
echo ---
apt-get update
apt-get build-dep aptitude

echo 
echo Cleaning
echo 
cd git-aptitude
git-reset-clean-pull-checkout.sh $branch $tag

echo ---
echo Configuring
echo ---
export GTHREAD_LIBS='-L/usr/lib/x86_64-linux-gnu'
export VTE_LIBS='-L/usr/lib/x86_64-linux-gnu'
export CXXFLAGS="-std=c++14"

export NOCONFIGURE=yes
./autogen.sh

##
# GTK & QT frontends are unmaintained:
# --enable-gtk \
# --enable-qt \
# The following is also buggy
# --enable-resolver-sanity-checks \
##
./configure   --enable-reload-cache \
--prefix=/usr --sysconfdir=/etc
--localstatedir=/var

leads to:

checking how to link gmock... configure: error: Can't figure out where
Google Mock lives; either install the google-mock package or place the
library in the link path

However:
===
1) *It is already installed*:
# apt-cache policy google-mock
google-mock:
  Installed: 1.7.0-18092013-2.1

2) *There is no library in the package; intalled files:*
/.
/usr
/usr/bin
/usr/bin/gmock_gen
/usr/include
/usr/include/gmock
/usr/include/gmock/gmock-actions.h
/usr/include/gmock/gmock-cardinalities.h
/usr/include/gmock/gmock-generated-actions.h
/usr/include/gmock/gmock-generated-actions.h.pump
/usr/include/gmock/gmock-generated-function-mockers.h
/usr/include/gmock/gmock-generated-function-mockers.h.pump
/usr/include/gmock/gmock-generated-matchers.h
/usr/include/gmock/gmock-generated-matchers.h.pump
/usr/include/gmock/gmock-generated-nice-strict.h
/usr/include/gmock/gmock-generated-nice-strict.h.pump
/usr/include/gmock/gmock-matchers.h
/usr/include/gmock/gmock-more-actions.h
/usr/include/gmock/gmock-more-matchers.h
/usr/include/gmock/gmock-spec-builders.h
/usr/include/gmock/gmock.h
/usr/include/gmock/internal
/usr/include/gmock/internal/gmock-generated-internal-utils.h
/usr/include/gmock/internal/gmock-generated-internal-utils.h.pump
/usr/include/gmock/internal/gmock-internal-utils.h
/usr/include/gmock/internal/gmock-port.h
/usr/share
/usr/share/doc
/usr/share/doc/google-mock
/usr/share/doc/google-mock/CONTRIBUTORS
/usr/share/doc/google-mock/README.Debian
/usr/share/doc/google-mock/README.gz
/usr/share/doc/google-mock/changelog.Debian.gz
/usr/share/doc/google-mock/copyright
/usr/share/gmock
/usr/share/gmock/cpp
/usr/share/gmock/cpp/__init__.py
/usr/share/gmock/cpp/ast.py
/usr/share/gmock/cpp/gmock_class.py
/usr/share/gmock/cpp/keywords.py
/usr/share/gmock/cpp/tokenize.py
/usr/share/gmock/cpp/utils.py
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/gmock_gen.1.gz
/usr/src
/usr/src/gmock
/usr/src/gmock/CMakeLists.txt
/usr/src/gmock/src
/usr/src/gmock/src/gmock-all.cc
/usr/src/gmock/src/gmock-cardinalities.cc
/usr/src/gmock/src/gmock-internal-utils.cc
/usr/src/gmock/src/gmock-matchers.cc
/usr/src/gmock/src/gmock-spec-builders.cc
/usr/src/gmock/src/gmock.cc
/usr/src/gmock/src/gmock_main.cc

3) *trying Include path:*
./configure   --enable-reload-cache \
--with-google-mock=/usr/include/gmock \
--prefix=/usr --sysconfdir=/etc --localstatedir=/var

leads to the same error because the option is not recognized:
configure: WARNING: unrecognized options: --with-google-mock

4) *trying additional compiler flag:*
../configure   CXXFLAGS="-I/usr/include/gmock" \
 --enable-reload-cache \
 --prefix=/usr --sysconfdir=/etc --localstatedir=/var

leads to the same error.
Same with CPPFLAGS.

What could be done to work around this issue?
Regards.
-- 
Jean-Christophe
--- End Message ---
--- Begin Message ---
Source: aptitude
Source-Version: 0.8.6-1

We believe that the bug you reported is fixed in th

[Aptitude-devel] Bug#849370: marked as done (aptitude: Aptitude crashes with SIGABRT on install command)

2017-03-06 Thread Debian Bug Tracking System 
Your message dated Mon, 06 Mar 2017 18:34:00 +
with message-id 
and subject line Bug#849370: fixed in aptitude 0.8.6-1
has caused the Debian Bug report #849370,
regarding aptitude: Aptitude crashes with SIGABRT on install command
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
849370: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849370
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aptitude
Version: 0.8.3-1+b2
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

Aptitude crashes with SIGABRT on apt-get install command line or in the
"G" command in curses mode.

Attached the gdb backtrace.

Regards

Jean-Luc


- -- Package-specific info:
Terminal: xterm-256color
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.8.3
Compiler: g++ 6.2.0 20161103
Compiled against:
  apt version 5.0.0
  NCurses version 6.0
  libsigc++ version: 2.10.0
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.0.20161126
  cwidget version: 0.5.17
  Apt version: 5.0.1

aptitude linkage:
linux-vdso.so.1 (0x7ffcd1d8c000)
libapt-pkg.so.5.0 => /lib/x86_64-linux-gnu/libapt-pkg.so.5.0 
(0x7fce635c8000)
libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 
(0x7fce63398000)
libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 
(0x7fce6316e000)
libsigc-2.0.so.0 => /lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7fce62f67000)
libcwidget.so.3 => /lib/x86_64-linux-gnu/libcwidget.so.3 
(0x7fce62c6a000)
libsqlite3.so.0 => /lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7fce62961000)
libboost_iostreams.so.1.62.0 => 
/lib/x86_64-linux-gnu/libboost_iostreams.so.1.62.0 (0x7fce62749000)
libboost_filesystem.so.1.62.0 => 
/lib/x86_64-linux-gnu/libboost_filesystem.so.1.62.0 (0x7fce6253)
libboost_system.so.1.62.0 => 
/lib/x86_64-linux-gnu/libboost_system.so.1.62.0 (0x7fce6232c000)
libxapian.so.30 => /lib/x86_64-linux-gnu/libxapian.so.30 
(0x7fce61f1e000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fce61d01000)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7fce6197d000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fce61679000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7fce61462000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fce610c4000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fce60ec)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7fce60ca9000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fce60a8d000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7fce6087d000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7fce60657000)
liblz4.so.1 => /lib/x86_64-linux-gnu/liblz4.so.1 (0x7fce60445000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fce6023d000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7fce60036000)
/lib64/ld-linux-x86-64.so.2 (0x560ffd83b000)

- -- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (600, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-i7-0.1 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages aptitude depends on:
ii  aptitude-common0.8.3-1
ii  libapt-pkg5.0  1.4~beta2
ii  libboost-filesystem1.62.0  1.62.0+dfsg-4
ii  libboost-iostreams1.62.0   1.62.0+dfsg-4
ii  libboost-system1.62.0  1.62.0+dfsg-4
ii  libc6  2.24-8
ii  libcwidget3v5  0.5.17-4+b1
ii  libgcc11:6.2.1-7
ii  libncursesw5   6.0+20161126-1
ii  libsigc++-2.0-0v5  2.10.0-1
ii  libsqlite3-0   3.15.2-2
ii  libstdc++6 6.2.1-7
ii  libtinfo5  6.0+20161126-1
ii  libxapian301.4.1-1

Versions of packages aptitude recommends:
ii  libparse-debianchangelog-perl  1.2.0-12
ii  sensible-utils 0.0.9

Versions of packages aptitude suggests:
ii  apt-xapian-index0.49
ii  aptitude-doc-en [aptitude-doc]  0.8.3-1
ii  aptitude-doc-fr [aptitude-doc]  0.8.3-1
ii  debtags 2.1.2

[Aptitude-devel] Bug#841347: marked as done (packages are not marked as auto "i A" in aptitude)

2017-03-06 Thread Debian Bug Tracking System 
Your message dated Mon, 06 Mar 2017 18:34:00 +
with message-id 
and subject line Bug#841347: fixed in aptitude 0.8.6-1
has caused the Debian Bug report #841347,
regarding packages are not  marked as auto "i A" in aptitude
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
841347: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt
Version: 1.3.1
Severity: normal

Hi!

I typically use mk-build-depends -i to install the build dependencies of
a package.

Those $foo-build-depends pile up and from time to time I use aptitude
(in interactive mode) to remove them. But none of the dependencies are
actually removed then. Afaics, they are all in state "i" instead of
"i A".

Interestingly, if I remove the $foo-build-depends package via apt, the
packages are properly marked for autoremoval.

Is there some broken interaction between aptitude and apt regarding the
auto state? I vaguely remember that this worked in the past.

If you want to reproduce the problem, try the following, with the
attached deb:

$ apt file install ./gtk+3.0-build-deps_3.22.1-4_amd64.deb
[install lots of stuff]
$ apt remove gtk+3.0-build-deps
[lists lots of packages as autoinstalled]
$ apt autoremove
[removes lots of stuff]

$ apt file install ./gtk+3.0-build-deps_3.22.1-4_amd64.deb
[install lots of stuff]
$ aptitude remove gtk+3.0-build-deps
[removes gtk+3.0-build-deps]
$ apt autoremove
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.



Regards,
Michael



-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "true";
APT::Install-Suggests "0";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^linux-image-4\.7\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-headers-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.7\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.7\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.7\.0-1-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.7\.0-1-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.7\.0-1-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.7\.0-1-amd64$";
APT::NeverAutoRemove:: "^.*-modules-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.7\.0-1-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.7\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.7\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-tools-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^linux-tools-4\.7\.0-1-amd64$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-image";
APT::VersionedKernelPackages:: "linux-headers";
APT::VersionedKernelPackages:: "linux-image-extra";
APT::VersionedKernelPackages:: "linux-signed-image";
APT::VersionedKernelPackages:: "kfreebsd-image";
APT::VersionedKernelPackages:: "kfreebsd-headers";
APT::VersionedKernelPackages:: "gnumach-image";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::VersionedKernelPackages:: "linux-backports-modules-.*";
APT::VersionedKernelPackages:: "linux-tools";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "contrib/metapackages";
APT::Never-MarkAuto-Sections:: "non-free/metapackages";
APT::Never-MarkAuto-Sections:: "restricted/metapackages";
APT::Never-MarkAuto-Sections:: "universe/metapackages";
APT::Never-MarkAuto-Sections:: "multiverse/metapackages";
APT::Move-Autobit-Sections "";
APT::Move-Autobit-Sections:: "oldlibs";
APT::Move-Autobit-Sections:: "contrib/oldlibs";
APT::Move-Autobit-Sections:: "non-free/oldlibs";
APT::Move-Autobit-Sections:: "restricted/oldlibs";
APT::Move-Autobit-Sections:: "universe/oldlibs";
APT::Move-Autobit-Sections:: "multiverse/oldlibs";
APT::Update "";
APT::Update::Post-Invoke-

[Aptitude-devel] Bug#837946: marked as done (aptitude: actions causing »aptitude received signal SIGABRT, =?UTF-8?Q?Aborted.=C2=AB?=)

2017-03-06 Thread Debian Bug Tracking System 
Your message dated Mon, 06 Mar 2017 18:34:00 +
with message-id 
and subject line Bug#837946: fixed in aptitude 0.8.6-1
has caused the Debian Bug report #837946,
regarding aptitude: actions causing »aptitude received signal SIGABRT, Aborted.«
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
837946: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837946
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aptitude
Version: 0.8.2-1+b1
Severity: normal

There is one sole action saved from a previous run:
# ci  kernel linux-image-4.6.0-1-amd64:amd64
"Cancel pending actions" does not deselect actually cancel it, holding the
package does. Either way (action canceled or still pending), when next pressing
'g' to preview, aptitude crashes with:

Thread 1 "aptitude" received signal SIGABRT, Aborted.
0xf776ad09 in __kernel_vsyscall ()
@@gdb> bt
@gdb> #0  0xf776ad09 in __kernel_vsyscall ()
#1  0xf6d08c19 in __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#2  0xf6d0a117 in __GI_abort () at abort.c:89
#3  0x5676f8d9 in subsumes (d2=..., d1=...) at
../../../../src/generic/apt/apt.cc:1182
#4  or_group_subsumes (d1=..., d2=..., cache=) at
../../../../src/generic/apt/apt.cc:1205
#5  0x567715d2 in internal_is_interesting_dep (cache=0x5834cff8, d=...) at
../../../../src/generic/apt/apt.cc:1303
#6  is_interesting_dep (d=..., cache=0x5834cff8) at
../../../../src/generic/apt/apt.cc:1344
#7  0x56794e35 in aptitude_resolver_version::dep_iterator::applicable (dep=...,
prv=..., prv_open=false, cache=0x5834cff8) at
../../../../src/generic/apt/aptitude_resolver_universe.cc:283
#8  0x5678e2aa in aptitude_resolver_version::dep_iterator::applicable
(this=0xffdb1208) at
../../../../src/generic/apt/aptitude_resolver_universe.cc:302
#9  0x5678e389 in aptitude_resolver_version::dep_iterator::normalize
(this=0xffdb1208) at
../../../../src/generic/apt/aptitude_resolver_universe.cc:317
#10 0x5678f665 in aptitude_resolver_version::dep_iterator::operator++
(this=0xffdb1208) at
../../../../src/generic/apt/aptitude_resolver_universe.cc:529
#11 0x5687df87 in aptitude_universe::dep_iterator::operator++ (this=) at ../../../../src/generic/apt/aptitude_resolver_universe.h:1246
#12 generic_problem_resolver::generic_problem_resolver
(this=, _step_score=, _broken_score=, _unfixed_soft_score=, infinity=,
_full_solution_score=, _unfixed_soft_cost=...,
_future_horizon=, _initial_state=..., _universe=...) at
../../../../src/generic/problemresolver/problemresolver.h:3782
#13 0x5686cd0c in aptitude_resolver::aptitude_resolver (this=0x583427c8,
step_score=-10, broken_score=-100, unfixed_soft_score=-200, infinity=100,
resolution_score=50, unfixed_soft_cost=..., future_horizon=50,
_cost_settings=..., initial_installations=..., cache=0x5834cff8,
_policy=0x599b2240) at ../../../../src/generic/apt/aptitude_resolver.cc:731
#14 0x567e7091 in resolver_manager::create_resolver (this=0x5a866730) at
../../../../src/generic/apt/resolver_manager.cc:968
#15 0x567e9373 in resolver_manager::maybe_create_resolver (this=0x5a866730,
consider_policybroken=true) at
../../../../src/generic/apt/resolver_manager.cc:805
#16 0x567e9ce8 in resolver_manager::reset_resolver (this=,
consider_policybroken=) at
../../../../src/generic/apt/resolver_manager.cc:218
#17 0x566c3ba4 in do_package_run () at ../../src/ui.cc:1817
#18 0xf74c745c in cwidget::widgets::widget::handle_key(cwidget::config::key
const&) () from /usr/lib/i386-linux-gnu/libcwidget.so.3
#19 0xf7499b88 in
cwidget::widgets::passthrough::handle_key(cwidget::config::key const&) () from
/usr/lib/i386-linux-gnu/libcwidget.so.3
#20 0xf74cbb3b in cwidget::widgets::widget::dispatch_key(cwidget::config::key
const&) () from /usr/lib/i386-linux-gnu/libcwidget.so.3
#21 0xf747621c in cwidget::widgets::menubar::handle_key(cwidget::config::key
const&) () from /usr/lib/i386-linux-gnu/libcwidget.so.3
#22 0xf74cbb3b in cwidget::widgets::widget::dispatch_key(cwidget::config::key
const&) () from /usr/lib/i386-linux-gnu/libcwidget.so.3
#23 0xf743db51 in cwidget::toplevel::input_thread::get_input_event::dispatch()
() from /usr/lib/i386-linux-gnu/libcwidget.so.3
#24 0xf7434bef in cwidget::toplevel::mainloop(int) () from /usr/lib/i386-linux-
gnu/libcwidget.so.3
#25 0x566c3dae in ui_main () at ../../src/ui.cc:3124
#26 0x565ccf11 in main (argc=, argv=) at
../../src/main.cc:1402

Kinda stuck.
Downgrading to 0.8.2-1+b1 from 0.8.3 (also to install dbg symbols) did not
work. Backtrace is from the former version.



-- Package-specific info:
Terminal: screen-256color
$DISPLAY is set.
which aptitude: /usr/bin/aptitu

[Aptitude-devel] Bug#831858: marked as done (aptitude sets already auto-installed packages as manually installed)

2017-03-06 Thread Debian Bug Tracking System 
Your message dated Mon, 06 Mar 2017 18:33:59 +
with message-id 
and subject line Bug#831858: fixed in aptitude 0.8.6-1
has caused the Debian Bug report #831858,
regarding aptitude sets already auto-installed packages as manually installed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
831858: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831858
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aptitude
Version: 0.8.1-1
Severity: normal

After installing packages (having dependencies) with "apt" and running
aptitude, aptitude sometimes changes the auto-installed dependencies
to manually installed in the /var/lib/apt/extended_states file.

To reproduce, the problem, I did the following:

1. An upgrade with aptitude (this appears to be important).
/var/log/apt/history.log contains:

Start-Date: 2016-07-20  10:59:25
Upgrade: linux-doc-4.6:amd64 (4.6.3-1, 4.6.4-1), manpages:amd64 (4.06-1, 
4.07-1), libc6-dev-x32:amd64 (2.23-1, 2.23-2), linux-libc-dev:amd64 (4.6.3-1, 
4.6.4-1), libc6-dev-i386:amd64 (2.23-1, 2.23-2), libdv4:amd64 (1.0.0-10, 
1.0.0-11), libc6-dbg:amd64 (2.23-1, 2.23-2), libc6-dev:amd64 (2.23-1, 2.23-2), 
ruby-xmlparser:amd64 (0.7.3-2, 0.7.3-3), libc6:amd64 (2.23-1, 2.23-2), 
libc6:i386 (2.23-1, 2.23-2), locales:amd64 (2.23-1, 2.23-2), metacity:amd64 
(1:3.20.1.1-1, 1:3.20.2-1), ruby-unf-ext:amd64 (0.0.7.2-1+b2, 0.0.7.2-2), 
linux-headers-4.6.0-1-common:amd64 (4.6.3-1, 4.6.4-1), 
linux-headers-4.6.0-1-amd64:amd64 (4.6.3-1, 4.6.4-1), libinput-bin:amd64 
(1.3.1-1, 1.3.3-1), libc-l10n:amd64 (2.23-1, 2.23-2), libc-bin:amd64 (2.23-1, 
2.23-2), libc6-x32:amd64 (2.23-1, 2.23-2), libmetacity0:amd64 (1:3.20.1.1-1, 
1:3.20.2-1), metacity-common:amd64 (1:3.20.1.1-1, 1:3.20.2-1), libc6-i386:amd64 
(2.23-1, 2.23-2), linux-kbuild-4.6:amd64 (4.6.3-1, 4.6.4-1), ruby-unf:amd64 
(0.1.4-1, 0.1.4-2), manpages-dev:amd64 (4.06-1, 4.07-1), libc-dev-bin:amd64 
(2.23-1, 2.23-2), multiarch-support:amd64 (2.23-1, 2.23-2), glibc-doc:amd64 
(2.23-1, 2.23-2), linux-compiler-gcc-5-x86:amd64 (4.6.3-1, 4.6.4-1), 
linux-image-4.6.0-1-amd64:amd64 (4.6.3-1, 4.6.4-1), libinput10:amd64 (1.3.1-1, 
1.3.3-1)
End-Date: 2016-07-20  11:06:52

2. Purge packages with "apt" (the goal being to reproduce the problem
after reinstalling them). /var/log/apt/history.log contains:

Start-Date: 2016-07-20  11:07:48
Commandline: apt purge julia libopenlibm2 libjs-mathjax julia-doc libspqr2 
libdsfmt-19937-1 fonts-mathjax libjs-underscore sphinx-rtd-theme-common 
libpcre2-8-0 libopenblas-base libunwind8 julia-common libarpack2 
libopenspecfun1 libjs-modernizr libjs-sphinxdoc libutf8proc2
Purge: julia:amd64 (0.4.6-1+b1), libopenlibm2:amd64 (0.5.1+dfsg-1), 
libutf8proc2:amd64 (2.0.1-1), libjs-mathjax:amd64 (2.6.1-1), julia-doc:amd64 
(0.4.6-1), libspqr2:amd64 (1:4.5.3-1), libdsfmt-19937-1:amd64 (2.2.3+dfsg-3), 
fonts-mathjax:amd64 (2.6.1-1), libjs-underscore:amd64 (1.7.0~dfsg-1), 
sphinx-rtd-theme-common:amd64 (0.1.9-1), libpcre2-8-0:amd64 (10.21-1), 
libopenblas-base:amd64 (0.2.18-1), libunwind8:amd64 (1.1-4.1), 
julia-common:amd64 (0.4.6-1), libarpack2:amd64 (3.4.0-1), libopenspecfun1:amd64 
(0.5.2-1), libjs-modernizr:amd64 (2.6.2+ds1-1), libjs-sphinxdoc:amd64 (1.4.5-1)
End-Date: 2016-07-20  11:07:56

3. Reinstall the packages (with auto-installed dependencies) with
"apt". /var/log/apt/history.log contains:

Start-Date: 2016-07-20  11:08:36
Commandline: apt install julia julia-doc
Install: julia:amd64 (0.4.6-1+b1), libopenlibm2:amd64 (0.5.1+dfsg-1, 
automatic), libutf8proc2:amd64 (2.0.1-1, automatic), libjs-mathjax:amd64 
(2.6.1-1, automatic), julia-doc:amd64 (0.4.6-1), libspqr2:amd64 (1:4.5.3-1, 
automatic), libdsfmt-19937-1:amd64 (2.2.3+dfsg-3, automatic), 
fonts-mathjax:amd64 (2.6.1-1, automatic), libjs-underscore:amd64 (1.7.0~dfsg-1, 
automatic), sphinx-rtd-theme-common:amd64 (0.1.9-1, automatic), 
libpcre2-8-0:amd64 (10.21-1, automatic), libopenblas-base:amd64 (0.2.18-1, 
automatic), libunwind8:amd64 (1.1-4.1, automatic), julia-common:amd64 (0.4.6-1, 
automatic), libarpack2:amd64 (3.4.0-1, automatic), libopenspecfun1:amd64 
(0.5.2-1, automatic), libjs-modernizr:amd64 (2.6.2+ds1-1, automatic), 
libjs-sphinxdoc:amd64 (1.4.5-1, automatic)
End-Date: 2016-07-20  11:08:48

At this time, the "automatic" packages are marked as auto-installed
in /var/lib/apt/extended_states, i.e. with "Auto-Installed: 1".

But just after running aptitude as root with no arguments (just to
get the UI), for the above "automatic" packages, the Auto-Installed
field is changed to "Auto-Installed: 0".

-- Package-specific info:
Terminal: xterm-d

[Aptitude-devel] Bug#836567: marked as done (aptitude: [PATCH] aborts on encountering new DepCompareOp flags)

2017-03-06 Thread Debian Bug Tracking System 
Your message dated Mon, 06 Mar 2017 18:33:59 +
with message-id 
and subject line Bug#836567: fixed in aptitude 0.8.6-1
has caused the Debian Bug report #836567,
regarding aptitude: [PATCH] aborts on encountering new DepCompareOp flags
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
836567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aptitude
Version: 0.8.3-1
Severity: important
Tags: patch

Aptitude recently started aborting under some circumstances, notably
when asked to calculate safe upgrades on my multiarch-enabled system.
The aborts turned out to occur on line 1182 of src/generic/apt/apt.cc,
with t1 values that didn't match any cases because the ArchSpecific
flag was originally set and never masked out.  I've gotten good
results by masking out *all* high bits when setting t1 and t2, per the
below patch, but haven't examined the code closely enough to be
certain that it's correct or sufficient.

Could you please take a look?

Thanks!

diff --git a/src/generic/apt/apt.cc b/src/generic/apt/apt.cc
index 1850825..c384f9a 100644
--- a/src/generic/apt/apt.cc
+++ b/src/generic/apt/apt.cc
@@ -1141,8 +1141,8 @@ static bool subsumes(const pkgCache::DepIterator &d1,
   if(!d2.TargetVer())
return false;
 
-  pkgCache::Dep::DepCompareOp t1 = (pkgCache::Dep::DepCompareOp) 
(d1->CompareOp &~ pkgCache::Dep::Or);
-  pkgCache::Dep::DepCompareOp t2 = (pkgCache::Dep::DepCompareOp) 
(d2->CompareOp &~ pkgCache::Dep::Or);
+  pkgCache::Dep::DepCompareOp t1 = (pkgCache::Dep::DepCompareOp) 
(d1->CompareOp % pkgCache::Dep::Or);
+  pkgCache::Dep::DepCompareOp t2 = (pkgCache::Dep::DepCompareOp) 
(d2->CompareOp % pkgCache::Dep::Or);
 
   int cmpresult = _system->VS->DoCmpVersion(d1.TargetVer(), 
d1.TargetVer()+strlen(d1.TargetVer()),
d2.TargetVer(), 
d2.TargetVer()+strlen(d2.TargetVer()));

-- Package-specific info:
Terminal: xterm-256color
$DISPLAY is set.
which aptitude: /home/amu/bin/aptitude

aptitude version information:
aptitude 0.8.3
Compiler: g++ 6.1.1 20160802
Compiled against:
  apt version 5.0.0
  NCurses version 6.0
  libsigc++ version: 2.8.0
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.0.20160625
  cwidget version: 0.5.17
  Apt version: 5.0.0

aptitude linkage:
linux-vdso.so.1 (0x7ffe49113000)
libapt-pkg.so.5.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 
(0x7fa04d947000)
libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 
(0x7fa04d717000)
libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 
(0x7fa04d4ec000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7fa04d2e5000)
libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 
(0x7fa04cfe8000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7fa04cce4000)
libboost_iostreams.so.1.61.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.61.0 (0x7fa04cacc000)
libboost_filesystem.so.1.61.0 => 
/usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.61.0 (0x7fa04c8b3000)
libboost_system.so.1.61.0 => 
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.61.0 (0x7fa04c6ae000)
libxapian.so.22 => /usr/lib/x86_64-linux-gnu/libxapian.so.22 
(0x7fa04c2aa000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fa04c08d000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7fa04bd0b000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fa04ba06000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7fa04b7f)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fa04b44e000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fa04b24a000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7fa04b033000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fa04ae17000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7fa04ac07000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7fa04a9e4000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7fa04a7d1000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fa04a5c9000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7fa04a3c3000)
/lib64/ld-linux-x86-64.so.2 (0x55aa2c2b)

-- System Information:
Debian Release: stret

[Aptitude-devel] aptitude_0.8.6-1_amd64.changes ACCEPTED into unstable

2017-03-06 Thread Debian FTP Masters 


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 05 Mar 2017 23:19:57 +0100
Source: aptitude
Binary: aptitude aptitude-common aptitude-doc-cs aptitude-doc-en 
aptitude-doc-es aptitude-doc-fi aptitude-doc-fr aptitude-doc-it aptitude-doc-ja 
aptitude-doc-nl aptitude-doc-ru
Architecture: source all amd64
Version: 0.8.6-1
Distribution: unstable
Urgency: medium
Maintainer: Aptitude Development Team 
Changed-By: Manuel A. Fernandez Montecelo 
Description:
 aptitude   - terminal-based package manager
 aptitude-common - architecture independent files for the aptitude package 
manager
 aptitude-doc-cs - Czech manual for aptitude, a terminal-based package manager
 aptitude-doc-en - English manual for aptitude, a terminal-based package manager
 aptitude-doc-es - Spanish manual for aptitude, a terminal-based package manager
 aptitude-doc-fi - Finnish manual for aptitude, a terminal-based package manager
 aptitude-doc-fr - French manual for aptitude, a terminal-based package manager
 aptitude-doc-it - Italian manual for aptitude, a terminal-based package manager
 aptitude-doc-ja - Japanese manual for aptitude, a terminal-based package 
manager
 aptitude-doc-nl - Dutch manual for aptitude, a terminal-based package manager
 aptitude-doc-ru - Russian manual for aptitude, a terminal-based package manager
Closes: 831858 836567 837946 841347 841875 849370 852666 853037 854897 855329
Changes:
 aptitude (0.8.6-1) unstable; urgency=medium
 .
   [ Manuel A. Fernandez Montecelo ]
   * New upstream release. Please see /usr/share/aptitude/NEWS for a change
 log with more details.
 .
 - User visible changes:
   * [cmdline] Better message when there are no deb-src in sources.list
 (Closes: #841875)
 .
 - Bug fixes:
   * Use a more strict mask for comparison of dependency operators, thanks 
to
 Aaron M. Ucko for the initial patch (Closes: #836567, #837946, #849370)
   * Fix reading tag and their classification in subtrees (Closes: #853037)
   * Fix misdetection of auto-installed packages from apt
 (Closes: #831858, #841347)
 .
 - Translation updates:
   * ru.po: Russian translation by Lev Lamberov (Closes: #855329)
   * Dutch documentation translation by Frans Spiesschaert (Closes: #854897)
 .
 .
   * Remove wrong "From:" from contributor name in prev. changelog entry.
   * d/patches:
 - drop ftbfs-fix-french-doc.patch
 .
   [ Axel Beckert ]
   * Restrict build-dependency on google-mock to >= 1.8.0 as aptitude FTBFS
 with earlier versions since the adaptions for 1.8.0 in 0.8.4-1.
 (Closes: #852666)
Checksums-Sha1:
 2cd0ea536524eebc8a4e31eb4d9cbc6ebc1fe879 2990 aptitude_0.8.6-1.dsc
 e2b6237cdd3acc6cd8869dbaf6470e8cad805c91 4714728 aptitude_0.8.6.orig.tar.xz
 5c8a939b0511be877a4db3379c2d34656b128a3f 53184 aptitude_0.8.6-1.debian.tar.xz
 aa7705ceeb8d0d18543db4bbfa5fd12e9e441c0f 1587236 
aptitude-common_0.8.6-1_all.deb
 0a106be903adb0f081a9e9a13c796d47acb0d0ff 22809940 
aptitude-dbgsym_0.8.6-1_amd64.deb
 4fea0c5344d597c3c1f314af2259f540073f1128 366168 aptitude-doc-cs_0.8.6-1_all.deb
 96961e0c4ca6b0d77be0d2b279a1f92ae632ea16 433884 aptitude-doc-en_0.8.6-1_all.deb
 b309aebff9fd6efc94fb3300fd0fe64c1a58a9d0 412322 aptitude-doc-es_0.8.6-1_all.deb
 1be20331e72780b7b8fc99e4726ee80feacf7b1d 273728 aptitude-doc-fi_0.8.6-1_all.deb
 85aae26df27f1b9536656ce2d02c6591f521d12e 313762 aptitude-doc-fr_0.8.6-1_all.deb
 9cda1a63f870e4d3c5996c07a111a1c1b1714223 276002 aptitude-doc-it_0.8.6-1_all.deb
 eeb927f37d7ab7fc4f7811c065830726251a14c9 370354 aptitude-doc-ja_0.8.6-1_all.deb
 c8a32a55ab359d5092b32f64bcb5ec587d4e07ed 374422 aptitude-doc-nl_0.8.6-1_all.deb
 4deca63426d264f6a8de88eedb274985fc0d9c92 391446 aptitude-doc-ru_0.8.6-1_all.deb
 c2c29027e620325fcd19b8e5f3d6f7cb41abf9ec 12505 aptitude_0.8.6-1_amd64.buildinfo
 09ba83773ba87170bbc00e64e7f0c5a9d4f30664 1475560 aptitude_0.8.6-1_amd64.deb
Checksums-Sha256:
 633da493f99b0e10fc4e5c77afc8cd808e3223aa1471dafa778066ce11d2e9bd 2990 
aptitude_0.8.6-1.dsc
 b132a2fc45b57ed62e4d8a7447d32f0506dcc6f2b096bd149bfa7b3f727f0912 4714728 
aptitude_0.8.6.orig.tar.xz
 ae03e945f1b10e9cf8b0e95566836690e9bb91f8fcf4866041637a56cd95b2a0 53184 
aptitude_0.8.6-1.debian.tar.xz
 d7d795cc3f8e23b985ab8d35e268b5f851852ce86d463d2dfeade19cf4e894f3 1587236 
aptitude-common_0.8.6-1_all.deb
 21733c06db3ff163bda7381464c106815b34ca5b503d6f6b55d57dca303079b9 22809940 
aptitude-dbgsym_0.8.6-1_amd64.deb
 868e8b8973c4c9633928e7bc8ac1c7909a90595fbdc6f0147cd8dae3d0a420cc 366168 
aptitude-doc-cs_0.8.6-1_all.deb
 1e4c62c42afd79bbd696b901ff4f4e3876fa2ae605e6a2fabe3cbac75d2202f6 433884 
aptitude-doc-en_0.8.6-1_all.deb
 ece3484e9e4993511e23af3e65a4dd9befc7339b4ffa48edec7d8a8fa598d0ed 412322 
aptitude-doc-es_0.8.6-1_all.deb
 5f774931e4b36fcb23794b531a9a99fc79e24940e23d649cf5102c9597e87a88 273728 
aptitude-doc-fi_0.8.6-1_all.deb
 af709a127d60eeca0ae43f3308e3e7793c61486c59aac06d7f672ab7088f5f73 313762 
aptitude-doc-fr_0.8.6-1_all.deb
 c5354ca1d7a

[Aptitude-devel] Processing of aptitude_0.8.6-1_amd64.changes

2017-03-06 Thread Debian FTP Masters 
aptitude_0.8.6-1_amd64.changes uploaded successfully to localhost
along with the files:
  aptitude_0.8.6-1.dsc
  aptitude_0.8.6.orig.tar.xz
  aptitude_0.8.6-1.debian.tar.xz
  aptitude-common_0.8.6-1_all.deb
  aptitude-dbgsym_0.8.6-1_amd64.deb
  aptitude-doc-cs_0.8.6-1_all.deb
  aptitude-doc-en_0.8.6-1_all.deb
  aptitude-doc-es_0.8.6-1_all.deb
  aptitude-doc-fi_0.8.6-1_all.deb
  aptitude-doc-fr_0.8.6-1_all.deb
  aptitude-doc-it_0.8.6-1_all.deb
  aptitude-doc-ja_0.8.6-1_all.deb
  aptitude-doc-nl_0.8.6-1_all.deb
  aptitude-doc-ru_0.8.6-1_all.deb
  aptitude_0.8.6-1_amd64.buildinfo
  aptitude_0.8.6-1_amd64.deb

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel