Your message dated Mon, 11 May 2026 12:12:15 +0000
with message-id <[email protected]>
and subject line Bug#1135678: Removed package(s) from unstable
has caused the Debian Bug report #881940,
regarding Curious side effect of a no-op mapc
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 [email protected]
immediately.)


-- 
881940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881940
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rep
Version: 0.92.5-3

The attached piece of Lisp source, when run through rep with a command
such as "rep test.lisp", prints

a1 -> 2
a2 -> 5
b1 -> 5

where I would have expected the middle line to read 'a2 -> 2', because
the functions a2 and a1 are return values from the same lambda and ought
to behave the same.

If I remove or comment out line 3 of the file, which is a call to mapc
that I would expect to have no effect at all, then the output changes to
become what I expected. This also happens if I change the final line of
'indirector' so that the lambda returns index rather than index-copy -
another transformation that surely ought to make no difference.

I can't _think_ of any quirk of semantics in any flavour of Lisp that
makes this behaviour expected.

Cheers,
Simon

-- 
for k in [pow(x,37,0x1a1298d262b49c895d47f) for x in [0x50deb914257022de7fff,
0x213558f2215127d5a2d1, 0x90c99e86d08b91218630, 0x109f3d0cfbf640c0beee7,
0xc83e01379a5fbec5fdd1, 0x19d3d70a8d567e388600e, 0x534e2f6e8a4a33155123]]:
 print("".join([chr(32+3*((k>>x)&1))for x in range(79)])) # <[email protected]>

Attachment: test.lisp
Description: Binary data


--- End Message ---
--- Begin Message ---
Version: 0.92.7-4.1+rm

Dear submitter,

as the package librep 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/1135678

The version of this package that was in Debian prior to this removal
can still be found using https://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
[email protected].

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to