Re: Bugs marked incomplete

[Chris Coulson]

2008/9/2 Bryce Harrington <[EMAIL PROTECTED]>

> On Tue, Sep 02, 2008 at 01:54:21AM +0200, Wouter Stomp wrote:
> > On Mon, Sep 1, 2008 at 11:44 PM, Bryce Harrington <[EMAIL PROTECTED]>
> wrote:
> > > First, afaik automatic-expiration is not enabled for Ubuntu.  It tracks
> > > when bugs will expire but doesn't close them without human action.
> > >
> >
> > Ok, so what does expiring mean then?
>
> Auto-expiration is a Launchpad feature that can be enabled on a
> per-project (but not per-source) basis.  So, some non-Ubuntu Launchpad
> using projects may have it flipped on.  Ubuntu made the decision that
> auto-expiring bugs was not desireable, so in Ubuntu the "expires in X
> days" is more of just a hint for triagers and reporters.
>
> > > So... I think this isn't a problem.  If you could show a (recent)
> > > example where something in Ubuntu got expired this way, that'd be worth
> > > knowing about.
> > >
> >
> > No I don't :-) (although if I remember right it did happen to some of
> > my bugs a while ago) I guess I misunderstood the expiring concept.
> > Thanks for explaining.
>
> Sure.  There was a brief period a while ago when this was turned on by
> default for Ubuntu, which may be what you remember.  AFAIK all bugs that
> were closed due to this, were reopened.
>
> Bryce
>
> --
> Ubuntu-devel-discuss mailing list
> Ubuntu-devel-discuss@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
>

Unfortunately, some triagers do just close bugs when they are marked ready
to expire, without actually checking whether the reporter provided the
requested information. I have re-opened one such report recently, although I
don't want to share the bug report number publicly on the mailing list
without contacting the triager first.

Regards
Chris
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bugs marked incomplete

[Bryce Harrington]

On Tue, Sep 02, 2008 at 08:04:43AM +0100, Chris Coulson wrote:
> Unfortunately, some triagers do just close bugs when they are marked ready
> to expire, without actually checking whether the reporter provided the
> requested information. I have re-opened one such report recently, although I
> don't want to share the bug report number publicly on the mailing list
> without contacting the triager first.

As you apparently gathered, that is certainly possible but generally
incorrect.  Discussing it with the triager is the right approach.

If the reporter provided the information requested, then the bug should
not be closed as expired - it should either be moved to
Confirmed/Triaged, or additional questions asked and left at Incomplete
(with the counter reset).

Bryce

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bugs marked incomplete

[James Westby]

On Mon, 2008-09-01 at 23:32 +0200, Wouter Stomp wrote:
> Hello,
> 
> Bugs that are marked incomplete and subsequently get a reply from the
> original reporter often stay in the incomplete status. This means they
> automatically get closed even though the needed info was provided. I
> think it would be a good idea to automatically change the status to
> new once a new comment is made on an incomplete bug.

I have seen this feature in a list of the launchpad teams possible plans
for LP 3.0, so it may be something that happens soon.

Thanks,

James

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

PackageKit: Call for testing

[Sebastian Heinlein]

The APT backend for PackageKit [1] has made a lot of progress recently
in the 0.3.x series. It nearly supports all features of PackageKit. 

Highlights of the 0.3.x series are:

  * Search for codecs and mime type handlers
  * Local file installation
  * Change log for updates
  * Group support
  * Repository handling
  * Notification of new distro releases
  * A lot of bug fixes

See the feature matrix for more infromation:

http://www.packagekit.org/pk-matrix.html

Currently we have got a quite outdated 0.2.4 version in Intrepid.
Furthermore sharing the same version would help to reduce maintenance
burden, since Fedora plans to ship 0.3.2 in the next release. But before
proposing a freeze exception I would like to have some feedback.

So if you are interested in this piece of software and want to push
packagekit forward please test it on your system and report bugs that
you may encounter.

You can find packages of the upcoming 0.3.2 release for Hardy and
Intrepid in this Personal Package Archive:

https://launchpad.net/~packagekit/+archive

Add the repository and install the packages packagekit and
gnome-packagekit.

