similar to: usertags for xen bugs?

On Fri, Aug 16, 2013 at 03:16:49PM +0100, Ian Campbell wrote: > Looking through http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=xen I > think it would be useful to add some usertags, in particular to easily > filter for toolstack specific (i.e xend) bugs. I've never seen the use for this. The kernel team tried and it did not work well. The release team however uses them and like it.

On Mon, 2013-08-19 at 13:28 +0200, Bastian Blank wrote: > On Fri, Aug 16, 2013 at 03:16:49PM +0100, Ian Campbell wrote: > > Looking through http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=xen I > > think it would be useful to add some usertags, in particular to easily > > filter for toolstack specific (i.e xend) bugs. > > I've never seen the use for this. I was

user pkg-xen-devel@lists.alioth.debian.org usertag 271051 + close-after-first-upload usertag 326817 + probably-unreproducible usertag 331297 + probably-fixed usertag 321154 + probably-fixed usertag 327493 + pending-in-svn usertag 342249 + pending-in-svn usertag 321157 + pending-in-svn usertag 323698 + pending-in-svn thanks Hi! I'm user-tagging some of the bugs in the bts so we can keep a

Processing commands for control at bugs.debian.org: > user pkg-xen-devel at lists.alioth.debian.org Setting user to pkg-xen-devel at lists.alioth.debian.org (was ijc at debian.org). > usertags 599520 toolstack-xend There were no usertags set. Usertags are now: toolstack-xend. > close 599520 4.4.0-1 Failed to add fixed version '4.4.0-1' to 599520: Not altering archived bugs; see

Processing commands for control at bugs.debian.org: > user pkg-xen-devel at lists.alioth.debian.org Setting user to pkg-xen-devel at lists.alioth.debian.org (was ijc at debian.org). > usertags 532603 toolstack-xend There were no usertags set. Usertags are now: toolstack-xend. > close 532603 4.4.0-1 Bug #532603 [src:xen] xen-utils-3.2-1: incorrectly calls network-script Marked as fixed in

user debian-release at lists.debian.org usertag 469013 -goal-python2.5 retitle 469013 Python API memory handling bug in unused code path found 469013 3.0-unstable+hg11561-1 thanks Hi, the code that exhibits the buggy PyObject_NEW/PyMem_DEL behaviour (in xen-unstable-3.0-unstable+hg11561/tools/pygrub/src/fsys/ext2/ext2module.c) is not actually compiled and the results shipped[1]. As such,

Processing commands for control at bugs.debian.org: > user pkg-xen-devel at lists.alioth.debian.org Setting user to pkg-xen-devel at lists.alioth.debian.org (was ijc at debian.org). > usertags 477525 toolstack-xend There were no usertags set. Usertags are now: toolstack-xend. > close 477525 4.4.0-1 Bug #477525 [src:xen] xend with network-route fails to start, missing $vifnum Marked as

Processing commands for control at bugs.debian.org: > user pkg-xen-devel at lists.alioth.debian.org Setting user to pkg-xen-devel at lists.alioth.debian.org (was ijc at debian.org). > usertags 502123 toolstack-xend There were no usertags set. Usertags are now: toolstack-xend. > close 502123 4.4.0-1 Bug #502123 [src:xen] xen-utils-unstable: Debian patch breaks paravirtualized guest initrd

Processing commands for control at bugs.debian.org: > user pkg-xen-devel at lists.alioth.debian.org Setting user to pkg-xen-devel at lists.alioth.debian.org (was ijc at debian.org). > usertags 494727 toolstack-xend There were no usertags set. Usertags are now: toolstack-xend. > close 494727 4.4.0-1 Bug #494727 [src:xen] xen-utils-3.2-1: Fail to define a new domain. Marked as fixed in

Hi, AFAIK, the status of Xen in lenny is currently the following: - no dom0 kernel - domU kernel only for i386 (no domU kernel for amd64) I was told (I don't remember where) that this is because the vanilla kernel only supports domU for i386, and has no dom0 support, so distros have to port the patches to their kernels (please correct me if I'm wrong). However: - etch shipped with dom0

