Package: pulseaudio
Version: 4.0-6
Severity: normal
Since reporting bugs about pulseaudio being silent seems to be
problematic due to lack of reproducability (may require same hardware
and software setup) and lack of other information, I'd suggest to add a
bug-script to the pulseaudio packages tha
On 2014-02-17 19:48, Julien Cristau wrote:
> On Sat, Feb 8, 2014 at 19:13:38 +0100, Andreas Beckmann wrote:
>
>> Package: ftp.debian.org
>> Severity: normal
>>
>> Please remove xserver-xorg-input-void 1:1.4.0-1+exp1 from experimental,
>> it is uninstallabl
Package: pkgconf
Version: 0.9.5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'sid' fails.
>From the attached log (scroll to the bot
(1.0-11.1+deb7u1) wheezy; urgency=medium
+
+ * QA upload.
+ * Rebuild with current debhelper. (Closes: #689773, #476252)
+
+ -- Andreas Beckmann Mon, 17 Feb 2014 23:40:09 +0100
+
elib (1.0-11.1) unstable; urgency=low
* Non-maintainer upload.
[The following lists of changes regard files as
either reassign back to resolvconf "does not preserve comments (and
whitespace)" or
On 2014-02-18 00:27, Holger Levsen wrote:
> The solution for this bug is probably to remove the comments from
> /etc/resolv.conf with a custom-script...
post_setup_resolv_confconf (or do we already have one that
Package: libunwind-setjmp0
Version: 1.1-2.2
Severity: important
Tags: patch
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to remove some
diversions after upgrading from wheezy and removing the package
afterwards.
Filing this as i
about changes outside debian/
Low intent to NMU, not earlier than three months from now, but somewhen
before freeze :-)
Andreas
>From d11b26ee017afc80980dab4ba9b8c3fe7f7e0b61 Mon Sep 17 00:00:00 2001
From: Andreas Beckmann
Date: Tue, 18 Feb 2014 00:09:14 +0100
Subject: [PATCH] clea
On 2013-05-07 11:33, Patrick Matthäi wrote:
> Am 07.05.2013 11:22, schrieb Andreas Beckmann:
>>applying upgrade script for 3.1.7+dfsg1-8 -> 3.2.0.
>>Trying to connect to database
>>DSN: DBI:mysql:database=otrs2;host=localhost;port=3306;
>>Databas
On 2014-02-17 07:28, Alexander Wirt wrote:
> On Sun, 16 Feb 2014, Andreas Beckmann wrote:
>
>> On 2014-02-16 14:09, Alexander Wirt wrote:
>>> I did several installation with fresh vms and I wasn't able to reproduce the
>>> problem.
>>
>> piup
Followup-For: Bug #736296
Hi,
that fix does not yet work. The following bits are wrong:
* there is only a dpkg-maintscript-helper call in the preinst, but it is
missing from all the other maintainer scripts. Please consider using a
$PACKAGE.maintscript file and dh_installdeb - this will plac
Package: dpkg
Version: 1.17.6
Severity: normal
Hi,
please document how to use the symlink_to_dir/dir_to_symlink
dpkg-maintscript-helper commands correctly if they are being introduced
"too late", e.g.
version 1 ships a symlink
version 2 ships a directory
version 3 starts using d-m-h symlink_to_d
On 2014-02-17 23:34, Michael Gilbert wrote:
> control: tag -1 confirmed
> control: severity -1 grave
I'll probably downgrade the severity if Xserver 1.15 moves towards testing
> I am also seeing this with 14.1.
please
reportbug -N 739054
s.t. we have the glory details :-)
do you also get
(E
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
nmu veusz_1.20.1-1 . amd64 . -m "Rebuild against sip-api-10.1"
The maintainer upload of veusz was built in wheezy (sip-api-8.1),
but uploaded to sid.
Andreas
@Jeremy: please build package
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
nmu cubemap_1.0.3-1 . amd64 . -m "Rebuild against protobuf 2.5"
The maintainer upload seems to have been built in parallel to the
starting protobuf transition against old libprotobuf7.
Andr
Package: llvm-3.5-tools
Version: 1:3.5~svn201412-1
Severity: grave
Tags: sid
Justification: renders package unusable
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package is no longer
installable in sid:
The following packages have unmet dep
Package: python-taskflow
Version: 0.1.2-1
Severity: grave
Tags: sid
Justification: renders package unusable
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 python-taskflow
Hi,
during a test with piuparts I noticed your package is not
installable in sid:
The following pa
Package: dpsyco-sudo
Version: 1.0.36
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: piuparts
Control: sffects -1 + dpsyco
Hi,
during a test with piuparts I noticed your package modifies conffiles.
This is forbidden by the policy, see
http://www.debian.org/doc/debian
Package: texlive-publishers,texlive-publishers-doc
Version: 2013.20140215-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
Control: severity -1 important
On 2014-02-18 04:26, Andreas Beckmann wrote:
> I'll probably downgrade the severity if Xserver 1.15 moves towards testing
Bug has been confirmed upstream, AMD is working on a fix.
Andreas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.de
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
nmu supertux_0.3.4-1 . ALL . experimental . -m "Rebuild against glew 1.10"
supertux in experimental depends on the no longer available libglew1.7
Andreas
--
To UNSUBSCRIBE, email to deb
On Wednesday, 15. January 2014 22:29:31 Sebastian Ramacher wrote:
> I've prepared an NMU for warzone2100 (versioned as 3.1~beta11-2.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
Hi Sebastian,
do you plan to fix this in experimental, too?
Andreas
Control: found -1 201202.0-2
Control: tag -1 jessie sid
On Sunday, 1. December 2013 16:03:41 Julien Cristau wrote:
> your package no longer builds on armel and armhf, see the build logs at
> https://buildd.debian.org/status/logs.php?pkg=mcrl2&ver=201210.1-1&suite=si
Extending to the version in te
Control: found -1 3.0.4624-8
On Monday, 10. February 2014 21:43:54 Filippo Rusconi wrote:
> On Sat, Feb 08, 2014 at 01:13:37AM +0100, Andreas Beckmann wrote:
> >your package failed to build on mips and mipsel:
> >
> >https://buildd.debian.org/status/package.php?
Package: python-pysam-tests
Version: 0.7.5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships a world
writable directory and several world writable files in there.
>From the attached log (scroll to the bottom...):
On 2014-02-20 10:08, Andreas Tille wrote:
> Hi Andreas,
>
> the directory is intended to be written by the world since the whole
> world should be able to run the test suite there ... this is the purpose
> of this package at all: Let everybody run the test (including
> autopkgtest) and forget abo
Package: gnuhealth-server
Version: 2.4.1-1
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.
>Fro
Package: fsharp
Version: 3.0.34+dfsg-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + libfsharp-data-typeproviders4.3-cil
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the pac
Package: libboinc7
Version: 7.2.39+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + boinc-dev
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'wheezy'.
It installed fine in 'wheezy', then the upgrade to 'jessie' fails
On 2014-02-21 14:37, Gianfranco Costamagna wrote:
> Hi Andreas,
>
> I tried to add a Break+Replaces, but it didn't work,
How did this look like? And how did it fail?
> I think because now boinc-dev is not a real package anymore, just a
> transition virtual package.
Since the B+R you add are v
Package: libqt5-dev
Version: 3
Severity: serious
Tags: sid
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package is no longer
installable in experimental. It depends on libqt5v8-5-dev which is no
longer available or provided by any package.
C
Package: fontconfig-config
Version: 2.11.0-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to purge.
>From the attached log (scroll to the bottom...):
Removing fontconfig-config (2.11.0-3) ...
Purging conf
Package: libtowitoko2
Version: 2.0.7-9
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package left unowned
directories on the system after purge, which is a violation of
policy 6.8:
http://www.debian.org/doc/debian-policy/ch
Package: python-expeyes
Version: 3.1.6-1
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package left unowned
directories on the system after purge, which is a violation of
policy 6.8:
http://www.debian.org/doc/debian-policy/
Package: shinken-common
Version: 1.4-2
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package left unowned
directories on the system after purge, which is a violation of
policy 6.8:
http://www.debian.org/doc/debian-policy/ch
On 2014-02-21 19:02, Gianfranco Costamagna wrote:
>>> I think because now boinc-dev is not a real package anymore, just a
>>> transition virtual package.
no it's not virtual, only transitional ...
>> This probably breaks if I torture-test it :-) And it will definitely
>> break in case you add a
Source: pacemaker-mgmt
Version: 2.0.0+hg1141-2.3
Severity: serious
Justification: fails to build from source (but built successfully in the past)
>From a rebuild in sid:
[...]
Making all in mgmt
make[2]: Entering directory `/tmp/buildd/pacemaker-mgmt-2.0.0+hg1141/mgmt'
Making all in daemon
make[3
On Friday, 21. February 2014 02:46:33 Simon McVittie wrote:
> Upgrading syncevolution to a version with syncevolution-libs-gnome
> It probably just needs Replaces: syncevolution-libs (<< 1.3.99.7),
> Breaks: syncevolution-libs (<< 1.3.99.7).
>
> I haven't installed the KDE equivalent but it probab
Package: rygel-2.2-dev
Version: 0.21.4-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 trie
Source: mariadb-5.5
Version: 5.5.35-1
Severity: serious
the mariadb-*-5.5 packages ship the same files as mysql-*-5.6 in
experimental without having appropriate Breaks+Replaces.
Maybe myriadb and mysql should agree on a set of virtual packages that
can be used for Provides/Conflicts/Replaces to a
On 2014-02-23 04:31, Jeremy Malcolm wrote:
> I just noticed that you reopened this bug but without giving any explanation,
> and the package has now been removed from testing. Why was the bug reopened?
The forcemerge left this bug in a state where it cannot be archived
again since it is not cons
On 2014-02-23 09:25, joj wrote:
>> Bug has been confirmed upstream, AMD is working on a fix.
>> Andreas
>
> Could you point out where this was confirmed (bug on the bug tracker etc)? I
> don't seem be able to find a corresponding bug on the ati.cchtml.com bugzilla.
In private correspondence.
An
On 2014-01-18 15:09, Holger Levsen wrote:
> subject says it all. (This will become more interesting as piuparts results
> will be used for testing migration.)
We have updates of all essential packages in each upgrade ... if any of
the essential packages fails, the test of the package to be tested
On 2014-01-18 15:12, Holger Levsen wrote:
> currently piuparts.d.o only tests packages of arch amd64 and all, while the
> machines could trivially have i386 chroots, to also tests packages which are
> i386 only.
We could start with having both sid_i386 and sid_amd64 for now. And they
should be t
On 2014-01-18 15:18, Andreas Beckmann wrote:
> Or should we drop tes special case essential-required and run them for
> all the packages? That would be around 60 identical tests that would
> either all pass or all fail, but yes, that's an early indicator that
> something is amis
On 2014-01-18 15:57, Holger Levsen wrote:
> Hi Andreas,
>
> On Samstag, 18. Januar 2014, Andreas Beckmann wrote:
>> We could start with having both sid_i386 and sid_amd64 for now. And they
>> should be tested *full*.
>
> we really want to test testing2sid and wheezy
Followup-For: Bug #734913
Hi,
the recent fix did not cover all cases:
* libstdc++-4.9-doc needs to Conflicts: libstdc++-4.8-doc
(not libstdc++6-4.8-doc)
* libx32stdc++6-4.9-dbg needs to Conflicts: libx32stdc++6-4.8-dbg
To avoid having the list of conflicts growing infinitely in the future,
wh
-8.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Configure with --with-gcc-arch=no to generate generic code.
+(Closes: #735368)
+
+ -- Andreas Beckmann Sat, 18 Jan 2014 17:46:36 +0100
+
meep (1.1.1-8) unstable; urgency=low
* debian/control: Standards Version to 3.9.3. (N
install-info calls in maintainer scripts. (Closes: #708497)
+ * Switch to debhelper 9.
+ * Add info-dir-section. (Closes: #528883)
+ * Note that the upstream URL is no longer available. (Closes: #624415)
+
+ -- Andreas Beckmann Sat, 18 Jan 2014 18:15:04 +0100
+
opt (3.19-1.1) unstable; u
tainer scripts. (Closes: #708492)
+
+ -- Andreas Beckmann Sat, 18 Jan 2014 19:30:03 +0100
+
jargon (4.0.0-5) unstable; urgency=low
* Don't install /usr/doc link (closes:#322809)
diff -u jargon-4.0.0/debian/prerm jargon-4.0.0/debian/prerm
--- jargon-4.0.0/debian/prerm
+++ jargon-4.0.0/debi
ian/changelog
--- bison++-1.21.11/debian/changelog
+++ bison++-1.21.11/debian/changelog
@@ -1,3 +1,10 @@
+bison++ (1.21.11-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Get rid of install-info calls in maintainer scripts. (Closes: #708488)
+
+ -- Andreas Beckmann Sat, 18 Jan 2014 1
2)
+ * elib.texi: s/^@sp$/@sp 1/ (Closes: #712317)
+ * Use unversioned Depends: emacs | emacsen. (Closes: #433985)
+ * Fix doc-base section.
+ * d/copyright: Update FSF address and point to common-licenses/GPL-2.
+ * Fix some debhelper issues.
+
+ -- Andreas Beckmann Sat, 18 Jan 2014 20:30:5
729278)
+ * Fix typo in description. (Closes: #406654)
+ * Use Homepage field. (Closes: #615335)
+
+ -- Andreas Beckmann Sat, 18 Jan 2014 23:15:04 +0100
+
trueprint (5.3-4) unstable; urgency=low
* New maintainer (Closes: #374128)
only in patch2:
unchanged:
--- trueprint-5.3.orig/debian
conversion. (Closes: #728427)
+Use dpkg-maintscript-helper dir_to_symlink which requires dpkg 1.17.5.
+
+ -- Andreas Beckmann Sun, 19 Jan 2014 00:40:32 +0100
+
python-babel (1.3+dfsg.1-2) unstable; urgency=low
* Fixes upgrade from 1.3-2 that was deleting files from the -localedata
diff -Nru
Package: qa.debian.org
Severity: wishlist
Hi,
it would be nice if the PTS would list package versions in DEFERRED
(and the remaining time) in the "versions" box, like it is done for
packages in the NEW queue.
Andreas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with
On 2014-01-17 05:20, Adam Borowski wrote:
> Hi! I'm running a -rc kernel (as 3.12 doesn't work for me due to #730863),
> and the module builds but fails to insert with the following message:
>
> nvidia: Unknown symbol acpi_os_wait_events_complete (err 0)
That symbol should be present in your ker
On 2014-01-15 17:54, Karsten wrote:
> Here are the automatic collected informations.
So far I don't see any errors ...
X starts ... and after 30 seconds cleanly shuts down.
Please check the logfile of login manager (gdm3, kdm, xdm or whatever)
Please try the new driver releases 319.82 in unstable
On 2014-01-18 23:56, moli wrote:
> ok, another way to reproduce without chrome or flash or youtube:
>
> reboot to a clean system, dont run anything, only an X and a console
> # mkdir /tmp/foo
> # mount -t tmpfs none /tmp/foo -o size=900m
> # dd if=/dev/zero of=/tmp/foo/bar
> (a message comes with
On 2014-01-19 21:13, Andreas Beckmann wrote:
> Could you try the vesa (xserver-xorg-video-vesa) driver instead and see
> what happens under extreme memory pressure?
And since I suspect xserver-xorg-video-intel, you might want try a newer
version of that driver. The Xorg maintainers can pr
Package: ftp.debian.org
Severity: normal
Please remove the outdated libsbml binaries from armhf, the package
cannot be built there any more.
Andreas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
nmu libgeo-proj4-perl_1.04-1 . sparc . -m "Rebuild against perl 5.18"
The buildd chroot on sompek.debian.org that built the package on
04 Jan 2014 21:30
https://buildd.debian.org/status/fet
On 2014-01-19 16:05, Ivo De Decker wrote:
> On Wed, Apr 24, 2013 at 09:20:59PM +0200, Holger Levsen wrote:
>> h01ger: about #678931, perhaps piuparts should use etckeeper and
>> report
>> the file content changes as well, to have some idea what is going on... :)
>
> This can be done by adding t
Control: reopen -1
Control: reassign -1 xserver-xorg-video-intel 2:2.19.0-6
Control: retitle -1 xserver-xorg-video-intel: X crashes under memory pressure
Hi moli,
thanks for the further tests. I'm reopening and reassigning this bug
report from 'general' to the intel driver, moving the discussion
Followup-For: Bug #735364
Hi,
to fix this, just remove the -march=... settings from
debian/makefile.local.*
The build system has the nasty behavior where
debian/rules clean
first triggers a full build (with -march=native which is the default as
long as no makefile.local got setup).
Andreas
On 2014-01-20 10:39, Karsten Malcher wrote:
>> And try a minimal config file as decribed in
>> /usr/share/doc/nvidia-driver/README.Debian.gz
>
> I tried to use nvidia-xconfig with the same result of this black blank
> screen.
> The xorg.conf is attached.
Did you try the minimal one? I.e. only t
On 2014-01-18 17:44, Helmut Grohne wrote:
> When using piuparts --pbuilder I noticed that it feels slow. Now that's
> not the fault of piuparts, but instead an artifact of my setup that made
> me ponder whether piuparts' defaults are good. It happens that I mounted
> /var/cache/pbuilder/build as an
On 2014-01-10 03:28, Andreas Beckmann wrote:
> ... that probably won't work ... I would expect a crash on a
> disappearing package.
OK, it didn't crash. But it does no longer update the source summaries
for removed source packages, e.g.
https://piuparts.debian.org/wheezy
Package: ftp.debian.org
Severity: normal
Please remove the outdated armhf binaries from nvidia-graphics-drivers
in unstable. Upstream did no 319.82 release for armhf. armhf support is
available in the newer upstream 331.38 in experimental.
Andreas
--
To UNSUBSCRIBE, email to debian-bugs-dist-
On 2014-01-20 15:03, Holger Levsen wrote:
> Hi,
>
> On Sonntag, 19. Januar 2014, Andreas Beckmann wrote:
>> Can't we run etckeeper "from outside" of the chroot like adequate?
>
> not sure if we can do this with etckeeper, but we can certainly preserve /etc
On 2014-01-21 03:14, Holger Levsen wrote:
> While this is all nice and true, I don't really see a reason not to include
> Helmut's patch, so I'm inclined to use it, as it makes using --pbuilder more
> straightforward. (With the downsides --pbuilder has...)
Would it be useful to have --pbuilder
Package: kamailio-java-modules
Version: 4.1.1-1
Severity: serious
Tags: sid
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package is no longer
installable in sid:
kamailio-java-modules/i386 unsatisfiable Depends: gjc-jre
You could try gcj-jre
On 2014-01-20 13:46, Karsten wrote:
> This time i booted with the suggested xorg.conf with vesa.
> Result is the same.
> I land on the text console
> After login and startx i got "no screens found"
> Trying now to install driver from unstable ...
The vesa test was done in a mixed vesa+nvidia setup
Package: yrmcds
Version: 1.0.3-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):
http://www.debian.org/doc/debian-policy/ch-m
On 2014-01-11 07:59, Charles Plessy wrote:
> it seems that Piuparts is not able to install grub-common, on which
> pv-grub-menu depends, but I do not undertand why. Do you have an explanation
> ?
grub-common is successfully installed.
Keeping the failed chroot and digging around there manually:
Package: python-babel
Version: 1.3-1
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:
http://www.debian.org/doc/debian-policy/ch-maintai
On 2014-01-21 23:40, Charles Plessy wrote:
>> ++ find_device /
>> ++ grub-probe --device-map=/boot/grub/device.map -t device /
>> + root_device=
>
> Thanks for the help, could you replace
>
> grub-probe --device-map=${device_map} -t device $1 2> /dev/null
>
> with
>
> grub-probe --devic
Package: pkg-php-tools
Version: 1.9
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
I'm filing this against the packaging helper that most probably causes
this issue, not against the affected packages.
I recently noticed new problems where packages install files over
ex
Package: libjackson-json-java-doc
Version: 1.9.2-2
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
Package: python-whoosh-doc
Version: 2.5.6-2
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 ver
Package: libwine-bin,wine-bin
Version: 1.6.2-2
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
Package: rubberband-vamp,rubberband-ladspa
Version: 1.8.1-4
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
Package: vdr-dbg
Version: 2.0.3-1
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 th
Package: python-svn-dbg
Version: 1.7.8-0.1
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 vers
Package: python-sqlite-dbg
Version: 1.0.1-10
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 ve
Package: python-pysqlite1.1-dbg
Version: 1.1.8a-7
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 o
Package: python-apsw-doc
Version: 3.8.2-r1-1
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 ve
Package: openafs-kpasswd,openafs-fuse
Version: 1.6.6~pre2-1
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
Package: libnetfilter-queue-dev,libnetfilter-queue1-dbg
Version: 1.0.2-1
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.
Package: libnfnetlink0-dbg
Version: 1.0.1-2
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 ver
Package: llvm-dev
Version: 1:3.3-21
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
On 2014-01-22 04:13, Russ Allbery wrote:
> Andreas Beckmann writes:
>
>> 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
-01-22 05:03:46.0 +0100
@@ -1,3 +1,12 @@
+flexpart (9.02-7.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * postinst: Do not run update-alternatives --auto as that would override
+local customization.
+ * prerm: Remove the correct alternative. (Closes: #729212)
+
+ -- Andre
as that could
+override local customization.
+
+ -- Andreas Beckmann Wed, 22 Jan 2014 05:18:24 +0100
+
fluxbox (1.3.5-1) unstable; urgency=low
* Release from Experimental to Unstable. No changes.
diff -Nru fluxbox-1.3.5/debian/fluxbox.preinst fluxbox-1.3.5/debian/fluxbox.preinst
On 2014-01-22 09:55, Karsten wrote:
> I have done as described.
> After the reboot i land on the text shell.
> But now i got an interesting other result.
> When i log in and startx the screen is flickering and i can see
> for a short moment something like a desktop, then the screen is black.
This
Control: reassign -1 src:wfmath 0.3.12-3
Control: tag -1 jessie sid
On Wednesday, 22. January 2014 08:43:20 coldtobi wrote:
> I understand that you need a sponsor for it, unfortunatly I am not a DD.
> However, I miss actions from you actively searching for one, and thre is
> also not a response fo
Package: openrc
Version: 0.12.4+20131230-7
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,
th
[Please keep the Bug Cc:ed - therefore fullquote]
On 2014-01-22 10:47, Karsten Malcher wrote:
> Hello Diederik,
>
> that's really interesting.
> So it must be a configuration problem of previous installations?
> Do you have made a fresh installation or an upgrade?
>
> I have made now an addition
On 2014-01-22 22:44, Adam D. Barratt wrote:
> Have you checked the resulting package, beyond confirming that it
> installs? I'd be particularly interested in a full binary debdiff; I
> realise this is "just" a no-change rebuild, but the previous upload was
> pre-lenny.
$ debdiff nana_2.5-12_amd64.
Package: staden-io-lib
Version: 1.13.3-2
Severity: serious
Justification: fails to build from source
Hi,
staden-io-lib only built successfully on i386-any and amd64-any, all
other architectures fail two tests.
https://buildd.debian.org/status/package.php?p=staden-io-lib
excerpts from
https://bu
Source: ruby-prof
Version: 0.13.1-1
Severity: serious
Hi,
ruby-prof FTBFS on all architectures except powerpc:
https://buildd.debian.org/status/package.php?p=ruby-prof
Excerpt from
https://buildd.debian.org/status/fetch.php?pkg=ruby-prof&arch=i386&ver=0.13.1-1&stamp=1387838705
make "DESTDIR="
Source: sra-sdk
Version: 2.3.4-2+dfsg-1
Severity: serious
Hi,
sra-sdk FTBFS on i386 and amd64 due to symbol changes.
https://buildd.debian.org/status/fetch.php?pkg=sra-sdk&arch=i386&ver=2.3.4-2%2Bdfsg-1&stamp=1387878452
https://buildd.debian.org/status/fetch.php?pkg=sra-sdk&arch=kfreebsd-i386&ve
101 - 200 of 15613 matches
Mail list logo