The new applications will appear in the System -> Administration menu.

The obligatory screenshot:

http://www.glatzor.de/fileadmin/files/screenshots/packagekit/Bildschirmfoto.png

Cheers,

Sebastian


signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

CDBS and upstream changelogs

[Pär Andersson]

Hi,

I recently discovered a missing upstream changelog in a package, and after 
some confusion I found that it was caused by CDBS. Here is the relevant CDBS 
changelog:

cdbs (0.4.49ubuntu3) hardy; urgency=low
...
  * debhelper.mk.in: Do not install upstream changelogs by default. They are
huge and thus waste a lot of archive and CD space, quite uninteresting for
ordinary users, and easy to get by downloading the source package or
visiting the upstream page pointed out in copyright.
...

As this change was made intentionally I send this here instead of reporting it 
as a bug.

I realize that I am probably not the mentioned "ordinary user". However I do 
find it very annoying to have to manually download huge source packages just 
to read what have changed in a newly installed version of a package. That is 
if I even realize that the package is built using CDBS, and I therefore 
should not expect the normal changelog.gz.

This is from the Debian Policy Manual, 12.7 Changelog files:
--
If an upstream changelog is available, it should be accessible 
as /usr/share/doc/package/changelog.gz in plain text. If the upstream 
changelog is distributed in HTML, it should be made available in that form 
as /usr/share/doc/package/changelog.html.gz and a plain text changelog.gz 
should be generated from it using, for example, lynx -dump -nolist. If the 
upstream changelog files do not already conform to this naming convention, 
then this may be achieved either by renaming the files, or by adding a 
symbolic link, at the maintainer's discretion.[93]
--

So disabling CDBS automatic handling of this looks like an obvious policy 
violation to me. It also introduces hidden changes in Ubuntu compared to 
Debian, as CDBS built packages synced from Debian to Ubuntu will miss 
documentation files compared to the package in Debian.

How much space does this really save on the CDs?

Cheers,

Pär Andersson


signature.asc
Description: This is a digitally signed message part.
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Intrepid compatibility with C3 CPUs

[Oliver Grawert]

hi,
On Mo, 2008-08-18 at 19:31 +0100, Sam Tygier wrote:
> Hi
> 
> The current intrepid test releases will not boot on machines with Via C3 
> CPUs. At boot the message:
> 
> "This kernel requires the following features not present on the CPU: cmov
> Unable to boot - please use a kernel appropriate for your CPU."
it was a bug introduced by merging the 2.6.24 configs from hardy to
2.6.26 in intrepid and is solved in the 2.6.27 builds ... 

> [EMAIL PROTECTED]:~$ grep CONFIG_M586 /boot/config-2.6.26-5-generic 
# CONFIG_M586 is not set
# CONFIG_M586MMX is not set
# CONFIG_M586TSC is not set
[EMAIL PROTECTED]:~$ grep CONFIG_M586 /boot/config-2.6.27-2-generic 
CONFIG_M586=y
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set

ciao
oli




signature.asc
Description: This is a digitally signed message part
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: CDBS and upstream changelogs

[Martin Pitt]

Pär Andersson [2008-09-02 12:57 +0200]:
> I realize that I am probably not the mentioned "ordinary user". However I do 
> find it very annoying to have to manually download huge source packages just 
> to read what have changed in a newly installed version of a package. 

We deliberately made this change in order to save several Megabytes on
the CDs, which are better spent for more useful things. You don't have
to download the entire source package, usually the upstream home pages
have an online accessible changelog.

Also, in many cases a summary of the interesting upstream changes are
echoed in the package changelog (debian/changelog).

> So disabling CDBS automatic handling of this looks like an obvious policy 
> violation to me.

I don't agree. Normal debhelper doesn't install upstream changelogs by
default either, and cdbs doesn't stop you from doing it, it just
doesn't do it by default (as in Debian).

> It also introduces hidden changes in Ubuntu compared to 
> Debian, as CDBS built packages synced from Debian to Ubuntu will miss 
> documentation files compared to the package in Debian.