Hi, there are quite some ancient xen bug reports filed against packages that the BTS does not know (any longer) since they have been removed. I would appreciate it if you could take a look at the xen bugs (mostly xen 3.x stuff that was neither reassigned to xen 4 nor closed at the time xen3 was removed) and either reassign them to existing (source) packages or close them. The complete list of

Package: xen-utils-common Version: 4.1.2-3 Severity: important /etc/default/xen, which carries the TOOLSTACK setting, is not honored by xend init script. The xend initscript doesn't check for the value of TOOLSTACK. It just populates it in its initscript. lnx200-39:/etc/init.d# grep TOOLSTACK * xend:TOOLSTACK=$(/usr/lib/xen-common/bin/xen-toolstack 2>/dev/null) xend: if [ -z

Ian Campbell wrote: > + * Expand on the descriptions of some packages. (Closes: #466683) Trivial typo here: > Package: libxen-dev > Section: libdevel > Depends: libxen- at version@ (= ${binary:Version}), libxenstore3.0 (= ${binary:Version}), ${misc:Depends} > Description: Public headers and libs for Xen > This package contains the public headers and static libraries for

Source: xen Version: 4.1.1-2 Severity: serious Tags: wheezy sid User: debian-qa at lists.debian.org Usertags: qa-ftbfs-20111022 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[5]: Entering directory `/build/xen-njlTaX/xen-4.1.1/debian/build/build-utils_amd64/tools/check' > PYTHON=python2.6

tags 466683 +patch thanks commit 765ac4708e4dd8a6fea0028d631a7c3363b286b7 Author: Ian Campbell <ijc at hellion.org.uk> Date: Fri Aug 16 10:30:17 2013 +0100 * debian/changelog: Update * debian/templates/control.main.in: Update descriptions for some packages. diff --git a/xen/debian/changelog b/xen/debian/changelog index 6100e75..e5b25ef 100644 --- a/xen/debian/changelog +++

Processing commands for control at bugs.debian.org: > user debian-qa at lists.debian.org Setting user to debian-qa at lists.debian.org (was debian at abeckmann.de). > usertags 669005 piuparts Bug#669005: uninstallable on sid (might just need require a rebuild) There were no usertags set. Usertags are now: piuparts. > affects 669005 + shogun-python-static shogun-python-modular

Package: xen-utils-common Version: 4.1.2-7 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, The script /usr/lib/xen-common/bin/xen-toolstack improperly aborts if *either* `xm` or `xl` cannot be found in the xen-dir (/usr/lib/xen-4.0/bin). This means that a default installation (e.g. following Debian wiki on the subject, namely installing xen-linux-system and

Processing commands for control at bugs.debian.org: > # As per Moritz, not blockers > user release.debian.org at packages.debian.org Setting user to release.debian.org at packages.debian.org (was adam at adam-barratt.org.uk). > tag 609531 + squeeze-ignore Bug #609531 [xen] CVE-2010-4255: 64-bit PV xen guest can crash host by accessing hypervisor per-domain memory area Added tag(s)

Processing commands for control at bugs.debian.org: > found 712376 4.1.4-4 Bug #712376 [src:xen] xen FTBFS with current gcc-4.8 Marked as found in versions xen/4.1.4-4. > tags 712376 + sid jessie Bug #712376 [src:xen] xen FTBFS with current gcc-4.8 Added tag(s) sid and jessie. > user debian-gcc at lists.debian.org Setting user to debian-gcc at lists.debian.org (was bigon at debian.org).

Processing commands for control at bugs.debian.org: > user debian-security at lists.debian.org Setting user to debian-security at lists.debian.org (was carnil at debian.org). > usertags 776319 + tracked There were no usertags set. Usertags are now: tracked. > tags 776319 + upstream fixed-upstream Bug #776319 [src:xen] CVE-2015-0361 Added tag(s) upstream and fixed-upstream. > retitle