Yes, this has been fixed in aptitude 0.7.6 about 1.5 years ago. See
https://bugs.debian.org/576319 for details.
** Bug watch added: Debian Bug tracker #576319
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576319
** Changed in: aptitude (Ubuntu)
Status: New => Fix Released
** Also
** Tags removed: amd64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/493846
Title:
German man page for aptitude is outdated
To manage notifications about this bug go to:
> P.S. Debian Stable has already updated to xymon_4.3.28-2
No, that's wrong. Debian Stretch (current stable) has been initially
released with that version.
And neither Debian (nor AFAIK) Ubuntu will update to newer upstream
releases in stable releases unless there's a critical security issue
The following comment by the main ack upstream developer in the
according upstream ticket may give a hint where to look for the
failure reason:
- Forwarded message from Andy Lester
(https://github.com/beyondgrep/ack2/issues/652#issuecomment-350527181) -
Here's something interesting: Many
Using "pbuilder" I've set up a minimal chroot for Ubuntu 18.04 Bionic as
of today. Inside that chroot, I installed autopkgtest, pkg-perl-
autopkgtest and ack (version 2.18+dfsg-1, 2.19.01-1 doesn't seem to be
on my mirror yet) from bionic-proposed and ran "autopkgtest ./ -- null"
inside the
Hrm, no, the only upstream commit since 2.18 which mentions Ubuntu is
https://github.com/beyondgrep/ack2/commit/66009a140a9d05302546bcd4c1d85fd5d66388f2
and that only fixes a lintian warning about misspellings (which we had
overridden already in the Debian package). So I don't see any relation
to
This is a bug report against ack, the kanji converter, which has been
removed from Ubuntu since before Ubuntu 14.04 LTS (Trusty) and replaced
with ack, the grep for humans, in Ubuntu 17.04 Zesty.
Hence closing.
** Changed in: ack (Ubuntu)
Status: Confirmed => Fix Released
--
You
Upstream said, he fixed the reason for this issue in his upstream
release candidate 2.19_01 which I'll soon upload to Debian as 2.19.01-1.
I'll close this bug report with that upload, so please reopen it, if
this doesn't fix the issue. (Can't really test that beforehand as this
issue seems
*** This bug is a duplicate of bug 1640514 ***
https://bugs.launchpad.net/bugs/1640514
** This bug has been marked a duplicate of bug 1640514
/snap/bin is not added to the PATH when using zsh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
zsh sources /etc/zsh/zprofile by default. /etc/profile (and hence
/etc/profile.d/) is only sourced in zsh's compatibility mode, i.e. when
zsh is called as sh or ksh. At least Debian does not provide such
symlinks and does not plan to do so in the future. (In contrary, Debian
deliberately stopped
Someone from Ubuntu might want to cherry-pick that patch from 4.3.26-2
into 4.3.25-1 from 16.04 LTS. But IIRC that needs some changes/flags to
this bug report I can't do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This should be already fixed in 4.3.26-2 (and upstream in 4.3.27):
xymon (4.3.26-2) unstable; urgency=high
* Apply upstream-suggested patch for multiple CGI related regressions in
4.3.26.
-- Axel Beckert <a...@debian.org> Fri, 04 Mar 2016 16:01:20 +0100
--
You received th
A fixed version is already present in e.g. zesty.
** Changed in: xymon (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730738
Title:
xymon web interface
in
Debian Testing and Unstable.
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, https://people.debian.org/~abe/
: :' : | Debian Developer, Debian Perl Team member, Debian ack maintainer
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`-|
Upstart is no more. Hence separating from the other bug reports (which
were about error messages which should be fixed by the conversion and
may still be there) and closing as invalid.
** This bug is no longer a duplicate of bug 574773
Cannot make directory '/var/run/screen': Permission denied
Disconnecting from the "init script should be converted to upstart" bug
reports.
** Summary changed:
- Cannot make directory '/var/run/screen': Permission denied (convert init to
upstart)
+ Cannot make directory '/var/run/screen': Permission denied
--
You received this bug notification
ution-only patch.
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, https://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 20
This is a conflict with an Ubuntu-only package. I'll add a proper
Conflicts/Replaces header with the next upload to Debian, but inside an
Ubuntu stable release this needs to be fixed by Ubuntu.
** Changed in: debian-goodies (Ubuntu)
Status: New => Confirmed
--
You received this bug
I do not want to add any further patches to Debian's screen package
which makes it differ from upstream behaviour more than it already does.
(Of course, it's a different thing if issues are caused by existing
patches.)
And IMHO workarounds for issues in other packages do not belong into
shell
Please see this new section in README.Debian, which will be published
with the next upload of Debian's screen package to Debian Unstable:
https://anonscm.debian.org/cgit/collab-
maint/screen.git/tree/debian/README.Debian#n142
I don't see any other feasible solution to this problem from the side
** Bug watch added: Debian Bug tracker #854414
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854414
** Also affects: screen (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854414
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Wheezy).
But there is an request to remove it at least also from Oldstable
(Jessie): https://bugs.debian.org/869273
> So it is sensible to remove it from ubuntu as well. Thanks
That's nevertheless correct.
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, https://people.
** Changed in: aiccu (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718233
Title:
aiccu package should be taken out of distribution due to closing of
Fixed in the 4.0-3 upload to Debian Unstable by adding a NEWS.Debian
file. Now the package just needs to be synced to Ubuntu to fix this in
Ubuntu, too.
** Changed in: fping (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of
@rhhoek: Thanks for the response: Will add a NEWS.Debian file with an
according entry. If you have apt-listchanges installed, you will be
either shown or mailed that entry when you update the package.
Not sure if that will still make it into Ubuntu Artful. In case the
freeze for Artful is already
** Changed in: fping (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1712812
Title:
In version 4.0-2 fping6 is not installed
To manage notifications about
This is on purpose. fping6 is no more needed. fping can do IPv4 and
IPv6. Please see /usr/share/doc/fping/changelog.Debian.gz.
The reason that command-not-found suggests to install fping for fping6
sounds like an out of date apt-file database.
Do you think an entry in NEWS.Debian would have
So what does this have to do with WICD, the Wireless/Wired Internet
Connection Daemon? Is this an issue with duplicity, an incremental
commandline backup tool? Or with another tool which calls duplicity
(which wicd definitely does not).
Marking as invalid for now until further information is
This is fixed since 2.0.9+nmu1 and fixed in Ubuntu since 2015-10-26 and
xenial. Hence closing.
** Changed in: equivs (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is fixed with 2.0.9+nmu1 and hence fixed in Ubuntu since 2015-10-26
and xenial as Mantas wrote. Hence closing.
** Changed in: equivs (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: equivs (Ubuntu)
Status: Confirmed => In Progress
** Changed in: equivs (Ubuntu)
Assignee: (unassigned) => Axel Beckert (xtaran)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Hi Jeremy,
I don't see why this bug report are declared as affecting debian-goodies
in _Debian_. This seems to be an ubuntu-specific issue to me as no
package named bikeshed exists in Debian.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
val for each of your autossh connection to
make autossh react more timely if the connection stalls:
Replace every occurrence of "autossh" in your setup with e.g.
"env AUTOSSH_POLL=5 autossh" to see if that already helps.
Hope this helps!
R
*** This bug is a duplicate of bug 1522675 ***
https://bugs.launchpad.net/bugs/1522675
So why is this bug report filed against aptitude?
** Package changed: aptitude (Ubuntu) => synaptic (Ubuntu)
** This bug has been marked a duplicate of bug 1522675
Warning messages about unsandboxed
** Also affects: wicd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689138
Title:
Wrong Galician translation
To manage notifications about this bug go
** Changed in: wicd (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689138
Title:
Wrong Galician translation
To manage notifications about this
Yes, this is no more reproducible in fwsnort 1.6.x, hence closing.
** Summary changed:
- fwsnort --update-rules doesn't works
+ fwsnort --update-rules doesn't work
** Changed in: fwsnort (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member
So the screen testsuite I wrote 2.5 years ago actually found a bug?
Cool! :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669578
Title:
Get ttyname() to work properly in containers
To manage
mmit is only present in the master branch which is the
developement branch for a potential Screen 5.x series.
But that branch iss far from stable. Debian and Ubuntu currently track
the screen-v4 stable branch — which still has that code.
Regards, Axel
--
,''`. | Axel Beckert <
According to Markus Kuhn, this bug has been fixed with the screen
version in Ubuntu 16.04. Hence closing.
Future versions of screen (4.5.1-1 and higher, currently in Debian
Experimental) use libutempter instead of setgid utmp and hence
/var/run/screen/ will have permissions 1777 anyways.
**
** Tags added: patch
** Also affects: wicd (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: Debian Bug tracker #758737
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758737
** Also affects: wicd (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758737
** Also affects: wicd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1591489
Title:
WPA2-PEAP with CCMP/MSCHAPV2 requires Domain this should not
** Summary changed:
- PEAP templates does not work with wpa_supplicant-2.6 because of typo .
+ PEAP templates does not work with wpa_supplicant-2.6 because of typo
MSCHAPv2 vs MSCHAPV2
** Also affects: wicd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: wicd
Comment #3 only works if you added a diversion _manually_.
I consider comments #5 to #7 being a confirmation that this is not a bug
in the package, but caused by the local administrators having added
local diversions themselves.
--
You received this bug notification because you are a member of
** Summary changed:
- package ack-grep 2.12-1 failed to install/upgrade: trying to overwrite
`/usr/bin/ack', which is the diverted version of `/usr/bin/ack-grep'
+ package ack-grep 2.12-1 fails to install/upgrade with "trying to overwrite
`/usr/bin/ack', which is the diverted version of
** Changed in: debsums (Ubuntu)
Assignee: Debian Perl Group (pkg-perl-maintainers) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1522563
Title:
hangs on packages libfm4 and
*** This bug is a duplicate of bug 1522563 ***
https://bugs.launchpad.net/bugs/1522563
** This bug has been marked a duplicate of bug 1522563
hangs on packages libfm4 and libfm-extra4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
JFTR: The accused line (should be "nbuf[rpms->ln][winw+1] = wrapped ?
zr_nl : zr_zr;") hasn't been touched upstream since 2008-04-03, so the
chances that the issue shows up in all of the above mentioned and tested
versions of zsh are rather high (since 4.3.17 was released after that
line has been
Tyler/Seth: Sorry, the past message was thought for Tyler.
dmitri: I can't reproduce the crash with neither zsh 5.0.2 inside an
Ubuntu 14.04 chroot, nor with zsh 5.0.7 on Debian 8, zsh 4.3.17 on
Debian 7 or zsh 5.2 on Debian Unstable.
$ GET
** Changed in: zsh (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620375
Title:
zsh 5.0.2 Out of bounds read
To manage notifications about this bug go to:
Seth: Strip any leading space in the file and it works, e.g. like this:
→ sed -e 's/^ *//' base64.txt | base64 -d | zcat | file -
/dev/stdin: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from
'pinentry --display :0', real uid: 1000, effective uid: 1000, real gid: 1000,
Yes, this does no more appear in at least 16.04 Xenial. And Xenial has
procps 3.3.10 which should have fixed this issue. Hence closing. Thanks
for the hint.
** Changed in: procps (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of
@niemeyer: Nope, if you want the equivalent to /etc/profile, then use
/etc/zsh/zprofile.
See https://tanguy.ortolo.eu/blog/article25/shrc why zshenv is not
equivalent to profile.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Additionally, /etc/profile.d/ in Debian/Ubuntu is a feature implemented
in /etc/profile which is installed by base-files in its postinst script.
But zsh only loads /etc/profile if invoked in its sh or ksh emulation
mode (which is not the case if invoked as "zsh"). I don't think that we
should
@faenil: What you're citing is RedHat-specific and doesn't seem to
related to any commit in the upstream or the Debian zsh git repository.
So this is basically a Debian-/Ubuntu-specific feature request for
something that RedHat already kicked out again.
--
You received this bug notification
** Changed in: debsums (Ubuntu)
Status: Confirmed => In Progress
** Changed in: debsums (Ubuntu)
Assignee: (unassigned) => Debian Perl Group (pkg-perl-maintainers)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: aptitude (Ubuntu)
Status: New => Confirmed
** Bug watch added: Debian Bug tracker #838560
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838560
** Also affects: aptitude (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838560
Importance: Unknown
** Changed in: slay (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: slay (Ubuntu)
Assignee: (unassigned) => Axel Beckert (xtaran)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Summary changed:
- Samba 4.3.8-Ubuntu ls Windows 10 cli_list: Error: unable to parse name from
info level 260
+ smblcient 4.3.8-Ubuntu ls Windows 10 cli_list: Error: unable to parse name
from info level 260
** Summary changed:
- smblcient 4.3.8-Ubuntu ls Windows 10 cli_list: Error: unable
** Summary changed:
- Overwrites ~/.aptitude/config
+ Overwrites ~/.aptitude/config with root permissions if run under sudo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/498545
Title:
Overwrites
Robie: I wondered if I should do that, too, but I was unsure if it
really was the same bug since there was no mentioning of Ctrl-S/XON
except in the reference to the upstream bug report which might be same
issue or not.
But yeah, it's probably better if someone writes a fresh reports in case
this
> trying to overwrite '/usr/bin/ack', which is the diverted version of
'/usr/bin/ack-grep'
There never was a diversion of ack-grep to ack in the package. This
error message looks a lot like a diversion done by the local system
administrator, i.e. is a problem of a local, unsupported
*** This bug is a duplicate of bug 1589024 ***
https://bugs.launchpad.net/bugs/1589024
** This bug has been marked a duplicate of bug 1589024
Warning on viewing a changelog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This has been fixed in aptitude 0.7.6-1 and is fixed in yakkety.
See also Debian bug report https://bugs.debian.org/806595
** Bug watch added: Debian Bug tracker #806595
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806595
** Also affects: aptitude (Debian) via
If you want that fixed in xenial, too, please have a look at
https://wiki.ubuntu.com/StableReleaseUpdates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589024
Title:
Warning on viewing a changelog
I'm sorry, but I can't reproduce this issue. Tried with uxterm on trusty
and my own .zshrc (which is based on the Grml zshrc). No crash at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587622
Will test it.
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, 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
*** This bug is a duplicate of bug 1385390 ***
https://bugs.launchpad.net/bugs/1385390
As already mentioned in #1385390:
There never was a diversion of ack-grep to ack in the package, so this
looks a lot like a diversion by the local system administrator.
Remove to local diversion and the
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, 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
--
You received
Thanks for the link. According to
https://wiki.debian.org/AppStream/Guidelines this seems only for GUI
applications.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575345
Title:
Gnome Software
What kind of meta data do you mean? I thought GNOME's "Software" uses
packagekit as backend which again uses apt as backend and hence should
be able to see _all_ packages.
** Changed in: screen (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
e welcome. Thanks for maintaining the package for Debian.
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`-
** Changed in: linuxlogo (Ubuntu)
Status: Opinion => In Progress
** Changed in: linuxlogo (Ubuntu)
Assignee: (unassigned) => Axel Beckert (xtaran)
** Changed in: linuxlogo (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification be
lintian warnings if I should do
the upload and you're ok with fixing those warnings -- as they're
usually out-of-scope for an NMU unless permitted by the package
maintainer.)
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/
: :' : |
Hi Dariusz,
Axel Beckert wrote:
> You seem to have taken over the maintenance of the Debian package of
> linuxlogo, so you could make the default depending on the distro the
> package is built for at build time.
The attached patch should implement that behaviour for Ubuntu and
Raspbian
Hi Dariusz,
I don't seem to be the only one of this opinion, see
https://bugs.launchpad.net/ubuntu/+source/linuxlogo/+bug/1364624
You seem to have taken over the maintenance of the Debian package of
linuxlogo, so you could make the default depending on the distro the
package is built for at
*** This bug is a duplicate of bug 109 ***
https://bugs.launchpad.net/bugs/109
** This bug has been marked a duplicate of bug 109
Would be cool if the Ubuntu logo would be shown by default instead of the
Debian logo
--
You received this bug notification because you are a
ckages appear as “Obsolete or Locally
Installed” in the visual interface.
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD
that the bug report _is_ marked as
"Fix released", at least in the current development version:
3. Procedure
1. Check that the bug is fixed in the current development release,
and that its bug task is "Fix Released".
Now please go and follow that procedure,
oke those people, so it's up
to you to contact them. See the links I posted in my previous comment
for how to do that.
> Until that's done, this is *not* a duplicate,
It is.
> the reporting issue has not been solved
It has. Just not in 14.04.
> (hey look, that's for 14.04 too!).
Once a
d in Ubuntu" (which is not the same as "fixed in the
current LTS release").
If you really want to get this fixed in Ubuntu 14.04 LTS, please
follow the instructions in the guides listed above instead of opening
new duplicates for already existing bug reports. Thanks!
** Summary changed:
- Missing sucessor for obsolete package
+ Missing successor for obsolete packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569168
Title:
Missing successor for obsolete
Either the according package lists its successor(s) in the Depends field
(then it's usually called "transitional package") or there is no
(direct) successor at all. That can also happen.
Aptitude doesn't know more than the package (list) tells it.
Or do you have a different idea how Aptitude
This has been fixed in aptitude 0.7.4 as in Ubuntu 16.04 Xenial.
** Bug watch added: Debian Bug tracker #801460
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801460
** Also affects: aptitude (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801460
Importance: Unknown
This has been fixed in 4.3.11-1 and hence only affects trusty. Vivid,
wily and xenial are no more affected.
** Changed in: xymon (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This has nothing to with the package of GNU Screen.
** Package changed: screen (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to screen in Ubuntu.
https://bugs.launchpad.net/bugs/1556466
Title:
Startup may reveal
This has nothing to with the package of GNU Screen.
** Package changed: screen (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1556466
Title:
Startup may reveal information
To
This has been fixed in Debian with 2.5.0~rc2-1and there is 2.5.0-6 in
Ubuntu now.
** Changed in: libembperl-perl (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Bug watch added: Debian Bug tracker #806595
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806595
** Also affects: aptitude (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806595
Importance: Unknown
Status: Unknown
** Changed in: aptitude (Ubuntu)
Ehm, precise is still supported until April 2017. And that bug is still
present in precise. So reopening...
** Changed in: gvfs (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ss, I'd prefer to keep that bug
open at least until precise is gone, too.
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 C
Thanks for the bug report.
Fix committed in git in Debian: https://anonscm.debian.org/cgit/collab-
maint/hobbit-
plugins.git/commit/?id=ce1ae825c922f32033d45f9cc7dcea4140adc016
** Changed in: hobbit-plugins (Ubuntu)
Status: New => In Progress
** Changed in: hobbit-plugins (Ubuntu)
ed?
aptitude-create-state-bundle -- but that's probably not needed as this
is very likely already fixed (in Debian).
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2
** Also affects: aptitude (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801430
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516438
** Bug watch added: Debian Bug tracker #801373
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801373
** Also affects: padre (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801373
Importance: Unknown
Status: Unknown
--
You received this bug notification because
This issue has been caused because the python3.4 upload to trusty-
updates from 24th of September has been reverted yesterday and has been
replaced by the previous upload. See
https://bugs.launchpad.net/bugs/1500768
--
You received this bug notification because you are a member of Ubuntu
Bugs,
So you leave all users of the trusty-updates with packages installed
that are newer than what is available in the archives and hence take the
chance to get proper security updates in the future?
# apt-cache policy python3.4
python3.4:
Installed: 3.4.3-1ubuntu1~14.04.1
Candidate:
n3.4{,-minimal,-stdlib}=3.4.0-2ubuntu1.1".
You might want to adjust the list of packages depending on which
packages you have installed. (Usage of "{…,…}" requires bash, zsh or
similar as shell.)
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org
The according bug in Debian (https://bugs.debian.org/418361) has been
closed in Debian as "not actionable". Please see the discussion there
for details.
Besides: In my terminal (uxterm), these colors are readable without
issues while I agree that the colors in the screenshots are suboptimal.
But
JFTR: I just checked, for me the background color in this widget is a
light yellow, not an orange. Seems to make a difference wrt. to
readability.
** Attachment added: "Screenshot of aptitude 0.7.1-1 running in uxterm"
101 - 200 of 695 matches
Mail list logo