Right, that was the intention. Syncing a source package from Debian to
Ubuntu will cause a lot of other "hidden" changes, such as toolchain
hardening, translation stripping, gettext support for .desktop files,
and all that. The great thing about cdbs is that we can make those
changes centrally and document them there, instead of spreading them
over hundreds of source packages and constantly being inconsistent (of
course that doesn't apply to all packages which don't use cdbs).

> How much space does this really save on the CDs?

Back then, when we made the change, we rebuilt some 10 packages too
free several MB. It's difficult to measure the savings for all
packages using cdbs, but I guesstimate an magnitude of 10 MB.

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bugs marked incomplete

[Brian Murray]

On Mon, Sep 01, 2008 at 11:32:20PM +0200, Wouter Stomp wrote:
> Hello,
> 
> Bugs that are marked incomplete and subsequently get a reply from the
> original reporter often stay in the incomplete status. This means they
> automatically get closed even though the needed info was provided. I
> think it would be a good idea to automatically change the status to
> new once a new comment is made on an incomplete bug.

There are actually two sub-statuses, if you will, to Incomplete.  They
are "Incomplete w/o response" and "Incomplete w/ response" both of which
are searchable for via the Launchpad UI.  When a bug report receives a
response after being set to a status of Incomplete, the sub-status then
becomes "Incomplete w/ response" and the expiration timer is reset.

-- 
Brian Murray @ubuntu.com


signature.asc
Description: Digital signature
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bugs introduced in GCC?

[Colin Watson]

On Sun, Aug 17, 2008 at 06:32:41PM -0400, Richard M. Stallman wrote:
> Are the statements below true?
> Is the Ubuntu patch really 5 MB?

It is, although bear in mind that that includes a large volume of
packaging infrastructure; 1.3 MB of files in the Ubuntu patch have
nothing to do with patching GCC source. Of the remainder, 2.8 MB
consists simply of an SVN update up to 20080329, and a chunk of the rest
is conditionally applied depending on the architecture.

In terms of actual volume of patches against upstream, and excluding SVN
updates, the diff from the base Debian 4.2.3-2 version and Ubuntu 8.04's
4.2.3-2ubuntu7 is about 40 KB.

> If so, what is it meant to change?

Matthias (CCed) should be able to give more information on any
particular patches that are of concern.

> From: John Regehr <[EMAIL PROTECTED]>
> 
> ...the default C 
> compiler for Ubuntu [GNU/]Linux 8.04 is a patched gcc-4.2.3 which (on x86) 
> miscompiles this rather simple function:
> 
> int func_1 (void)
> {
>signed char l_11 = 1;
>unsigned char l_12 = -1;
>return (l_11 > l_12);
> }
> 
> The emitted code returns 1 instead of 0.  An unpatched gcc-4.2.3 compiles 
> this correctly.

Confirmed, although this is not the case for the gcc-4.2 package in our
development branch (4.2.4-3ubuntu2). There was already a bug open for
this (https://bugs.launchpad.net/ubuntu/+source/gcc-4.2/+bug/256797) and
I've adjusted its status and given it to Matthias. Since it's fixed in
our development branch, and I've bisected the fix down to a single
version, it should be relatively easy to track down.

As a miscompilation of simple code, I think this would merit an update
to 8.04.

Thanks,

-- 
Colin Watson   [EMAIL PROTECTED]

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bugs marked incomplete

[(``-_-´´) -- Fernando]

Olá James e a todos.

On Tuesday 02 September 2008 10:28:50 James Westby wrote:
> I have seen this feature in a list of the launchpad teams possible plans for 
> LP 3.0, so it may be something that happens soon.

I guess Bugs should work as Answers does.
Once the OP replies, it changes the state, until the OP marks it as Solved, in 
this case Invalid, or FixReleased by QA or Dev.

-- 
BUGabundo  :o)
(``-_-´´)   http://LinuxNoDEI.BUGabundo.net
Linux user #443786GPG key 1024D/A1784EBB
My new micro-blog @ http://BUGabundo.net
ps. My emails tend to sound authority and aggressive. I'm sorry in advance. 
I'll try to be more assertive as time goes by...


signature.asc
Description: This is a digitally signed message part.
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bugs marked incomplete

[Thomas Novin]

