Package: libapache2-mod-proxy-uwsgi
Version: 2.4.34-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
Package: libapache2-mod-proxy-uwsgi
Version: 2.4.34-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
Followup-For: Bug #894785
Control: found -1 2.4.33-2
Hi,
the recently added
Replaces: libapache2-mod-md (<< 2.4.33), libapache2-mod-proxy-uwsgi (<<
2.4.33)
on apache2-bin misses a corresponding
Breaks: libapache2-mod-md (<< 2.4.33), libapache2-mod-proxy-uwsgi (<< 2.4.33)
otherwise partial
Followup-For: Bug #894760
Hi,
similar problems exist with libapache2-mod-proxy-uwsgi:
Preparing to unpack .../13-apache2-bin_2.4.33-1_amd64.deb ...
Unpacking apache2-bin (2.4.33-1) over (2.4.29-2) ...
dpkg: error processing archive
Source: apache2
Version: 2.4.23-4
Severity: important
Hi,
apache2 FTBFS on on kfreebsd-i386:
https://buildd.debian.org/status/fetch.php?pkg=apache2=kfreebsd-i386=2.4.23-4=1471042791
make[4]: Entering directory '/«PKGBUILDDIR»/os/unix'
/usr/share/apr-1.0/build/libtool --no-silent --mode=compile
On 2016-05-28 22:21, Stefan Fritsch wrote:
> I think I have a patch that does this correctly.
Sounds promising. Be Is it generic enough s.t. it could be reused by
other packages with similar problems? (right now I remember squid and
libreoffice, but I think there were more)
> Is it possible with
Source: apr
Version: 1.5.2-3
Severity: important
Hi,
apr FTBFS on kfreebsd-i386 and kfreebsd-amd64 (but it built successfully
on these architectures in the past):
https://buildd.debian.org/status/fetch.php?pkg=apr=kfreebsd-amd64=1.5.2-3=1440073240
On 2015-06-25 11:40, Andreas Beckmann wrote:
Followup-For: Bug #768815
For wheezy-jessie we ignored the remaining problems in piuparts, but
for wheezy-jessie-stretch I'd like to get rid of them:
1m41.5s ERROR: FAIL: debsums reports modifications inside the chroot:
/etc/apache2/conf
Package: apache2-suexec-custom
Version: 2.4.16-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an
On 2015-08-08 22:36, Stefan Fritsch wrote:
Do you know if there is any practical difference between conflicts and
breaks+replaces in this case?
I don't think so. All dependencies on apache-2.2-common should be gone
by now, so removal of that package could happen anytime without
influencing any
On 2015-08-08 22:34, Stefan Fritsch wrote:
On Saturday 08 August 2015 11:38:14, Andreas Beckmann wrote:
This was observed while doing a wheezy - jessie - stretch upgrade
test. I did not see such behavior while testing the other apache
packages.
This now shows up on all (or at least a lot
Package: apache2.2-common
Version: 2.4.12-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package removes files that
were installed by another package.
The removed files were already present before the package was installed,
Package: apache2.2-common
Version: 2.4.12-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
Followup-For: Bug #768815
For wheezy-jessie we ignored the remaining problems in piuparts, but
for wheezy-jessie-stretch I'd like to get rid of them:
1m41.5s ERROR: FAIL: debsums reports modifications inside the chroot:
/etc/apache2/conf-available/other-vhosts-access-log.conf
On 2014-11-18 14:23, Stefan Fritsch wrote:
I think it would be best to ask the dpkg maintainers if they can make
dpkg recognize that the obsolete conffiles have been removed. If that
that is a hard part
but I got some weird idea about generalized file ownership:
(the classic ones)
* you own
On 2014-11-19 23:26, Arno Töll wrote:
On 19.11.2014 16:49, Andreas Beckmann wrote:
PS: do you need the apache2.2-common transitional package? would
Please see https://lists.debian.org/debian-devel/2014/07/msg00450.html
Nice writeup. No further questions :-)
Andreas
--
To UNSUBSCRIBE
Package: apache2.2-common
Version: 2.4.10-6
Severity: important
Hi,
this bug blocks doing piuparts wheezy - jessie upgrade tests for the
whole apache2 stack and any rdepends.
debsums: missing file /etc/bash_completion.d/apache2.2-common (from
apache2.2-common package)
debsums: missing file
On 2014-11-09 19:01, Stefan Fritsch wrote:
On Sunday 09 November 2014 14:21:34, Andreas Beckmann wrote:
I'm not sure whether (or how) dpkg-maintscript-helper mv_conffile
can be used reliably to rename a conffile and switch ownership to
another package at the same time.
I don't see how
Package: apache2
Version: 2.4.10-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of
Hi,
the package apache2.2-common (2.2.22-13) is still in sid ... but I
couldn't find a good explanation why. The source package apache2
previously providing it has been successfully rebuilt on all
architectures ...
This is a bit nasty as it blocks most piuparts tests for upgrading
apache
Control: affects -1 + phpbb3 debian-edu-config-gosa-netgroups
Processing triggers for libapache2-mod-php5 ...
apache2-maintscript-helper invoked from a modified environment.
Please hint required arguments manually
On 2013-07-23 08:38, jida...@jidanni.org wrote:
I get the same message. But
Package: glpi
Version: 0.83.91-3
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package left unowned files on
the system after purge, which is a violation of policy 6.8 (or 10.8):
Package: apache2.2-bin
Version: 2.4.4-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
Package: apache2-suexec
Version: 2.4.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
a test with piuparts revealed that your package misses the copyright
file after an upgrade from squeeze to wheezy, which is a violation of
Policy 12.5:
Uups, wrong template used ...
That happens during the sid - experimental upgrade, not squeeze-wheezy.
Andreas
--
To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
Package: apache2-bin
Version: 2.4.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries
Package: apache2-suexec-custom,apache2-suexec-pristine
Version: 2.4.1-2
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package left unowned files on
the system after purge, which is a violation of policy 6.8:
Package: apache2
Severity: wishlist
Hi,
there is a new upstream release (2.2.10) available.
I'd like to see this version in unstable because of the following new feature:
*) mod_proxy_balancer: Add 'bybusyness' load balance method.
While packaging the new version locally, the patches 059-064
Package: apache2.2-common
Version: 2.2.8-3
Severity: normal
File: /usr/sbin/a2dissite
Hi,
a2dissite should be able to remove dead symlinks pointing from
sites-enabled to a no longer existant file in sites-available.
(bash_completion already gives you a proper list of sites from
sites-anabled)
reopen 392349
thanks
This bug was previously closed with:
* Enable the same list of modules as we had in 2.0 (by default) and do
that for all older versions than 2.2.3-3 to fix upgrade issues people
have had. Closes: #392349
Unfortunately, there is a typo in apache2.2-common.postinst that
Package: apache2
Severity: normal
Hi,
apache (1.x) recently switched to libdb4.4-dev, but apache2 still uses
libdb4.3-dev.
Now php5 can't be built due to conflicting build depends: libdb4.4-dev
(pulled by apache-dev) and libdb4.3-dev (pulled by apache2-prefork-dev).
Andreas
-- System
31 matches
Mail list logo