** Package changed: postfix (Ubuntu Oracular) => cyrus-sasl2 (Ubuntu
Oracular)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078851
Title:
saslauthd wrong permission of /var/spool/postfix/var/run/s
Fixed in Noble and later.
** Changed in: pysubnettree (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/2035333
Title:
Bug due to change of underlying swig v
There's no postfix bug described here.
** Changed in: postfix (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065546
Title:
postfix configuration must be
** Changed in: cyrus-imapd (Ubuntu)
Status: Fix Committed => 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/1971469
Title:
FTBFS against openssl 3
To manage notifications about t
On Monday, January 31, 2022 9:51:59 PM EST Bryce Harrington wrote:
> Comparing the build log from 3.6.3 with the autopkgtest log for 3.6.4,
> these lines jump out at me:
>
> ### 3.6.3 ###
>
> install -m644 debian/postfix.insserv.conf
> debian/postfix/etc/insserv.conf.d/postfix txt2man -t postf
In theory, yes. In practice, it would be very complicated and it's not
something that's likely to get done in the near-term.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957884
Title:
postfix war
Does restarting (not reloading) or stopping/starting postfix get things
back in sync?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957884
Title:
postfix warns about differing chroot files after pa
It's postfix@$INSTANCE. If you don't have multi-instance setup, the
default instance is "-", so you would look for postfix@-, not postfix@.
This is discussed in README.Debian. You should probably file a new bug
for this problem if you don't get it figured out.
--
You received this bug notificat
On Wednesday, January 5, 2022 11:13:49 AM EST you wrote:
> Also check if we can get rid of the delta and make postfix a sync again.
No. The glibc change isn't incorporated. It would be nice if someone from a
distro (like Ubuntu) that has applied the patch would talk to upstream about
it and get
Thanks. I'll reassign this to Ubuntu's dkimpy package. They should
consider doing a stable release update to fix this.
** Project changed: dkimpy-milter => dkimpy (Ubuntu)
** Changed in: dkimpy (Ubuntu)
Importance: Undecided => High
** Changed in: dkimpy (Ubuntu)
Status: New => Triag
Not a ca-certificates issue.
** Changed in: ca-certificates (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915238
Title:
warning: /var/spool/postfix/etc
This is an unneeded leftover and the file in the chroot
(/var/spool/postfix) can be deleted.
When using smtp*_tls_CAfile, the smtp or smtpd daemon copies from
/etc/ssl/certs before entering the chroot (CApath is different), so it
doesn't need to be there. We stopped copying the file into the chro
So I looked into this a bit more and based on
http://www.postfix.org/postconf.5.html#smtp_tls_CAfile is doesn't appear
to me that the ca-certificates.crt file needs to be in the chroot at
all. What happens if you just delete the chroot copy? Looking in the
git history, I can see we used to instal
Public bug reported:
Debian now has jack-mixer 17. This might be a good time to see if a
sync is possible or at least do a merge so it's clear what's different
between the packages.
** Affects: jack-mixer (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notific
Incorporation of this patch in postfix upstream is currently being
discussed on the postfix-users mailing list. The specific question
asked by Wietse is:
Has this been adopted, or do people on 3.5.* still have to tinker with
their /etc/resolv.conf files?
If anyone from Ubuntu could comment on th
I'm open to putting a fix in Debian. I haven't come up with a solution
that I'm happy with and don't currently have a lot of time to work on
this.
I think Paride Legovini's "wall-of-text" post is on the right track, but
I would really prefer to avoid asking a question about this.
Anything in con
No. We've had postfix in a chroot since approximately forever. It
might be something in default path resolution has changed? Since I no
longer us Ubuntu, I really don't know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
We (Debian and derivatives such as Ubuntu) have postfix in a chroot by
default. This is a side effect of that configuration.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885403
Title:
posttls-fin
On Thursday, June 18, 2020 9:46:34 AM EDT you wrote:
> To do that a process needs to be defined for future Postfix SRUs
> containing micro-release updates. I see we already have some good DEP-8
> tests, so we'd need to write a wiki page describing this process and ask
> the SRU team to acknowledge
On Wednesday, June 17, 2020 5:51:07 PM EDT Lucas Kanashiro wrote:
> I see this fix in version 3.4.13. Hopefully this postfix SRU [1] will be
> accepted and we will have version 3.4.11 in Focal, so we have two patch
> level releases to consider if we want to update to 3.4.13. Checking the
> changelo
installed postfix package post-installation script subprocess returned
error exit status 75
This exist status indicates the system does not have a proper hostname
set. It is a local configuration issue and not a package bug.
** Changed in: postfix (Ubuntu)
Status: New => Invalid
--
You
I looked into the history of this. We used to have a patch in Debian to
use gethostbyname to address this issue. It was dropped because it
caused worse problems. Here's the relevant code snippet from the most
recent postfix release:
/*
* If the local machine name is not in FQDN form, t
https://github.com/vdukhovni/postfix/commit/
119d6abed969b1b30c62722ae31c854b5682beae#diff-1843f98f5710e97bd063d5807334442a
There will be a new 3.4 release in a few days, I'd just update your SRU to
encompass that when it comes out. It's all bug fixes, reported by users or
not.
--
You receive
In that case, someone with the new libc and postfix 3.4.11/3.5.2 or later
should write to the postfix-users list and ask for help. My recollection is
that the upstream developers did not have access to a system with the new libc
and were dependent on third party testing, so something may have b
On Monday, June 8, 2020 4:59:30 PM EDT you wrote:
> postfix (3.5.2-1+b1) sid; urgency=low, binary-only=yes
> .
>* Binary-only non-maintainer upload for amd64; no source changes.
>* Rebuild against libicu67
> .
> -- all / amd64 / i386 Build Daemon (x86-conova-01)
> Wed, 03 Jun 2020 20
That change is included in postfix 3.4.11 which is, of course, just
after the one that's in 20.04. "Someone" (i.e. not me) should look into
an SRU to update postfix. It has an existing microversion release
authorization from the Tech Board, so it shouldn't be too hard, it just
takes someone invol
Re-assigning to glibc then. I think that's a good demonstration this
isn't a postfix issue.
** Package changed: postfix (Ubuntu) => glibc (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/186895
Postfix doesn't have a bug tracker. Their policy is to fix bugs when
they are identified. Emailing postfix-users is the correct path
forward.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881196
Ti
That's almost certainly not the case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880970
Title:
Postfix refuses to start because file postfix-files is missing
To manage notifications about this
The package ships the file, so it's not a postfix bug.
https://packages.ubuntu.com/focal/amd64/postfix/filelist
** Changed in: postfix (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Fixed in focal and later up to the point where the package was removed.
** Changed in: python-pip (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/1556681
Tit
Fixed in bionic and later.
** Changed in: python-pip (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/1676675
Title:
python3-pip package missing dependency
Fixed in focal and later.
** Changed in: python-pip (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/1773794
Title:
python3-pip now requires python3-distuti
Fixed in Focal/Groove.
** Changed in: python-pip (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: hundredpapercuts
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
This was fixed by reverting the breaking change in python3 3.7 and 3.8.
** Changed in: python-bleach (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860270
Title
This was fixed in 3.4.7-2.
** Changed in: postfix (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/1444968
Title:
Postfix init.d scripts malfunction in an u
This was fixed in 3.4.7-2.
** Changed in: postfix (Ubuntu)
Status: Confirmed => 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/1548594
Title:
Convert test suite to python 3.0
To
This was fixed in 3.3.2-1.
** Changed in: postfix (Ubuntu)
Status: Triaged => 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/1684037
Title:
Wrong systemd dependencies prevent pos
In any case, this bug was about dropping deltas from Debian, not
upstream and Debian/Ubuntu handle this the same now.
** Changed in: python-pip (Ubuntu)
Status: New => Fix Released
** Changed in: python-pip (Ubuntu)
Milestone: ubuntu-15.10 => None
--
You received this bug notificatio
It's fixed in python-virtualenv 20.0.20+ds-1 and python-pip 20.1-1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873369
Title:
Python2 virtualenv installs broken pip command
To manage notificatio
** No longer affects: python-pip (Ubuntu)
** No longer affects: python-pip (Ubuntu Xenial)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1586381
Title:
Pip states report "AttributeError: 'Requireme
This was due to an incompatibility between the way pip and setuptools
manage their vendored modules. The problem was worked around by a
change in the Debian python-pip package (20.0.2-4) which was sync'ed
into Ubuntu. It's not a virtualenv bug.
python-pip | 20.0.2-5ubuntu1 | focal/uni
The fix for this was included in 20.0.2-4 imported from Debian.
python-pip | 20.0.2-5ubuntu1 | focal/universe | source
python-pip | 20.0.2-5ubuntu1 | groovy/universe | source
** Changed in: python-pip (Ubuntu)
Status: Confirmed => Fix Released
--
The fix was included in pip 20.0.2 brought in from Debian:
python-pip | 20.0.2-5ubuntu1 | focal/universe | source
python-pip | 20.0.2-5ubuntu1 | groovy/universe | source
** Changed in: python-pip (Ubuntu)
Status: Confirmed => Fix Released
--
You r
This is not a postfix bug.
** Changed in: postfix (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874923
Title:
Postfix documentation may have an error
To man
This is fixed in the Debian postfix git repository, but not uploaded
yet. Please use this approach vice what's in the patch.
https://salsa.debian.org/postfix-team/postfix-
dev/-/commit/b8e0b846e34eeaaa2315ead2304824b21b01fe7a
--
You received this bug notification because you are a member of Ubu
On Thursday, March 26, 2020 5:31:05 PM EDT you wrote:
> On 2020-03-26 3:54 p.m., Scott Kitterman wrote:
> > Does applying this change help:
> >
> > https://salsa.debian.org/postfix-team/postfix-dev/-/commit/
> > b8e0b846e34eeaaa2315ead2304824b21b01fe7a
>
> Does
There are some differences between stable and what was in unstable that Ubuntu
synced.
Does applying this change help:
https://salsa.debian.org/postfix-team/postfix-dev/-/commit/
b8e0b846e34eeaaa2315ead2304824b21b01fe7a
Scott K
--
You received this bug notification because you are a member o
On Thursday, March 26, 2020 12:22:20 PM EDT you wrote:
> Comparing strace between Ubuntu and Debian (lxc launch images:debian/10)
> showed that Debian's version doesn't try to connect to the tlsmgr socket
> for some reason.
>
> Ubuntu 3.4.10-1:
...
> Debian 3.4.8-0+10debu1:
...
If you use buster-
I don't recall seeing this issue in Debian, so I don't have any particular
suggestions. Since the postfix is identical, I'd be inclined to look
elsewhere.
Scott K
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
On Friday, March 6, 2020 2:49:21 AM EST you wrote:
> I'm so sorry this issue went unanswered for 9 years.. The backlog we've
> accrued here is truly unfortunate. We'd really like to see the situation
> improve, but with nearly 1300 open bugs, manually testing each has
> become virtually impossible.
9 years later. Lovely. I don't even use Ubuntu anymore.
** Changed in: apport (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/861645
Title:
Apport re
On Thursday, January 30, 2020 12:52:00 AM EST you wrote:
> Thanks Scott. Sincere questions: do you have any evidence users
> appreciate the current default? I'm asking myself what is the use case
> in which a user wants postfix to be installed, listening on all
> interfaces and yet.. unconfigured?
On Monday, January 27, 2020 5:05:06 AM EST you wrote:
> Hi kiko,
>
> > I have a highly customized set up, with vhosts, ldap, etc, and I
>
> installed the package first to be able to configure it, and immediately
> after installed I started dropping email.
>
> Clearly this was surprising to you.
On Friday, November 1, 2019 8:59:55 AM EDT you wrote:
> I have a pass with python3 for 3.4.7-1 in debian/sid. Let me clean that
> branch up now and make a MR in salsa.
>
> ** Attachment added: "log"
>
> https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1845334/+attachment/
> 5302040/+files
Any word on this? It'd be nice to get it done.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845334
Title:
Update DEP8 test to python3
To manage notifications about this bug go to:
https://bugs.l
** Changed in: postfix (Ubuntu Xenial)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728723
Title:
postfix check warns about symlink being group writable
To manage
That's correct. It was fixed in 2.0.0, but I'm not sure the fix would
directly apply to 1.3.2. I've targeted the bug appropriately for 16.04.
Perhaps someone involved in Ubuntu development will take a look.
** Also affects: pypolicyd-spf (Ubuntu Xenial)
Importance: Undecided
Status: Ne
That's got it properly triaged. I only work on postfix in Debian, so I
can't say if this will be fixed or not in Ubuntu.
** Also affects: postfix (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: postfix (Ubuntu Xenial)
Status: New => Triaged
** Changed in: postf
This is something that you should address with upstream (postfix-users mailing
list is the best venue).
Scott K
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826534
Title:
Pix workaround should b
No idea why the remote bug status isn't updating, but this is fixed in
Debian.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791853
Title:
Postfix upgrade queries about replacing /etc/postfix/maked
This is not a bug, but an intentional design change to, by default,
better protect user privacy. See man 5 policyd-spf.conf for details.
To restore the previous behaviour, add this to the policy server's
configuration:
Hide_Receiver = No
** Changed in: pypolicyd-spf (Ubuntu)
Status: New =
This is fixed in 3.3.2-1, which is in disco.
Scott K
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812571
Title:
postfix-dbgsym package has empty .debug files; debian/rules dh_strip
confusion
T
It turns out this was a Qt bug.
** Changed in: quassel (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1153064
Title:
Quassel IRC client has a 2 pixel win
** Changed in: quassel (Ubuntu)
Status: Fix Committed => 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/833751
Title:
error in English string
To manage notifications about this b
** Also affects: opendmarc (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: opendmarc (Ubuntu Trusty)
Status: New => Confirmed
** Changed in: opendmarc (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of
This is fixed in 3.3.
** Changed in: postfix (Ubuntu)
Status: Triaged => 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/1553928
Title:
postfix-pgsql SSL connection to postgres
T
FYI, this is fixed in 3.3.1 upstream, so when that lands, this diff can
be dropped.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753470
Title:
Postconf segfaults every 5 minutes
To manage notific
Fixed for the next upload in Debian that will, in due course, make its
way to Ubuntu.
** Changed in: clamtk (Ubuntu)
Importance: Undecided => High
** Changed in: clamtk (Ubuntu)
Status: New => Fix Committed
** Changed in: clamtk (Ubuntu)
Assignee: (unassigned) => Scott
On Monday, September 17, 2018 06:10:30 AM you wrote:
> This isn't sometihng we'd want to take a Delta in Ubuntu for IMHO, so
> I'm waiting if my Debian submission will be accepted.
I expect I'll apply the change, but am severely lacking in time right
now.
It would help if you could submit a merge
I'm open to changes for type hinting.
Scott K
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782416
Title:
Python3 Compat Problem: "Cannot use a bytes pattern on a string-like
object"
To manage
This is true pretty much throughout dkimpy when used with python3. It's
not particularly feasible to change it. I'm open to suggestions on
improved documentation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
If you feed it bytes, it works fine:
>>> print(message)
b'Authentication-Results: lists.example.org; arc=none; spf=pass
smtp.mfrom=jqd@d1.example; dkim=pass (1024-bit key) header.i=@d1.example;
dmarc=pass\nReceived: from localhost\nMessage-ID: \nDate:
Mon, 01 Jan 2011 01:02:03 +0400\nFrom: Test
It looks more like a debconf issue to me:
Preparing to unpack .../1-postfix_3.3.0-1_amd64.deb ...
Gtk-[1;32mMessage[0m: [34m20:19:38.211[0m: GtkDialog mapped without a
transient parent. This is discouraged.
Use of uninitialized value $ret in scalar chomp at
/usr/share/perl5/Debconf/Client/Co
** Package changed: update (Ubuntu) => postfix (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753470
Title:
Postconf segfaults every 5 minutes
To manage notifications about this bug go to:
On Monday, May 07, 2018 08:56:52 PM you wrote:
> Thanks Scott, I did email postfix-users with subject "NULL pointer deref
> in pcf_check_dbms_client() with unreadable map file", but I'm not
> subscribed. Checking the archive at https://marc.info/?l=postfix->
> users&r=1&b=201805&w=2 doesn't show m
On Monday, May 07, 2018 03:43:26 PM you wrote:
> I think the only contact to the developers is their postfix-devel
> mailing list here:
>
> http://www.postfix.org/lists.html
postfix-devel is generally for developers of postfix. Users should use
postfix-users (even for code issues like this).
On Monday, May 07, 2018 04:47:07 PM you wrote:
> And this is new in 3.3.0. I was also looking for some git/svn/bzr/cvs
> repository to check the history of these changes, but couldn't find it.
This is maintained by one of the primary postfix developers:
https://github.com/vdukhovni/postfix
It's
On Monday, May 07, 2018 03:14:56 PM you wrote:
> vstream_fopen() did return 0 and errno was set to EACCES, I don't know
> why that check is excluding the permission problem. I emailed upstream
> (couldn't find a bugtracker for it).
There is no postfix bugtracker upstream. Did you mail the postfix
This only happens if you've manually deleted /etc/postfix/main.cf but
left the postfix package installed. This is not a supported
configuration.
** Changed in: postfix (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On Wednesday, May 02, 2018 07:27:36 AM you wrote:
> Thanks Scott. I've gone ahead and built this package in the
> https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/ ;
> given the large amount of code around the introduced deserializer, I'd
> like to see a successful test report be
** Bug watch added: Debian Bug tracker #896914
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896914
** Also affects: quassel (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896914
Importance: Unknown
Status: Unknown
--
You received this bug notification because
*** This bug is a security vulnerability ***
Public security bug reported:
A recent upstream release contains two security fixes. All supported
Ubuntu releases are affected.
* SECURITY UPDATE: quasselcore, corruption of heap metadata caused by
qdatastream
- debian/patches/Implement_cu
I'm not using Kubuntu anymore anyway.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/657350
Title:
Crash in ubi-console-setup.
Not using Kubuntu anymore anyway.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/628894
Title:
Manual partition p
This was fixed in 1.3.2-3.
** Changed in: opendmarc (Ubuntu)
Status: Confirmed => 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/1694843
Title:
opendmarc ignores configuration
T
** Changed in: postfix (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748726
Title:
postfix incorrectly depends on e2fsprogs
To manage notifications about t
Did you ever get this figured out?
** Changed in: psycopg2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1238559
Title:
Exception causes next transaction t
Presumably this is resolved by now. Please set back to new if not.
** Changed in: psycopg2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/650777
Title:
ope
** Changed in: psycopg2 (Ubuntu)
Status: Confirmed => 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/1304138
Title:
Backport 2.5 bugfixes
To manage notifications about this bug g
Fix in Debian packaging git repository for the next upload to Debian.
Once that's uploaded, Ubuntu can update from that to get the fix.
** Changed in: clamav (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I agree it's not a duplicate.
I've seen this in Debian as well and haven't solved it their either.
** This bug is no longer a duplicate of bug 1531299
postfix upgrade can fail due to "newaliases: fatal:
inet_addr_local[getifaddrs]: getifaddrs: Address family not supported by
protocol" under
It was fixed in Debian later, but it's harmless. Because these are symlinks
(which the script doesn't follow), the permissions it detects aren't the
actual permissions. The 'fix' is not to emit the warnings for this. You can
ignore them.
--
You received this bug notification because you are
Bug in obsolete python helper:
File "/usr/share/pycentral-data/pyversions.py", line 172, in
default_version
** Changed in: psycopg2 (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Bug in obsolete python helper (pycentral).
** Changed in: psycopg2 (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/848566
Title:
package python-psycopg2 2.2.1
** Package changed: psycopg2 (Ubuntu) => egenix-mx-base (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650064
Title:
package python-psycopg2 2.6.1-1build2 failed to install/upgrade:
subpr
** Package changed: psycopg2 (Ubuntu) => python-defaults (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700964
Title:
package python-psycopg2 2.6.1-1build2 failed to install/upgrade: sub-
>From the terminal log:
newaliases: fatal: file /etc/postfix/main.cf: parameter mail_owner: user
postfix has same user ID as pulse
This is a local configuration issue and not a package bug.
** Changed in: postfix (Ubuntu)
Status: New => Invalid
--
You received this bug notification beca
Traceback (most recent call last):
File "/usr/bin/pycompile", line 35, in
from debpython.version import SUPPORTED, debsorted, vrepr, \
File "/usr/share/python/debpython/version.py", line 24, in
from ConfigParser import SafeConfigParser
ImportError: No module named 'ConfigParser'
** P
Based on the report against the test tool, unless this issue is
validated with the current version of the tool released in May 2017,
it's a false positive. It's not clear there's any kind of bug at all.
** Changed in: postfix (Ubuntu)
Importance: Critical => Undecided
** Changed in: postfix (
1 - 100 of 12919 matches
Mail list logo