On Mon, 2008-09-01 at 23:32 +0200, Wouter Stomp wrote:
> Bugs that are marked incomplete and subsequently get a reply from the
> original reporter often stay in the incomplete status. This means they
> automatically get closed even though the needed info was provided. I
> think it would be a good idea to automatically change the status to
> new once a new comment is made on an incomplete bug.

IIRC..Bugzilla does this nicely (might be the only thing it does
nicely). When a bug is marked incomplete by a triager the original
reporter gets a email notification (just as LP) but then when the
reporter responds and presses submit, he gets a question which is
something like "Did you give the developers what they needed?".

That would be one way to solve it..

Ps. This is also almost how it works on LP Answers as well.

Rgds


-- 
Thomas Novin <[EMAIL PROTECTED]>
GPG key: http://xyz.pp.se/~thnov/gpg.asc


-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: OpenOffice 3 and Firefox 3.1 in Intrepid?

[Matthias Klose]

Vishal Rao schrieb:
> What about other packages like Eclipse (which currently shows at 3.2)

did you package 3.4? very cool! where can I find the package?

  Matthias

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: PackageKit: Call for testing

[Luke L]

It's packagekit-gnome, not 'gnome-packagekit'.

Worked fine for me. Are we supposed to be critiquing the software? It was a
bit minimalist, and the frames in the windows are not resize-able. It
doesn't seem as full featured as Synaptic, though it has a good look to it.
It's info area is better laid out, and a live search feature. The repo
listing is better in Synaptic.

In short, I could see it being very useful and competitive with Synaptic,
with a few tweaks and cleanups.

On Tue, Sep 2, 2008 at 5:05 AM, Sebastian Heinlein <[EMAIL PROTECTED]>wrote:

> The APT backend for PackageKit [1] has made a lot of progress recently
> in the 0.3.x series. It nearly supports all features of PackageKit.
>
> Highlights of the 0.3.x series are:
>
>  * Search for codecs and mime type handlers
>  * Local file installation
>  * Change log for updates
>  * Group support
>  * Repository handling
>  * Notification of new distro releases
>  * A lot of bug fixes
>
> See the feature matrix for more infromation:
>
> http://www.packagekit.org/pk-matrix.html
>
> Currently we have got a quite outdated 0.2.4 version in Intrepid.
> Furthermore sharing the same version would help to reduce maintenance
> burden, since Fedora plans to ship 0.3.2 in the next release. But before
> proposing a freeze exception I would like to have some feedback.
>
> So if you are interested in this piece of software and want to push
> packagekit forward please test it on your system and report bugs that
> you may encounter.
>
> You can find packages of the upcoming 0.3.2 release for Hardy and
> Intrepid in this Personal Package Archive:
>
> https://launchpad.net/~packagekit/+archive
>
> Add the repository and install the packages packagekit and
> gnome-packagekit.
>
> The new applications will appear in the System -> Administration menu.
>
> The obligatory screenshot:
>
>
> http://www.glatzor.de/fileadmin/files/screenshots/packagekit/Bildschirmfoto.png
>
> Cheers,
>
> Sebastian
>
> --
> Ubuntu-devel-discuss mailing list
> Ubuntu-devel-discuss@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
>
>


-- 
Luke L.
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: PackageKit: Call for testing

[Sebastian Heinlein]

Am Dienstag, den 02.09.2008, 23:50 -0500 schrieb Luke L:
> It's packagekit-gnome, not 'gnome-packagekit'.
> 
> Worked fine for me. Are we supposed to be critiquing the software? It
> was a bit minimalist, and the frames in the windows are not
> resize-able. It doesn't seem as full featured as Synaptic, though it
> has a good look to it. It's info area is better laid out, and a live
> search feature. The repo listing is better in Synaptic.
> 
> In short, I could see it being very useful and competitive with
> Synaptic, with a few tweaks and cleanups.

Currently it is not the question if to replace our existing tools. But
it is important to not miss the PackageKit interface on APT based
systems, since some upstream projects think about using it for
installing additional components.

Furthermore PackageKit only wants to target simply package manupiulation
tasks. It will never be a replacement for Synaptic, but could be used in
the language selector or gnome-app-install.

Cheers,

Sebastian


signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss