[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#499483: marked as done (mouseemu: newer upstream available; please re-sync)



Your message dated Thu, 23 Apr 2020 21:39:56 +0000
with message-id <E1jRjZc-000HlS-2i@fasolo.debian.org>
and subject line Bug#958387: Removed package(s) from unstable
has caused the Debian Bug report #499483,
regarding mouseemu: newer upstream available; please re-sync
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
499483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499483
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: mouseemu
Version: 0.15-8
Severity: normal

[Re severity: "newer upstream" is very minor severity because
 the only thing it adds beyond Debian's 0.15-5 is a new upstream URL
 and maintainer.  The "please resync" part is severity normal on the
 unverified assumption that the remaining diffs haven't yet been sent
 upstream as per Debian policy §4.3 or item 2 of the social contract.]

There is a newer upstream version available, 0.16.

My local Debian mirror doesn't have 0.15-5.diff.gz, but based on
0.15-6.diff.gz and debian/changelog, it looks like 0.16 is equal to
Debian's 0.15-5 except for noting a new maintainer and new canonical
download location.


On the subject of resyncing with upstream:
write_error.dpatch doesn't look right to me: if the
`if (write(fd, buf, n) < n)' test was previously succeeding in such a
way that `... <= 0' (the version introduced by write_error.dpatch)
wouldn't succeed (i.e. if write_error.dpatch actually makes a difference
to execution), then I believe the right thing to do is to loop until all
of buf has been written: i.e. introduce a function such as (untested):

  static ssize_t write_all(int fd, void const *buf, size_t count)
  {
	while (count) {
		ssize_t w = write(fd, buf, count);
		if (w < 0) {
			if (errno == EINTR)
				continue;
			return -1;
		}

		count -= w;
		buf = (void const *)((char const *)buf + w);
	}
	return 0;
  }

and use `if (write_all(fd, &event, sizeof(event)) < 0) perror(...);'.

(If OTOH write_error.dpatch is believed not to make a difference to
 execution, then I still think it is wrong: if in fact it turns out that
 there is a difference, then we want the perror to execute, to alert us
 to the fact that there is in fact a difference, in which case the
 write_all suggestion applies.)

pjrm.


-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



--- End Message ---
--- Begin Message ---
Version: 0.15-10+rm

Dear submitter,

as the package mouseemu has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/958387

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---

Reply to: